📅 Original date posted:2022-02-24
📝 Original message:Since Taproot was activated, we no longer need separate OP_RETURN outputs to be pushed on-chain. If we want to attach any data to a transaction, we can create "OP_RETURN <anything>" as a branch in the TapScript. In this way, we can store that data off-chain and we can always prove that they are connected with some taproot address, that was pushed on-chain. Also, we can store more than 80 bytes for "free", because no such taproot branch will be ever pushed on-chain and used as an input. That means we can use "OP_RETURN <1.5 GB of data>", create some address having that taproot branch, and later prove to anyone that such "1.5 GB of data" is connected with our taproot address.
Currently in Bitcoin Core we have "data" field in "createrawtransaction". Should the implementation be changed to place that data in a TapScript instead of creating separate OP_RETURN output? What do you think?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220224/e4160455/attachment.html>;
vjudeu at gazeta.pl [ARCHIVE] /
npub135…nssga
2023-06-07 23:04:51
in reply to nevent1q…90j4
Author Public Key
npub1357006afyypkgz03lmq8fnuvlkyjt0rukx8rt56ck8xv396jaceqmnssgaPublished at
2023-06-07 23:04:51Event JSON
{
"id": "07f1098b660224768d51ae3e6f9ff5f1ca16c79603028f06ebb83fff149e9eb2",
"pubkey": "8d3cf7eba921036409f1fec074cf8cfd8925bc7cb18e35d358b1ccc89752ee32",
"created_at": 1686179091,
"kind": 1,
"tags": [
[
"e",
"3e6d073ce9df9e718a58810827a644673d7a6ffe0ae6d99287d03c682a819b60",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2022-02-24\n📝 Original message:Since Taproot was activated, we no longer need separate OP_RETURN outputs to be pushed on-chain. If we want to attach any data to a transaction, we can create \"OP_RETURN \u003canything\u003e\" as a branch in the TapScript. In this way, we can store that data off-chain and we can always prove that they are connected with some taproot address, that was pushed on-chain. Also, we can store more than 80 bytes for \"free\", because no such taproot branch will be ever pushed on-chain and used as an input. That means we can use \"OP_RETURN \u003c1.5 GB of data\u003e\", create some address having that taproot branch, and later prove to anyone that such \"1.5 GB of data\" is connected with our taproot address.\n \nCurrently in Bitcoin Core we have \"data\" field in \"createrawtransaction\". Should the implementation be changed to place that data in a TapScript instead of creating separate OP_RETURN output? What do you think?\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220224/e4160455/attachment.html\u003e",
"sig": "5cc004c9b091700fa7e756d23a9e676a1ed0069faa5ee9bc7a6dc880c1cf91c1b03e2d7b754b654a71ead23d7576b934df936dc221d328a19af828d6f54a51f3"
}