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

April 4th, 2017

@WahWhoWah Still pretty accurate, though check out my latest project: medium.com/@lopp/announci…

via Twitter for Android in reply to WahWhoWah

TriangleBitcoin We’re live with @zooko, learning about @zcashco and on-chain cryptographic privacy! youtu.be/OZu4u_5L0l8

via Twitter for Android (retweeted on 7:04 PM, Apr 4th, 2017 via Twitter for Android)

@lightcoin Though I’m not entirely clear how it would work with extension blocks; presumably a new address type is required.

via Twitter Web Client in reply to lightcoin

@lightcoin The recipient is the one who generates an address for encumbering an output, thus they “choose” how the..twitter.com/i/web/status/8…Ne

via Twitter Web Client in reply to lightcoin

@lightcoin Though to be fair, you’re only trusting miners WRT to the new tx types. So if you don’t use them, you aren’t trusting miners.

via Twitter Web Client in reply to lightcoin

@dgenr818 @rogerkver Are you saying there’s no urgency to deploy scalability solutions for Bitcoin? We should striv..twitter.com/i/web/status/8…iu

via Twitter Web Client in reply to dgenr818

@jgarzik @rogerkver Seems to me there will /always/ be something better on the horizon. If we scrap a year of effor..twitter.com/i/web/status/8…WU

via Twitter Web Client in reply to lopp

@jgarzik @rogerkver And of course, there’s no requirement for all applications to add support in order for other ap..twitter.com/i/web/status/8…BL

via Twitter Web Client in reply to lopp

@jgarzik @rogerkver SegWit rollout phases had to go from: Proposal => Reference Implementation => Library support =..twitter.com/i/web/status/8…KP

via Twitter Web Client in reply to jgarzik

@richcollins @iang_fc Backwards compatible protocol upgrades are necessarily more complex in terms of code in order..twitter.com/i/web/status/8…2i

via Twitter Web Client in reply to richcollins

@rogerkver OTOH, if we’re asking “can we throw away SegWit and spend another year building a new approach” then sur..twitter.com/i/web/status/8…Qo

via Twitter Web Client in reply to lopp

@rogerkver Sunk Costs Fallacy requires that more resources must be expended to complete an ongoing project, but SegWit is already completed.

via Twitter Web Client in reply to rogerkver

@iang_fc Right; one shouldn’t add complexity for the sake of adding complexity. It should be a trade-off in return for beneficial gains.

via Twitter Web Client in reply to iang_fc

TriangleBitcoin Excited to host @zooko at 7PM EST tonight to learn more about @zcashco! Livestream will be available here: youtu.be/OZu4u_5L0l8

via Twitter for Android (retweeted on 10:07 AM, Apr 4th, 2017 via Twitter Web Client)

@britesense Yep, there are plenty of other issues also in play. 😬

via Twitter Web Client in reply to britesense

@fersecchi It’s a more substantial change because now you’d have to keep track of 2 separate UTXO sets. Likely creates compatibility issues.

via Twitter Web Client in reply to fersecchi

@mikevanrossum Exactly; I’ve seen far too many people treat is as a binary factor.

via Twitter Web Client in reply to mikevanrossum

However, “we shouldn’t add feature X because it adds complexity” is a non-argument. Every feature adds complexity. twitter.com/lopp/status/84…

via Twitter Web Client

Given complexity of Extension Blocks, I’d expect at least as long for ecosystem to implement as SegWit: a year, give or take.

via Twitter Web Client

As such, an appropriate alternative name for Extension Blocks might be “Segregated Unspent Transaction Output Set” 😬 twitter.com/lopp/status/84…

via Twitter Web Client

Segregated Witness moves txn signatures outside of legacy block space. Extension Blocks move entire txn outside of legacy block space.

via Twitter Web Client