📅 Original date posted:2023-08-03
🗒️ Summary of this message: The author of the pull request intends to remove restrictions on OP_Return outputs, despite potential transaction pinning vectors.
📝 Original message:
https://github.com/bitcoin/bitcoin/pull/28130
Sjors Provoost suggested that I email this mailing list as notice of my intent
to get a pull-req merged that would remove the arbitrary 80-byte, 1 output /
tx, standardness restrictions on OP_Return outputs. His rationale was that
removing these standardness restrictions could potentially open up additional
transaction pinning(1) vectors. Since this is a potential problem with any
relaxation of standardness rules, I don't consider this to be an important
concern. But consider this email your notice.
At least some miners appear to be mining non-bitcoin-core-standard
transactions. So with respect to the hash power of those miners these pinning
vectors may in fact exist already.
# References
1) https://bitcoinops.org/en/topics/transaction-pinning/
--
https://petertodd.org 'peter'[:-1]@petertodd.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230803/33786fbc/attachment-0001.sig>;
Peter Todd [ARCHIVE] /
npub1m2…a2np2
2023-08-03 12:35:35
in reply to nevent1q…ndlu
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-08-03 12:35:35Event JSON
{
"id": "1b1438f9d683acb78eb9015978e4e37e4666d7f0192e4890dcefde9c66656b51",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1691066135,
"kind": 1,
"tags": [
[
"e",
"44921983c1528fb9634a706635d283e97ae3ba5ad2863f78e5d881712ad31987",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2023-08-03\n🗒️ Summary of this message: The author of the pull request intends to remove restrictions on OP_Return outputs, despite potential transaction pinning vectors.\n📝 Original message:\nhttps://github.com/bitcoin/bitcoin/pull/28130\n\nSjors Provoost suggested that I email this mailing list as notice of my intent\nto get a pull-req merged that would remove the arbitrary 80-byte, 1 output /\ntx, standardness restrictions on OP_Return outputs. His rationale was that\nremoving these standardness restrictions could potentially open up additional\ntransaction pinning(1) vectors. Since this is a potential problem with any\nrelaxation of standardness rules, I don't consider this to be an important\nconcern. But consider this email your notice.\n\nAt least some miners appear to be mining non-bitcoin-core-standard\ntransactions. So with respect to the hash power of those miners these pinning\nvectors may in fact exist already.\n\n\n# References\n\n1) https://bitcoinops.org/en/topics/transaction-pinning/\n\n-- \nhttps://petertodd.org 'peter'[:-1]@petertodd.org\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230803/33786fbc/attachment-0001.sig\u003e",
"sig": "64a9fc543e398caf755afdca8314894849bcca12d66658b32b4ccc5d87d8edf5226e9c07692d923d3d285815b47f4c05eda303073b5dd9270b7f551ce1f0facf"
}