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

March 2nd, 2017

@kristovatlas I was very interested in earning a commission, but then I remembered I’m not in Europe. Oh well!

via Twitter Web Client in reply to kristovatlas

#ThrowbackThursday to my first @BitGo post. Just started writing a new “challenges of” article! 🤔 https://t.co/suus4zZD2c

via Twitter Web Client

@DelRayMan @coindesk @The_DTCC @Hyperledger Situation hasn’t changed since I last mentioned it :-/ https://t.co/cCvcKBZerL

via Twitter Web Client

Thanks for playing, everybody - you’re all correct! Everyone who has a vested interest can /try/ to influence Bitco… https://t.co/siLNpFh5vH

via Twitter Web Client

@meeDamian @eric_lombrozo @BitcoinBelle @bitcoin_sm @bitcoincoreorg I’m sure you can ask /r/btc and they’ll compile one for you.

via Twitter Web Client in reply to meeDamian

@gavinandresen @AaronvanW Yeah I don’t want anyone wasting time rehashing; was wondering if you have unique perspectives we haven’t heard.

via Twitter Web Client in reply to gavinandresen

@gavinandresen One ripple effect I could see is that the meaning / security of a “confirmation” could change due to services w/diff configs.

via Twitter Web Client in reply to gavinandresen

@gavinandresen Changing likelihood of reorgs, creating unbounded CONOP, incentivizing cartel-like mining behavior, misc ripple effects…

via Twitter Web Client in reply to gavinandresen

@eric_lombrozo @BitcoinBelle @bitcoin_sm @bitcoincoreorg There’s a whole list of grievances that have turned technical debate into politics.

via Twitter Web Client in reply to eric_lombrozo

@gavinandresen I’d be quite interested in seeing your long form argument of why Emergent Consensus is safe & why nodes should give up power.

via Twitter Web Client in reply to gavinandresen

@jchirak The cliffs just mean that my node was restarted or crashed, which is thankfully pretty rare.

via Twitter Web Client in reply to jchirak