📅 Original date posted:2023-02-16
🗒️ Summary of this message: Proposal to require all data in op_return output and add a required op_return_hash field checked by consensus, allowing nodes to re-validate the chain without storing op_return data.
📝 Original message:I propose to require all data to be in the op_return output PLUS add a
required op_return_hash field, which is checked by consensus. So that node
can re-validate the chain without having to store/download/look at the
contents of op_return data. The benefit of that little redundancy is that
"content-sensitive" communities can ignore the date they don't like.
Cheers
Claus
On Thu, Feb 16, 2023 at 7:30 PM Aymeric Vitte via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> It's super unclear how long it could take for such a change to be adopted
>
> Then the answer is simple, see:
> https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7#workaround-to-the-80b-op_return-limitation
>
> Outstandingly, very, mega, bad, but working, bringing bitcoin back 10
> years ago
>
> But why not? If bitcoin folks don't get that we need a 1tx storage
> solution for the future, then let's bring back bitcoin into the past and
> destroy coins
> Le 12/02/2023 à 17:23, Aymeric Vitte a écrit :
>
> https://github.com/bitcoin/bitcoin/issues/27043#issuecomment-1427069403
>
> "What is the process to have someone do the PR for this? Or I do it and
> most likely it will be a very shxtty one since I am not a C/C++ expert,
> then wasting the time of everybody
>
> It's urgently required, I did consider OP_RETURN as a dart in the past but
> changed my mind, it's adapted to the current evolutions, not flooding
> bitcoin with 2 txs while only 1 is needed
>
> If not the best 1 tx solution is super simple: store in addresses, and
> super bad at the end because burning bitcoins, while still not expensive if
> you don't need to store big things"
>
> Le 05/02/2023 à 19:12, Russell O'Connor via bitcoin-dev a écrit :
>
>
>
> On Sat., Feb. 4, 2023, 21:01 Peter Todd, <pete at petertodd.org> wrote:
>
>>
>>
>> On February 5, 2023 1:11:35 AM GMT+01:00, Russell O'Connor via
>> bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>> >Since bytes in the witness are cheaper than bytes in the script pubkey,
>> >there is a crossover point in data size where it will simply be cheaper
>> to
>> >use witness data. Where that crossover point is depends on the finer
>> >details of the overhead of the two methods, but you could make some
>> >reasonable assumptions. Such a calculation could form the basis of a
>> >reasonable OP_RETURN proposal. I don't know if it would be persuasive,
>> but
>> >it would at least be coherent.
>>
>> I don't think it's worth the technical complexity trying to carefully
>> argue a specific limit. Let users decide for themselves how they want to
>> use OpReturn.
>>
>
> Even better.
>
>>
>
> _______________________________________________
> bitcoin-dev mailing listbitcoin-dev at lists.linuxfoundation.orghttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
> --
> Sophia-Antipolis, France
> CV: https://www.peersm.com/CVAV.pdf
> LinkedIn: https://fr.linkedin.com/in/aymeric-vitte-05855b26
> GitHub : https://www.github.com/Ayms
> A Universal Coin Swap system based on Bitcoin: https://gist.github.com/Ayms/029125db2583e1cf9c3209769eb2cdd7
> A bitcoin NFT system: https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7
> Move your coins by yourself (browser version): https://peersm.com/wallet
> Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions
> torrent-live: https://github.com/Ayms/torrent-live
> node-Tor : https://www.github.com/Ayms/node-Tor
> Anti-spies and private torrents, dynamic blocklist: http://torrent-live.peersm.com
> Peersm : http://www.peersm.com
>
>
> --
> Sophia-Antipolis, France
> CV: https://www.peersm.com/CVAV.pdf
> LinkedIn: https://fr.linkedin.com/in/aymeric-vitte-05855b26
> GitHub : https://www.github.com/Ayms
> A Universal Coin Swap system based on Bitcoin: https://gist.github.com/Ayms/029125db2583e1cf9c3209769eb2cdd7
> A bitcoin NFT system: https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7
> Move your coins by yourself (browser version): https://peersm.com/wallet
> Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions
> torrent-live: https://github.com/Ayms/torrent-live
> node-Tor : https://www.github.com/Ayms/node-Tor
> Anti-spies and private torrents, dynamic blocklist: http://torrent-live.peersm.com
> Peersm : http://www.peersm.com
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230216/8a0f80cf/attachment.html>;
Claus Ehrenberg [ARCHIVE] /
npub1a8…e3wff
2023-06-07 23:19:03
in reply to nevent1q…lk5g
Author Public Key
npub1a8ck0asqq2y93057qzj5laj2c67mrdssw65txe5kr84g3a80v2nqye3wffPublished at
2023-06-07 23:19:03Event JSON
{
"id": "25e6d8fb54f593ca24d27163502fb812d8c14a3b6611147beac65307b66a0685",
"pubkey": "e9f167f600028858be9e00a54ff64ac6bdb1b61076a8b3669619ea88f4ef62a6",
"created_at": 1686179943,
"kind": 1,
"tags": [
[
"e",
"db7e30240de322a59459e6f6d735c7f019f73c8194514d70467812fbd7606451",
"",
"root"
],
[
"e",
"b8282510f2aaaae99819b0d8db0d71f3ee123bad04660fbed913a7c50e9fb18b",
"",
"reply"
],
[
"p",
"a2711d6616d348a3542bb2a791a9e51fcbc7b7d1d20652e5abe16d3e179321df"
]
],
"content": "📅 Original date posted:2023-02-16\n🗒️ Summary of this message: Proposal to require all data in op_return output and add a required op_return_hash field checked by consensus, allowing nodes to re-validate the chain without storing op_return data.\n📝 Original message:I propose to require all data to be in the op_return output PLUS add a\nrequired op_return_hash field, which is checked by consensus. So that node\ncan re-validate the chain without having to store/download/look at the\ncontents of op_return data. The benefit of that little redundancy is that\n\"content-sensitive\" communities can ignore the date they don't like.\n\nCheers\nClaus\n\nOn Thu, Feb 16, 2023 at 7:30 PM Aymeric Vitte via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e It's super unclear how long it could take for such a change to be adopted\n\u003e\n\u003e Then the answer is simple, see:\n\u003e https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7#workaround-to-the-80b-op_return-limitation\n\u003e\n\u003e Outstandingly, very, mega, bad, but working, bringing bitcoin back 10\n\u003e years ago\n\u003e\n\u003e But why not? If bitcoin folks don't get that we need a 1tx storage\n\u003e solution for the future, then let's bring back bitcoin into the past and\n\u003e destroy coins\n\u003e Le 12/02/2023 à 17:23, Aymeric Vitte a écrit :\n\u003e\n\u003e https://github.com/bitcoin/bitcoin/issues/27043#issuecomment-1427069403\n\u003e\n\u003e \"What is the process to have someone do the PR for this? Or I do it and\n\u003e most likely it will be a very shxtty one since I am not a C/C++ expert,\n\u003e then wasting the time of everybody\n\u003e\n\u003e It's urgently required, I did consider OP_RETURN as a dart in the past but\n\u003e changed my mind, it's adapted to the current evolutions, not flooding\n\u003e bitcoin with 2 txs while only 1 is needed\n\u003e\n\u003e If not the best 1 tx solution is super simple: store in addresses, and\n\u003e super bad at the end because burning bitcoins, while still not expensive if\n\u003e you don't need to store big things\"\n\u003e\n\u003e Le 05/02/2023 à 19:12, Russell O'Connor via bitcoin-dev a écrit :\n\u003e\n\u003e\n\u003e\n\u003e On Sat., Feb. 4, 2023, 21:01 Peter Todd, \u003cpete at petertodd.org\u003e wrote:\n\u003e\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e On February 5, 2023 1:11:35 AM GMT+01:00, Russell O'Connor via\n\u003e\u003e bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e \u003eSince bytes in the witness are cheaper than bytes in the script pubkey,\n\u003e\u003e \u003ethere is a crossover point in data size where it will simply be cheaper\n\u003e\u003e to\n\u003e\u003e \u003euse witness data. Where that crossover point is depends on the finer\n\u003e\u003e \u003edetails of the overhead of the two methods, but you could make some\n\u003e\u003e \u003ereasonable assumptions. Such a calculation could form the basis of a\n\u003e\u003e \u003ereasonable OP_RETURN proposal. I don't know if it would be persuasive,\n\u003e\u003e but\n\u003e\u003e \u003eit would at least be coherent.\n\u003e\u003e\n\u003e\u003e I don't think it's worth the technical complexity trying to carefully\n\u003e\u003e argue a specific limit. Let users decide for themselves how they want to\n\u003e\u003e use OpReturn.\n\u003e\u003e\n\u003e\n\u003e Even better.\n\u003e\n\u003e\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing listbitcoin-dev at lists.linuxfoundation.orghttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n\u003e --\n\u003e Sophia-Antipolis, France\n\u003e CV: https://www.peersm.com/CVAV.pdf\n\u003e LinkedIn: https://fr.linkedin.com/in/aymeric-vitte-05855b26\n\u003e GitHub : https://www.github.com/Ayms\n\u003e A Universal Coin Swap system based on Bitcoin: https://gist.github.com/Ayms/029125db2583e1cf9c3209769eb2cdd7\n\u003e A bitcoin NFT system: https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7\n\u003e Move your coins by yourself (browser version): https://peersm.com/wallet\n\u003e Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions\n\u003e torrent-live: https://github.com/Ayms/torrent-live\n\u003e node-Tor : https://www.github.com/Ayms/node-Tor\n\u003e Anti-spies and private torrents, dynamic blocklist: http://torrent-live.peersm.com\n\u003e Peersm : http://www.peersm.com\n\u003e\n\u003e\n\u003e --\n\u003e Sophia-Antipolis, France\n\u003e CV: https://www.peersm.com/CVAV.pdf\n\u003e LinkedIn: https://fr.linkedin.com/in/aymeric-vitte-05855b26\n\u003e GitHub : https://www.github.com/Ayms\n\u003e A Universal Coin Swap system based on Bitcoin: https://gist.github.com/Ayms/029125db2583e1cf9c3209769eb2cdd7\n\u003e A bitcoin NFT system: https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7\n\u003e Move your coins by yourself (browser version): https://peersm.com/wallet\n\u003e Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions\n\u003e torrent-live: https://github.com/Ayms/torrent-live\n\u003e node-Tor : https://www.github.com/Ayms/node-Tor\n\u003e Anti-spies and private torrents, dynamic blocklist: http://torrent-live.peersm.com\n\u003e Peersm : http://www.peersm.com\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230216/8a0f80cf/attachment.html\u003e",
"sig": "6517f50a7f3fd12f52fe712d79cbe9af651ca9c95562913ec8ca5fd13c77038556083f85cf75c03a69385cd4818fe93e1bfb99b402b1363b8dcd3e0eed03d9f7"
}