š
Original date posted:2023-02-05
šļø Summary of this message: The use of OP_RETURN for storing small things like signatures, addresses, and metadata is recommended, while Witness is suggested for storing big data. There is no need to micromanage the use of OP_RETURN since it has minimal impact.
š Original message:On February 5, 2023 12:40:38 PM GMT+01:00, Aymeric Vitte <aymeric at peersm.com> 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.
Peter Todd [ARCHIVE] /
npub1m2ā¦a2np2
2023-06-07 23:19:01
in reply to nevent1qā¦4tx8
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 23:19:01Event JSON
{
"id": "7c7c3f6810bd2dc21c3d32c68699aa61deb68c154e959486ac2b4a945bfd54a9",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686179941,
"kind": 1,
"tags": [
[
"e",
"db7e30240de322a59459e6f6d735c7f019f73c8194514d70467812fbd7606451",
"",
"root"
],
[
"e",
"bb27e5034bf2a4587c4173a7b8297fe84c7e3ad7d93dadbfa9699822adebbddb",
"",
"reply"
],
[
"p",
"a2711d6616d348a3542bb2a791a9e51fcbc7b7d1d20652e5abe16d3e179321df"
]
],
"content": "š
Original date posted:2023-02-05\nšļø Summary of this message: The use of OP_RETURN for storing small things like signatures, addresses, and metadata is recommended, while Witness is suggested for storing big data. There is no need to micromanage the use of OP_RETURN since it has minimal impact.\nš Original message:On February 5, 2023 12:40:38 PM GMT+01:00, Aymeric Vitte \u003caymeric at peersm.com\u003e wrote:\n\u003eI think logically:\n\u003e\n\u003e- if you want to store something big and can afford several txs in your\n\u003edesign, then you use something like witness\n\u003e\n\u003e- if you want to store small things like signatures, addresses hashes\n\u003eand some metadata and your design does not make several txs easy, then\n\u003eyou use OP_RETURN\n\u003e\n\u003eThen how can we move forward with several OP_RETURN and no size limit?\n\nBecause 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.\n\nSince 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.",
"sig": "c7e602caedbde5485359cb9958b2dc924d3dfb2a86ec97fbc082ae3e410007055066d248df20f780197e10f4e466d450865ab8c83088c43a92c12df1350adcaf"
}