🔖 Title: Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
🏷️ Categories: bitcoin-dev
👥 Authors:
• Christopher Allen ( Christopher Allen [ARCHIVE] (npub19g4…t5d0) )
• Claus Ehrenberg ( Claus Ehrenberg [ARCHIVE] (npub1a8c…3wff) )
• Rijndael ( Rijndael [ARCHIVE] (npub1zhs…3hc5) )
• Anthony Towns ( Anthony Towns [ARCHIVE] (npub17rl…9l2h) )
• Aymeric Vitte ( Aymeric Vitte [ARCHIVE] (npub15fc…5grz) )
• Peter Todd ( Peter Todd [ARCHIVE] (npub1m23…2np2) )
• Andrew Poelstra ( Andrew Poelstra [ARCHIVE] (npub1ae2…5t04) )
• Russell O'Connor ( Russell O'Connor [ARCHIVE] (npub1dw8…plrw) )
• Kostas Karasavvas ( Kostas Karasavvas [ARCHIVE] (npub1tqa…3e9m) )
🗒️ Conversation Summary: The debate is on the most efficient way to place 64 bytes into the Bitcoin blockchain, with suggestions including traditional OP_RETURN and spent taproot transactions. The current standard for OP_RETURN in Bitcoin is a maximum of 80 bytes and one output per transaction, but some suggest increasing the size of OP_RETURN to support a hash, signature, and metadata. There is ongoing discussion on changing the OP_RETURN size in Bitcoin, but ultimately requires code changes and community consensus for implementation.
📅 Messages Date Range: 2023-01-31 to 2023-02-18
✉️ Message Count: 34
📚 Total Characters in Messages: 75198
Bitcoin Mailing List
npub15g…x08lk
2023-06-07 23:18:53
Author Public Key
npub15g7m7mrveqlpfnpa7njke3ccghmpryyqsn87vg8g8eqvqmxd60gqmx08lkPublished at
2023-06-07 23:18:53Event JSON
{
"id": "db7e30240de322a59459e6f6d735c7f019f73c8194514d70467812fbd7606451",
"pubkey": "a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0",
"created_at": 1686179933,
"kind": 1,
"tags": [
[
"p",
"2a2be7532ec03e16fa6ff38360d30cc714893870cbd9fafbefeb1df2df858c4d"
],
[
"p",
"e9f167f600028858be9e00a54ff64ac6bdb1b61076a8b3669619ea88f4ef62a6"
],
[
"p",
"15e05de303b72be9f03d36f4f809672aab99fbb970537f1abd29c17ad3f2e282"
],
[
"p",
"f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab"
],
[
"p",
"a2711d6616d348a3542bb2a791a9e51fcbc7b7d1d20652e5abe16d3e179321df"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
],
[
"p",
"ee55eb03423bd4db01d5c92ad434d52c602d9da1de37ed37cc5bf7d2a13a4cab"
],
[
"p",
"6b8e77368804013d7126ba4b77c7963bcfeff909135791531097d7a0f03ca85d"
],
[
"p",
"583b87ea66416acca0bd5993658d2d707eaed613728cd1ae8acda872c6539dac"
]
],
"content": "🔖 Title: Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH\n🏷️ Categories: bitcoin-dev\n👥 Authors: \n• Christopher Allen ( nostr:npub19g47w5ewcqlpd7n07wpkp5cvcu2gjwrse0vl47l0avwl9hu933xsqct5d0 )\n• Claus Ehrenberg ( nostr:npub1a8ck0asqq2y93057qzj5laj2c67mrdssw65txe5kr84g3a80v2nqye3wff )\n• Rijndael ( nostr:npub1zhs9mccrku47nupaxm60szt8924en7aewpfh7x4a98qh45lju2pq7x3hc5 )\n• Anthony Towns ( nostr:npub17rld56k4365lfphyd8u8kwuejey5xcazdxptserx03wc4jc9g24stx9l2h )\n• Aymeric Vitte ( nostr:npub15fc36esk6dy2x4ptk2ner209rl9u0d736gr99edtu9knu9uny80s4g5grz )\n• Peter Todd ( nostr:npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2 )\n• Andrew Poelstra ( nostr:npub1ae27kq6z802dkqw4ey4dgdx493szm8dpmcm76d7vt0ma9gf6fj4svz5t04 )\n• Russell O'Connor ( nostr:npub1dw88wd5gqsqn6ufxhf9h03uk8087l7gfzdtez5csjlt6pupu4pwsj8plrw )\n• Kostas Karasavvas ( nostr:npub1tqac06nxg94veg9atxfktrfdwpl2a4snw2xdrt52ek5893jnnkkqey3e9m )\n🗒️ Conversation Summary: The debate is on the most efficient way to place 64 bytes into the Bitcoin blockchain, with suggestions including traditional OP_RETURN and spent taproot transactions. The current standard for OP_RETURN in Bitcoin is a maximum of 80 bytes and one output per transaction, but some suggest increasing the size of OP_RETURN to support a hash, signature, and metadata. There is ongoing discussion on changing the OP_RETURN size in Bitcoin, but ultimately requires code changes and community consensus for implementation.\n📅 Messages Date Range: 2023-01-31 to 2023-02-18\n✉️ Message Count: 34\n📚 Total Characters in Messages: 75198\n",
"sig": "b9ba32f10300b0c3e9a82e9ef1aad9eaba22af0d889483ec6a8b0873eff0321d47671c4d40872fca7174b32ff7c9b1166e478182d413598f1b7d90619d803bf7"
}