Latest Bitcoin Unlimited code patch replaces many instances of “assert()” w/ “DbgAssert()” to avoid those pesky crash-causing sanity checks.
@gubatron Isn’t it a lot harder to mine blocks when your node has crashed?
@digitsu @brucefenton’s point was regarding how a node determines the “correct” chain; cumulative work is but one of many checks.
@MadBitcoins Caveat: good luck spending separately between chains without replay protection software.
@brucefenton Yep, “most work” chain is more accurate, but /even then/ only when referring to compatible chain forks that follow same rules.
@bitrated Wouldn’t that mean no more escrow services?
@LarryBitcoin @giacomozucco More polite people ask “what’s your acceptable depth?”
.@bitrated lays out principles for dealing w/chain forks, vows to shut down if an Emergent Consensus fork prevails. https://t.co/Ud2lrFJk5r
@alansilbert SegWit supporters should tap him as a spokesman to tout transaction malleability fixes. 🙃
@twobitidiot Why is chaos imminent? I doubt whales use Circle.
@badslinky In the event that occurred I’d probably evaluate BitcoinEC
@drwasho Indeed, enterprises can afford that cost. But I like to think that Statoshi has value for users & developers. Can I charge for it?
I’m the guy who gets paged in the middle of the night if our infrastructure blows up. I won’t run unstable software. https://t.co/pf5LDh2Pih
Uh oh, is this another Bitcoin Unlimited vulnerability being exploited? https://t.co/2EdMJneyjL H/T @thomaskerin
@BronxR Are node operators reporting DDOS as opposed to process crashes / exploits? I know DNS amplification attacks have been used in past.
It appears that a nontrivial number of Bitcoin Unlimited nodes are still struggling to stay online.… https://t.co/94BjNv4oqO
RT @Ethan_Heilman: Very well written introduction to #mimblewimble:
https://t.co/qKboshtiaD
@TuurDemeester I seem to recall @jratcliff saying that he needs to rewrite his analytics software in order to run it on recent data…
@TuurDemeester I’m pretty sure that’s a @jratcliff generated chart https://t.co/EeHHO0l8AW
@ryanxcharles And yet all the electricity in the world can’t make my node accept a block that doesn’t abide by the rules I choose…
@drwasho Just checked with my VPS host for statoshi.info (@gandibar) and their largest disk is 2 TB for $115 / month. 😞
RT @coindesk: Ethereum devs had to reel in a highly anticipated app last week, after “significant” bugs provoked security concerns https://…
RT @acinq_co: LN vaporware is condensing into actual software 😀 Today we are releasing an early version of Eclair https://t.co/6MWrTC1mhF #…
.@factom Chief Scientist Brian Deery implemented a variation of SegWit on his own, well before SegWit was announced. https://t.co/zzycjSsd8a
@Kosmatos A BU node operator could lower the default EB config to say, 2MB but that risks potentially get forked off the network…
@checksum0 To be clear, I’m just trying to define resource bounding in terms that node operators can understand. Good for planning purposes.
Correction: there’s a message limit of 16 * node’s EB config value. Thus EB of 16 => 256MB https://t.co/VxYSGPEnHR https://t.co/bGHyMkftF9
@checksum0 Aha, thanks for the clarification!
@ErolKazan indeed, plus bad things would start to happen long before that size was reached.
Bitcoin Unlimited max block size is 256MB, raising worst case annual node disk usage from 50 Gigabytes ($1.50) to 13 Terabytes ($400.) 😬
@MadBitcoins It’s unclear what you’re asking because there is no such thing as “@Blockstream Core”