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

August 23rd, 2017

@freedomstream01 SegWit sends use less legacy block space and thus have to pay less fees in order to be competitive in the tx fee market.

via Twitter Web Client in reply to freedomstream01

@freedomstream01 Not automatically. Generally you’d create an on-chain SegWit transaction as an anchor for off-chain SegWit transactions.

via Twitter Web Client in reply to freedomstream01

Payment channel updates conducted via Twitter. Pretty nifty! Thread: twitter.com/FedericoTenga/…

via Twitter Web Client

pwuille I’m the proud sender of the 3rd SegWit transaction ever: smartbit.com.au/tx/c586389e5e4… Thanks everyone who helped us get this far!

via Twitter Web Client (retweeted on 10:01 PM, Aug 23rd, 2017 via Twitter Web Client)

Segregated Witness is now activated on Bitcoin mainnet. Onward! pic.twitter.com/kh2IJHlsyL

via Twitter Web Client

Prediction: block # 481824 is going to contain some abnormally high fee transactions. 🤓

via Twitter for Android

@laurashin @mriou @derek_hsue @zaoyang Google Fi has no CSRs who can override your PIN. Lack of customer service for the win!

via Twitter Web Client in reply to laurashin

murchandamus I just published “BitGo SegWit Launch” blog.bitgo.com/bitgo-segwit-l… Thanks to @arikaleph

via Twitter Web Client (retweeted on 4:54 PM, Aug 23rd, 2017 via Twitter Web Client)

📈Bitcoin bubble📉
📈Altcoin bubble📉
📈Bitcoin bubble📉
📈ICO bubble📉
📈Bitcoin bubble📉
📈Bitcoin fork bubble📉
History doesn’t repeat; it rhymes.

via Twitter Web Client

roasbeef We’ve created a site with tutorials, resources, and documentation for application developers: dev.lightning.community

via Twitter for Mac (retweeted on 3:58 PM, Aug 23rd, 2017 via Twitter Web Client)

lightning Announcing the 0.3 release of LND alpha! Now with feature completeness, neutrino light client, LTC, spec compliance. twitter.com/roasbeef/statu…

via Twitter Web Client (retweeted on 3:57 PM, Aug 23rd, 2017 via Twitter Web Client)

Is there a segwit.party in the Bay Area?

via Twitter Web Client

@DipierroAnthony @Sir_Lebowski All BitGo addresses are P2SH. LTC P2SH addresses are same format as BTC. Though now..twitter.com/i/web/status/9…mh

via Twitter Web Client in reply to DipierroAnthony

@cryptorush All BitGo addresses are P2SH. LTC P2SH addresses are same format as BTC. Though now there is a new vers..twitter.com/i/web/status/9…A8

via Twitter Web Client in reply to cryptorush

@scottshapiro Not if the two different blockchain protocols use the /exact/ same address format. Check out blog.trezor.io/litecoins-new-…

via Twitter Web Client in reply to scottshapiro

@scottshapiro Since crypto assets use push-style transactions, you can’t reject a received transaction. Only real p..twitter.com/i/web/status/9…M1

via Twitter Web Client in reply to scottshapiro

@Sir_Lebowski They can all be recovered, it’s just a painful manual process.

via Twitter Web Client in reply to Sir_Lebowski

@jt_mot2016 Because all BitGo BTC addresses are mirrored on BCH. They are valid from the protocol / blockchain poin..twitter.com/i/web/status/9…0f

via Twitter for Android in reply to jt_mot2016

LTC ➡️ BTC issue would be solved if the rest of the ecosystem would upgrade to M prefixed LTC P2SH addresses… 😒 twitter.com/lopp/status/90…

via Twitter for Android

BitGo sometimes sees users send BTC to LTC addresses. Now seeing many sending BCH to BTC. I suspect B2X will cause even greater confusion.

via Twitter for Android

@ErikVoorhees Deja vu! Well, if Bitcoin Cash could go from weak opt-in to strong default replay protection in 1 wee..twitter.com/i/web/status/9…gJ

via Twitter for Android in reply to ErikVoorhees

rusty_twit I just published “The Consensus Path To A Bitcoin Hard Fork: Part 1” medium.com/p/the-consensu…

via Medium (retweeted on 11:08 AM, Aug 23rd, 2017 via Twitter for Android)