š
Original date posted:2016-03-01
š Original message:Bitcoin Core is ready to move towards deployment of a soft fork which will
implement BIP's 68, 112, and 113.
BIP 68 - Relative lock-time using consensus-enforced sequence numbers -
https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki
BIP 112 - CHECKSEQUENCEVERIFY -
https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki
BIP 113 - Median time-past as endpoint for lock-time calculations -
https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki
BIP 113 logic was introduced in the 0.11.2 release as a standardness rule
and BIP 68 and BIP 112 logic has been merged into master*.
What remains to be done is finish testing, merge the logic to activate the
soft forks and backport the code to supported releases.
The exact rollout mechanism is still being finalized but will be
coordinated with the community.
This email is meant to serve as a readiness announcement and confirm that
there are no outstanding concerns.
Thanks,
Alex
* - BIP 68 and BIP 112 logic is only enforced when the tx version is >= 2
which will only become standard with the release of the soft fork code.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160301/f118cd50/attachment.html>;
Alex Morcos [ARCHIVE] /
npub10zā¦3xfzw
2023-06-07 17:49:25
in reply to nevent1qā¦j6nx
Author Public Key
npub10z4xjfgftd3fm9dfu7dw6mkemgyhxgumcmhd7yd0ggjq7rsaw4wqa3xfzwPublished at
2023-06-07 17:49:25Event JSON
{
"id": "517e6f41ca79ee8a2b054c2e46bd644cdc69d2cf00f6c05f188341e7eed083bb",
"pubkey": "78aa6925095b629d95a9e79aed6ed9da0973239bc6eedf11af42240f0e1d755c",
"created_at": 1686160165,
"kind": 1,
"tags": [
[
"e",
"aff16417c9da8817f374d4fff4746557216d9ac8150d08e520603f5039d50bfb",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "š
Original date posted:2016-03-01\nš Original message:Bitcoin Core is ready to move towards deployment of a soft fork which will\nimplement BIP's 68, 112, and 113.\n\nBIP 68 - Relative lock-time using consensus-enforced sequence numbers -\nhttps://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki\nBIP 112 - CHECKSEQUENCEVERIFY -\nhttps://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki\nBIP 113 - Median time-past as endpoint for lock-time calculations -\nhttps://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki\n\nBIP 113 logic was introduced in the 0.11.2 release as a standardness rule\nand BIP 68 and BIP 112 logic has been merged into master*.\nWhat remains to be done is finish testing, merge the logic to activate the\nsoft forks and backport the code to supported releases.\n\nThe exact rollout mechanism is still being finalized but will be\ncoordinated with the community.\n\nThis email is meant to serve as a readiness announcement and confirm that\nthere are no outstanding concerns.\n\nThanks,\nAlex\n\n\n* - BIP 68 and BIP 112 logic is only enforced when the tx version is \u003e= 2\nwhich will only become standard with the release of the soft fork code.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160301/f118cd50/attachment.html\u003e",
"sig": "7dd4ad9d282dc8a6e168026b242b7e03024cc015b5e36ee2df29d0e6fee290f948f97e76441d0d97d29c70336d4e75a7e351afed2ef6c62a9748945f176067cb"
}