<oembed><type>rich</type><version>1.0</version><author_name>npub1ts9hljj3l4yrpdxelpqdup3l46lw40fmkhw3rr0feh6s5ml247vqerfl5y</author_name><author_url>https://nostr.ae/npub1ts9hljj3l4yrpdxelpqdup3l46lw40fmkhw3rr0feh6s5ml247vqerfl5y</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-12-08&#xA;📝 Original message:On Mon, Dec 07, 2015 at 10:02:17PM +0000, Gregory Maxwell via bitcoin-dev wrote:&#xA;&gt; The Scaling Bitcoin Workshop in HK is just wrapping up. Many fascinating&#xA;&gt; proposals were presented. I think this would be a good time to share my&#xA;&gt; view of the near term arc for capacity increases in the Bitcoin system. I&#xA;&gt; believe we’re in a fantastic place right now and that the community&#xA;&gt; is ready to deliver on a clear forward path with a shared vision that&#xA;&gt; addresses the needs of the system while upholding its values.&#xA;&#xA;Thanks for writing this up. Putting the progress, ongoing work and plans related&#xA;to scaling in context, in one place, was badly needed.&#xA;&#xA;&gt; TL;DR:  I propose we work immediately towards the segwit 4MB block&#xA;&gt; soft-fork which increases capacity and scalability, and recent speedups&#xA;&gt; and incoming relay improvements make segwit a reasonable risk. BIP9&#xA;&gt; and segwit will also make further improvements easier and faster to&#xA;&gt; deploy. We’ll continue to set the stage for non-bandwidth-increase-based&#xA;&gt; scaling, while building additional tools that would make bandwidth&#xA;&gt; increases safer long term. Further work will prepare Bitcoin for further&#xA;&gt; increases, which will become possible when justified, while also providing&#xA;&gt; the groundwork to make them justifiable.&#xA;&#xA;Sounds good to me.&#xA;&#xA;There are multiple ways to get involved in ongoing work, where the community&#xA;can help to make this happen sooner:&#xA;&#xA;- Review the versionbits BIP https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki:&#xA;&#xA;  - Compare and test with implementation: https://github.com/bitcoin/bitcoin/pull/6816&#xA;&#xA;- Review CSV BIPs (BIP68 https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki / &#xA;       BIP112 https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki),&#xA;&#xA;  - Compare and test implementation: &#xA;&#xA;    https://github.com/bitcoin/bitcoin/pull/6564  BIP-112: Mempool-only CHECKSEQUENCEVERIFY&#xA;    https://github.com/bitcoin/bitcoin/pull/6312  BIP-68: Mempool-only sequence number constraint verification &#xA;    https://github.com/bitcoin/bitcoin/pull/7184  [WIP] Implement SequenceLocks functions for BIP 68&#xA;&#xA;- Segwit BIP is being written, but has not yet been published.&#xA;&#xA;  - Gregory linked to an implementation but as he mentions it is not completely&#xA;    finished yet. ETA for a Segwit testnet is later this month, then you can test as well.&#xA;&#xA;Wladimir</html></oembed>