The below is an off-site archive of all tweets posted by @lopp ever

March 21st, 2017

Latest Bitcoin Unlimited code patch replaces many instances of “assert()” w/ “DbgAssert()” to avoid those pesky crash-causing sanity checks.

via Twitter Web Client

@gubatron Isn’t it a lot harder to mine blocks when your node has crashed?

via Twitter Web Client in reply to gubatron

@digitsu @brucefenton’s point was regarding how a node determines the “correct” chain; cumulative work is but one of many checks.

via Twitter Web Client in reply to digitsu

@MadBitcoins Caveat: good luck spending separately between chains without replay protection software.

via Twitter Web Client in reply to MadBitcoins

@brucefenton Yep, “most work” chain is more accurate, but /even then/ only when referring to compatible chain forks that follow same rules.

via Twitter Web Client in reply to brucefenton

@bitrated Wouldn’t that mean no more escrow services?

via Twitter Web Client in reply to bitrated

@LarryBitcoin @giacomozucco More polite people ask “what’s your acceptable depth?”

via Twitter Web Client in reply to LarryBitcoin

.@bitrated lays out principles for dealing w/chain forks, vows to shut down if an Emergent Consensus fork prevails. https://t.co/Ud2lrFJk5r

via Twitter Web Client

@alansilbert SegWit supporters should tap him as a spokesman to tout transaction malleability fixes. 🙃

via Twitter Web Client in reply to alansilbert

@twobitidiot Why is chaos imminent? I doubt whales use Circle.

via Twitter Web Client in reply to twobitidiot

@badslinky In the event that occurred I’d probably evaluate BitcoinEC

via Twitter Web Client in reply to badslinky

@drwasho Indeed, enterprises can afford that cost. But I like to think that Statoshi has value for users & developers. Can I charge for it?

via Twitter Web Client in reply to drwasho

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

via Twitter Web Client

@Melt_Dem Because you’re storing BTC with @circlepay and they don’t want to hold it for you?

via Twitter Web Client in reply to Melt_Dem

Uh oh, is this another Bitcoin Unlimited vulnerability being exploited? https://t.co/2EdMJneyjL H/T @thomaskerin

via Twitter Web Client

@BronxR Are node operators reporting DDOS as opposed to process crashes / exploits? I know DNS amplification attacks have been used in past.

via Twitter Web Client in reply to BronxR

It appears that a nontrivial number of Bitcoin Unlimited nodes are still struggling to stay online.… https://t.co/94BjNv4oqO

via Twitter Web Client

@TuurDemeester I seem to recall @jratcliff saying that he needs to rewrite his analytics software in order to run it on recent data…

via Twitter Web Client in reply to TuurDemeester

@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…

via Twitter Web Client in reply to ryanxcharles

@drwasho Just checked with my VPS host for statoshi.info (@gandibar) and their largest disk is 2 TB for $115 / month. 😞

via Twitter Web Client in reply to drwasho

RT @coindesk: Ethereum devs had to reel in a highly anticipated app last week, after “significant” bugs provoked security concerns https://…

via Twitter Web Client

RT @acinq_co: LN vaporware is condensing into actual software 😀 Today we are releasing an early version of Eclair https://t.co/6MWrTC1mhF €¦

via Twitter Web Client

.@factom Chief Scientist Brian Deery implemented a variation of SegWit on his own, well before SegWit was announced. https://t.co/zzycjSsd8a

via Twitter Web Client

@Kosmatos A BU node operator could lower the default EB config to say, 2MB but that risks potentially get forked off the network…

via Twitter Web Client in reply to Kosmatos

@checksum0 To be clear, I’m just trying to define resource bounding in terms that node operators can understand. Good for planning purposes.

via Twitter Web Client in reply to checksum0

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

via Twitter Web Client

@ErolKazan indeed, plus bad things would start to happen long before that size was reached.

via Twitter Web Client in reply to ErolKazan

@MrHodl @eordano *shrugs* anyone is free to activate it and fork off whenever they want.

via Twitter Web Client in reply to MrHodl

Bitcoin Unlimited max block size is 256MB, raising worst case annual node disk usage from 50 Gigabytes ($1.50) to 13 Terabytes ($400.) 😬

via Twitter Web Client

@MadBitcoins It’s unclear what you’re asking because there is no such thing as “@Blockstream Core”

via Twitter Web Client in reply to MadBitcoins