Yes I agree, let people decide and since taproot has no limits then it sould be the same for OP_RETURN
I posted https://github.com/bitcoin/bitcoin/issues/27043 Le 05/02/2023 à 13:06, Peter Todd a écrit : > > On February 5, 2023 12:40:38 PM GMT+01:00, Aymeric Vitte <[email protected]> > wrote: >> I think logically: >> >> - if you want to store something big and can afford several txs in your >> design, then you use something like witness >> >> - if you want to store small things like signatures, addresses hashes >> and some metadata and your design does not make several txs easy, then >> you use OP_RETURN >> >> Then how can we move forward with several OP_RETURN and no size limit? > Because what matters is the impact on other users. OpReturn isn't in UTXO > space and doesn't even take advantage of the witness discount, so it clearly > has minimal impact. > > Since it has minimal impact, there's no reason to micromanage exactly how > people use it. Let them decide for themselves with the fee market. This is > exactly the same as how we didn't put artificial limits on Taproot. -- 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 [email protected] https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
