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

March 14th, 2017

@josephjpeters @TaylorGerring As far as I can tell @gavinandresen is uninvolved in the actual BU development process github.com/gavinandresen

via Twitter Web Client in reply to josephjpeters

TriangleBitcoin We’re honored to have @zooko speak about @zcashco on April 4th! The event will be livestreamed (link on meetup) meetu.ps/e/CvNGv/5nnm4/d

via Twitter for Android (retweeted on 7:26 PM, Mar 14th, 2017 via Twitter Web Client)

Disappointed to see doctored image (left) in @GAndrewStone’s post about a BU vulnerability. Doesn’t even sum to 100..twitter.com/i/web/status/8…MV

via Twitter Web Client

@desantis @kristovatlas Bitcoin Core uses the same mechanism for banning misbehavior peers, so I’m not sure why this matters.

via Twitter Web Client in reply to desantis

@desantis @kristovatlas Um, what’s the point? If a BU node has been patched to ban you, they no longer have the crash vuln.

via Twitter Web Client in reply to desantis

@paddyncl A single bug like this can only take down the implementation containing the bug.

via Twitter Web Client in reply to paddyncl

@desantis Anyone using the exploit wouldn’t be able to use it against nodes to which they couldn’t make a direct connection.

via Twitter Web Client in reply to desantis

@Excellion No need to be so negative. Look at the bright side: it’s a security feature. You can’t be attacked if you’re offline. 👍🏻

via Twitter Web Client in reply to Excellion

Greg Maxwell claims vulnerabilities in Bitcoin Unlimited more severe than the one used to crash 70% of nodes today. reddit.com/r/btc/comments…

via Twitter Web Client

@Ethan_Heilman @kyletorpey @kristovatlas AFAIK, BU has not implemented an Ethereum-style auto-update feature so I’d say it’s proof of PoC.

via Twitter Web Client in reply to Ethan_Heilman

Keep an eye on the Bitcoin Unlimited node charts. Someone may have begun exploiting the crash vulnerability…twitter.com/i/web/status/8…qE

via Twitter Web Client

@least_nathan @alistairmilne Tough one b/c only devs really care and complexity is relative / subjective. Aerospace code is pretty complex.

via Twitter Web Client in reply to least_nathan

@kristovatlas Looks to me like a GET_XTHIN command + a non-XTHIN inv.type will crash here github.com/BitcoinUnlimit…

via Twitter Web Client in reply to kristovatlas

Side effect of insufficient collaboration during peer review process. Only one reviewer on the pull request. twitter.com/petertoddbtc/s…

via Twitter Web Client

@least_nathan @alistairmilne I suppose you could argue that harming fungibility of anyone harms fungibility for everyone.

via Twitter Web Client in reply to least_nathan

@BitcoinBelle @Twitter Ah, to be clear I meant the people you follow yourself. So you can decide if you should unfollow high noise accounts.

via Twitter Web Client in reply to BitcoinBelle

When viewing the @Twitter “following” user list, would be helpful if you could sort accounts by tweet volume to help determine signal/noise.

via Twitter Web Client

@alistairmilne Ideally, every soft fork regardless of if it benefits you. Example: few people use P2SH but entire business are built on it.

via Twitter Web Client in reply to alistairmilne

If you want to see progress in Bitcoin’s evolution, you should support any change that doesn’t harm you.

via Twitter Web Client

My favorite underrated @brave feature: ability to hover over a tab and get temporary focus w/o clicking on it. Helpful when many tabs open.

via Twitter Web Client