🔖 Title: Standardisation of an unstructured taproot annex 🏷️ Categories: ...

Bitcoin Mailing List

npub15g7…08lk

2023-06-07 23:22:06

🔖 Title: Standardisation of an unstructured taproot annex
🏷️ Categories: bitcoin-dev
👥 Authors:
• Peter Todd ( Peter Todd [ARCHIVE] (npub1m23…2np2) )
• David A. Harding ( David A. Harding [ARCHIVE] (npub16dt…4wrd) )
• Joost Jager ( Joost Jager [ARCHIVE] (npub1asl…fqmx) )
• Greg Sanders ( Greg Sanders [ARCHIVE] (npub1jdl…gh0m) )
🗒️ Conversation Summary: The Bitcoin-dev mailing list discussed the taproot annex feature, which allows for immediate utilization and future flexibility. However, there are potential issues with signature hashes not covering other inputs' annex fields in coinjoin scenarios, and the proposed solution may not align with economic incentives. The annex malleability vector could mislead developers into believing their transactions are immune to replacement, resulting in compromised assumptions. A policy to mitigate annex malleability could mislead developers into thinking their transactions are immune to replacement, when they may not be.
📅 Messages Date Range: 2023-06-02 to 2023-06-03
✉️ Message Count: 11
📚 Total Characters in Messages: 21582

Author Public Key

npub15g7m7mrveqlpfnpa7njke3ccghmpryyqsn87vg8g8eqvqmxd60gqmx08lk

Show more details

Published at

2023-06-07 23:22:06

Kind type

1 Short Text Note

Event JSON

{ "id": "b686717ee8b6c1778c5cebee48da470faaa2069000c176619f95f986554460f4", "pubkey": "a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0", "created_at": 1686180126, "kind": 1, "tags": [ [ "p", "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa" ], [ "p", "d3574a24208f4e3d0821bb4a69a0c3ae842043d444fa5c4a8c49c369918a6fb2" ], [ "p", "ec3fb08b335b94aace30d13181f2ad0280df9bc34f1a99832c4e2da8fb125eb3" ], [ "p", "937f10fc4f78d8676348562d9d886843fbb351d99d6c96423fe9970819962e19" ] ], "content": "🔖 Title: Standardisation of an unstructured taproot annex\n🏷️ Categories: bitcoin-dev\n👥 Authors: \n• Peter Todd ( nostr:npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2 )\n• David A. Harding ( nostr:npub16dt55fpq3a8r6zpphd9xngxr46zzqs75gna9cj5vf8pknyv2d7equx4wrd )\n• Joost Jager ( nostr:npub1aslmpzentw224n3s6yccru4dq2qdlx7rfudfnqevfck637cjt6esswfqmx )\n• Greg Sanders ( nostr:npub1jdl3plz00rvxwc6g2ckemzrgg0amx5wen4kfvs3laxtssxvk9cvsf3gh0m )\n🗒️ Conversation Summary: The Bitcoin-dev mailing list discussed the taproot annex feature, which allows for immediate utilization and future flexibility. However, there are potential issues with signature hashes not covering other inputs' annex fields in coinjoin scenarios, and the proposed solution may not align with economic incentives. The annex malleability vector could mislead developers into believing their transactions are immune to replacement, resulting in compromised assumptions. A policy to mitigate annex malleability could mislead developers into thinking their transactions are immune to replacement, when they may not be.\n📅 Messages Date Range: 2023-06-02 to 2023-06-03\n✉️ Message Count: 11\n📚 Total Characters in Messages: 21582\n", "sig": "92a35c1f2943d00faf6ab1ad08c12ee9d4c4bf4bad91f238a7c35d41b5bb1da6f4484475c0cb00c10d3795f4598742c06b51d56777f2cde8cb15d1b58c21863e" }