{"type":"rich","version":"1.0","author_name":"npub1lhe3qfx2q5m7mq5d39waepf9lzhsy0cdey66svn63fyk6rt6n7ps7zg7ed","author_url":"https://nostr.ae/npub1lhe3qfx2q5m7mq5d39waepf9lzhsy0cdey66svn63fyk6rt6n7ps7zg7ed","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-09-27\n📝 Original message:On Sun, Sep 27, 2015 at 7:50 PM, Peter Todd via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e 10) Waiting for nVersion bits and CHECKSEQUENCEVERIFY will significantly\n\u003e     delay deployment of CLTV\n\u003e\n\u003e It's been proposed multiple times that we wait until we can do a single\n\u003e soft-fork with CSV using the nVersion bits mechanism.\n\u003e\n\u003e nVersion bits doesn't even have an implementation yet, nor has solid\n\u003e consensus been reached on the exact semantics of how nVersion bits\n\u003e should work.\n\n\nSmall correction, the suggestion is to aim to roll out CLTV+CSV together by\n0.12 release, using IsSuperMajority() (or versionbits if it is ready by\nthen). If CSV is not ready by then, we'd just roll out CLTV.\n\nHowever, the CSV related pull requests are ready for final review and if\nthat can happen soon I don't see why we wouldn't roll CLTV+CSV out together\nbefore 0.12. A considerable amount of time, discussion and iterations have\noccurred for the related PRs and I believe they are at the point of\nconsensus modulo final review before merging.\n\nReferences:\n\nMempool-only sequence number constraint verification\nhttps://github.com/bitcoin/bitcoin/pull/6312\n\nMempool-only CHECKSEQUENCEVERIFY\nhttps://github.com/bitcoin/bitcoin/pull/6564\n\nMempool-only Median time-past as endpoint for lock-time calculations\nhttps://github.com/bitcoin/bitcoin/pull/6566\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150927/81513026/attachment.html\u003e"}