Alan Reiner [ARCHIVE] on Nostr: 📅 Original date posted:2014-11-17 📝 Original message:On 11/16/2014 02:04 PM, ...
📅 Original date posted:2014-11-17
📝 Original message:On 11/16/2014 02:04 PM, Jorge Timón wrote:
> I remember people asking in #bitcoin-dev "Does anyone know any use
> case for greater sizes OP_RETURNs?" and me answering "I do not know of
> any use cases that require bigger sizes".
For reference, there was a brief time where I was irritated that the
size had been reduced to 40 bytes, because I had an application where I
wanted to put ECDSA in signatures in the OP_RETURN, and you're going to
need at least 64 bytes for that. Unfortunately I can't remember now
what that application was, so it's difficult for me to argue for it.
But I don't think that's an unreasonable use case: sending a payment
with a signature, essentially all timestamped in the blockchain.
Published at
2023-06-07 15:27:28Event JSON
{
"id": "1706e7f4cfdb9bc4c6a1abb1e3835844fa6d09ed8819f1e59bdd7eec64a58922",
"pubkey": "86f42bcb76a431c128b596c36714ae73a42cae48706a9e5513d716043447f5ec",
"created_at": 1686151648,
"kind": 1,
"tags": [
[
"e",
"9ea4322dc19e55ba7a16fb4778826be5d9520c59d79239c258ee43cc77449b49",
"",
"root"
],
[
"e",
"e3c1515b6cbb88aa52b2cfb692025fea201af2e277196d36885ddb96a179d811",
"",
"reply"
],
[
"p",
"498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84"
]
],
"content": "📅 Original date posted:2014-11-17\n📝 Original message:On 11/16/2014 02:04 PM, Jorge Timón wrote:\n\u003e I remember people asking in #bitcoin-dev \"Does anyone know any use\n\u003e case for greater sizes OP_RETURNs?\" and me answering \"I do not know of\n\u003e any use cases that require bigger sizes\".\n\nFor reference, there was a brief time where I was irritated that the\nsize had been reduced to 40 bytes, because I had an application where I\nwanted to put ECDSA in signatures in the OP_RETURN, and you're going to\nneed at least 64 bytes for that. Unfortunately I can't remember now\nwhat that application was, so it's difficult for me to argue for it. \nBut I don't think that's an unreasonable use case: sending a payment\nwith a signature, essentially all timestamped in the blockchain.",
"sig": "bd970758728c7c129cc92da1b85fb998b104bad1718aff9d633fd5121c4393b8e5f6952740013c33a1b508515f3739b871f9e407d5024604e310ee36bdd79b0f"
}