📅 Original date posted:2015-04-15 📝 Original message:Hi, Would it be wise to ...

s7r [ARCHIVE] /

npub1j3u…wg9h

2023-06-07 15:32:29

in reply to nevent1q…ht3y

📅 Original date posted:2015-04-15
📝 Original message:Hi,

Would it be wise to add a consensus rule like the one we have for blocks,

(if > 75% from last 1000 blocks are version 'n' mark version 'n' as
standard for blocks and if > 95% from the last 1000 blocks are version
'n' mark previous block versions as invalid)

but for transaction versions? In simple terms, if > 75% from all the
transactions in the latest 1000 blocks are version 'n', mark all
previous transaction versions as non-standard and if > 95% from all the
transactions in the latest 1000 blocks are version 'n' mark all previous
transaction versions as invalid.

At this moment, the standard in consensus is v1, but nothing is enforced
in the network related to transaction versions.

Regarding BIP62, as it can be read here [0] it is said that it requires
v2 transactions. It is also said that transaction version 2 will be
skipped and jump directly to v3, for an even version for transactions
and blocks (?). Might as well add the rule for invalidating previous
transaction versions if the majority updates - could this break anything
or affect functionality in any way?

BIP62 adds a newer transaction version which is optional and does not
mark previous v1 as non-standard or invalid. This means bitcoin core
will treat both v1 and v2/v3 transactions as standard and relay/mine
them with the same priority, regardless of the tx version?

Thanks.

[0]
https://bitcoin.stackexchange.com/questions/35904/how-much-of-bip-62-dealing-with-malleability-has-been-implemented

Author Public Key

npub1j3u42vq63qzs2nyddgkf4s4t7pa85x855vas54e6yauxsvpf2wcsacwg9h

Show more details

Published at

2023-06-07 15:32:29

Kind type

1 Short Text Note

Event JSON

{ "id": "4b0fe416c4870d2deef5d426d7cddc0ea072d5d180bc4fd29dd5c163b16472dd", "pubkey": "947955301a8805054c8d6a2c9ac2abf07a7a18f4a33b0a573a277868302953b1", "created_at": 1686151949, "kind": 1, "tags": [ [ "e", "8b8a2347eb8a1165154b18f1aa6b1f8a0b99712f1e1f9461e574d86e0b7c9986", "", "reply" ], [ "p", "a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0" ] ], "content": "📅 Original date posted:2015-04-15\n📝 Original message:Hi,\n\nWould it be wise to add a consensus rule like the one we have for blocks,\n\n(if \u003e 75% from last 1000 blocks are version 'n' mark version 'n' as\nstandard for blocks and if \u003e 95% from the last 1000 blocks are version\n'n' mark previous block versions as invalid)\n\nbut for transaction versions? In simple terms, if \u003e 75% from all the\ntransactions in the latest 1000 blocks are version 'n', mark all\nprevious transaction versions as non-standard and if \u003e 95% from all the\ntransactions in the latest 1000 blocks are version 'n' mark all previous\ntransaction versions as invalid.\n\nAt this moment, the standard in consensus is v1, but nothing is enforced\nin the network related to transaction versions.\n\nRegarding BIP62, as it can be read here [0] it is said that it requires\nv2 transactions. It is also said that transaction version 2 will be\nskipped and jump directly to v3, for an even version for transactions\nand blocks (?). Might as well add the rule for invalidating previous\ntransaction versions if the majority updates - could this break anything\nor affect functionality in any way?\n\nBIP62 adds a newer transaction version which is optional and does not\nmark previous v1 as non-standard or invalid. This means bitcoin core\nwill treat both v1 and v2/v3 transactions as standard and relay/mine\nthem with the same priority, regardless of the tx version?\n\n\nThanks.\n\n[0]\nhttps://bitcoin.stackexchange.com/questions/35904/how-much-of-bip-62-dealing-with-malleability-has-been-implemented", "sig": "b40b61c73c15f773e26ece78b4319323403c5a4783fe1276265fb1a3a38d0f635e751b8e1960ec05e54f2e69d696827fdb8913a4fd6880d55616b284e9df8b67" }