📅 Original date posted:2023-01-31
🗒️ Summary of this message: Which is better for placing 64 bytes into the Bitcoin blockchain: traditional OP_RETURN or spent taproot transaction? Debate on safety and uncensorability.
📝 Original message:All other things being equal, which is better if you need to place a
64-bytes into the Bitcoin blockchain? A traditional OP_RETURN or a spent
taproot transaction such as:
OP_FALSE
OP_IF
OP_PUSH my64bytes
OP_ENDIF
I know that the anti-OP_RETURN folk would say “neither.” But if there was
no other choice for a particular protocol, such as a timestamp or a
commitment, which is better? Or is there a safer place to put 64 bytes that
is more uncensorable but also does not clog UTXO space, only spent
transaction `-txindex` space?
My best guess was that the taproot method is better, but I suspect there
might be some who disagree. I'd love to hear all sides.
-- Christopher Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230131/cac8f8b3/attachment.html>;
Christopher Allen [ARCHIVE] /
npub19g…ct5d0
2023-06-07 23:18:53
in reply to nevent1q…6azr
Author Public Key
npub19g47w5ewcqlpd7n07wpkp5cvcu2gjwrse0vl47l0avwl9hu933xsqct5d0Published at
2023-06-07 23:18:53Event JSON
{
"id": "38db739c56c6894572a30fdcaa34fe5cfa3549378e6fb74cf4fff2e6885fb781",
"pubkey": "2a2be7532ec03e16fa6ff38360d30cc714893870cbd9fafbefeb1df2df858c4d",
"created_at": 1686179933,
"kind": 1,
"tags": [
[
"e",
"db7e30240de322a59459e6f6d735c7f019f73c8194514d70467812fbd7606451",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2023-01-31\n🗒️ Summary of this message: Which is better for placing 64 bytes into the Bitcoin blockchain: traditional OP_RETURN or spent taproot transaction? Debate on safety and uncensorability.\n📝 Original message:All other things being equal, which is better if you need to place a\n64-bytes into the Bitcoin blockchain? A traditional OP_RETURN or a spent\ntaproot transaction such as:\n\nOP_FALSE\nOP_IF\nOP_PUSH my64bytes\nOP_ENDIF\n\nI know that the anti-OP_RETURN folk would say “neither.” But if there was\nno other choice for a particular protocol, such as a timestamp or a\ncommitment, which is better? Or is there a safer place to put 64 bytes that\nis more uncensorable but also does not clog UTXO space, only spent\ntransaction `-txindex` space?\n\nMy best guess was that the taproot method is better, but I suspect there\nmight be some who disagree. I'd love to hear all sides.\n\n-- Christopher Allen\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230131/cac8f8b3/attachment.html\u003e",
"sig": "42ce1c79adc413947d1d26f9ab98d1ded6948e2f52c0264bb848be3d0ba9ba801b4f73102b2bbadaa0a430a58ba059988fd7a614beede16b37daa1f50e3dbe49"
}