📅 Original date posted:2022-03-16
📝 Original message:On Thu, Feb 24, 2022 at 10:02:08AM +0100, vjudeu via bitcoin-dev wrote:
> 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.
There are two use-cases for OP_RETURN: committing to data, and publishing data.
Your proposal can only do the former, not the latter, and there are use-cases
for both.
--
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/20220316/d213a1cc/attachment-0001.sig>;
Peter Todd [ARCHIVE] /
npub1m2…a2np2
2023-06-07 23:06:30
in reply to nevent1q…uapg
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Seen on
wss://relay.noswhere.comPublished at
2023-06-07 23:06:30Event JSON
{
"id": "9436c7c1f2f1eba90f789ec6a87fee31cba397939ce7829e04470aedecba3cd7",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686179190,
"kind": 1,
"tags": [
[
"e",
"eb152f6102d6aecd645f09865b06cdcb41dafdb1f68ba80a6cdd71f7aea8b4bc",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2022-03-16\n📝 Original message:On Thu, Feb 24, 2022 at 10:02:08AM +0100, vjudeu via bitcoin-dev wrote:\n\u003e 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\nThere are two use-cases for OP_RETURN: committing to data, and publishing data.\nYour proposal can only do the former, not the latter, and there are use-cases\nfor both.\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/20220316/d213a1cc/attachment-0001.sig\u003e",
"sig": "8d32e61e3d7815288899e1969bc5005a827c56793ea428711c0217eac0c80c1a61676e7e5edf0fe003044c4e8740332cad13ef19907db668904b8b1a6f8e6cb4"
}