📅 Original date posted:2016-07-31
📝 Original message:Your thoughts are sought on this simple proposal to allow transaction
authors to restrict execution to fewer than all blockchain forks where
the transaction would otherwise be valid.
Proposal
Node implementations select a bit from among the upper 8 bits of the
transaction version space to enforce as a hard fork opt-out bit.
To specify that a transaction NOT be mined by nodes that enforce a
particular bit, authors set that bit in the transaction version.
Opt-out is enforced by consensus among nodes enforcing each bit.
An implementation will relay, process and mine transactions that opt out
of other blockchain forks; just not those that opt out of its own fork.
Notes
Example: Via soft fork, all implementations may begin enforcing hard
fork opt-out bit 30. Post soft fork, setting this bit would make a
transaction invalid, unless a fork emerges that has stopped enforcing
bit 30.
Example: BIP109 implementations may stop enforcing bit 30 and begin
enforcing bit 28 when the BIP109 hard fork is activated for a chain they
are tracking.
Enforcing more than one hard fork opt-out bit would imply that an
implementation is actively participating in building more than one
blockchain fork, and therefore providing a way to opt out of each.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160731/7b1a2154/attachment.sig>;
Tom Harding [ARCHIVE] /
npub1ms…pmwjy
2023-06-07 17:52:06
in reply to nevent1q…djd9
Author Public Key
npub1msef5qkfwz4t7qacwxz775wgdtlytph78g2g2z903x90874u263sypmwjyPublished at
2023-06-07 17:52:06Event JSON
{
"id": "f71e20796f7a4167e3b919b98b6ca132c8025661dbaf87d998a84ef6447dfad6",
"pubkey": "dc329a02c970aabf03b87185ef51c86afe4586fe3a148508af898af3fabc56a3",
"created_at": 1686160326,
"kind": 1,
"tags": [
[
"e",
"d59af9f05ad4b5b6a52d0237e25782c742ce4b66a47422f757134e5afcd9d4c8",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2016-07-31\n📝 Original message:Your thoughts are sought on this simple proposal to allow transaction\nauthors to restrict execution to fewer than all blockchain forks where\nthe transaction would otherwise be valid.\n\n\nProposal\n\nNode implementations select a bit from among the upper 8 bits of the\ntransaction version space to enforce as a hard fork opt-out bit.\n\nTo specify that a transaction NOT be mined by nodes that enforce a\nparticular bit, authors set that bit in the transaction version.\nOpt-out is enforced by consensus among nodes enforcing each bit.\n\nAn implementation will relay, process and mine transactions that opt out\nof other blockchain forks; just not those that opt out of its own fork.\n\n\nNotes\n\nExample: Via soft fork, all implementations may begin enforcing hard\nfork opt-out bit 30. Post soft fork, setting this bit would make a\ntransaction invalid, unless a fork emerges that has stopped enforcing\nbit 30.\n\nExample: BIP109 implementations may stop enforcing bit 30 and begin\nenforcing bit 28 when the BIP109 hard fork is activated for a chain they\nare tracking.\n\nEnforcing more than one hard fork opt-out bit would imply that an\nimplementation is actively participating in building more than one\nblockchain fork, and therefore providing a way to opt out of each.\n\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 819 bytes\nDesc: OpenPGP digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160731/7b1a2154/attachment.sig\u003e",
"sig": "f8512caadb22794c37aede2d6dd1d68b76a3b19474c825ad1a642c012dc6569b17beac13fd9ed8f035ac77627c1fd7fac82ddd2e4d49ffea04d3e65b2cc0e638"
}