@WahWhoWah Still pretty accurate, though check out my latest project: https://t.co/Gmefbjq1mt
TriangleBitcoin We’re live with @zooko, learning about @zcashco and on-chain cryptographic privacy! youtu.be/OZu4u_5L0l8
@lightcoin Though I’m not entirely clear how it would work with extension blocks; presumably a new address type is required.
@lightcoin The recipient is the one who generates an address for encumbering an output, thus they “choose” how the… https://t.co/60WTxdIENe
@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.
@dgenr818 @rogerkver Are you saying there’s no urgency to deploy scalability solutions for Bitcoin? We should striv… https://t.co/Wx59eU4qiu
@jgarzik @rogerkver Seems to me there will /always/ be something better on the horizon. If we scrap a year of effor… https://t.co/zShBI8JWWU
@jgarzik @rogerkver And of course, there’s no requirement for all applications to add support in order for other ap… https://t.co/h9r5iGKLBL
@jgarzik @rogerkver SegWit rollout phases had to go from: Proposal => Reference Implementation => Library support =… https://t.co/pMUV6mztKP
@richcollins @iang_fc Backwards compatible protocol upgrades are necessarily more complex in terms of code in order… https://t.co/CQ2DVC5N2i
@rogerkver OTOH, if we’re asking “can we throw away SegWit and spend another year building a new approach” then sur… https://t.co/FofBTnNDQo
@rogerkver Sunk Costs Fallacy requires that more resources must be expended to complete an ongoing project, but SegWit is already completed.
@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.
TriangleBitcoin Excited to host @zooko at 7PM EST tonight to learn more about @zcashco! Livestream will be available here: youtu.be/OZu4u_5L0l8
@britesense Yep, there are plenty of other issues also in play. 😬
@fersecchi It’s a more substantial change because now you’d have to keep track of 2 separate UTXO sets. Likely creates compatibility issues.
@mikevanrossum Exactly; I’ve seen far too many people treat is as a binary factor.
However, “we shouldn’t add feature X because it adds complexity” is a non-argument. Every feature adds complexity. https://t.co/kwAeRwJRGt
Given complexity of Extension Blocks, I’d expect at least as long for ecosystem to implement as SegWit: a year, give or take.
As such, an appropriate alternative name for Extension Blocks might be “Segregated Unspent Transaction Output Set” 😬 https://t.co/T4DlZlKcMb
Segregated Witness moves txn signatures outside of legacy block space. Extension Blocks move entire txn outside of legacy block space.