š
Original date posted:2014-02-24
š Original message:40 bytes is small enough to never require an OP_PUSHDATA1, too, which will
make writing the OP_RETURN-as-standard BIP simpler.
On Mon, Feb 24, 2014 at 11:39 AM, Wladimir <laanwj at gmail.com> wrote:
>
> On Mon, Feb 24, 2014 at 5:03 PM, Jeff Garzik <jgarzik at bitpay.com> wrote:
>
>> A common IRC proposal seems to lean towards reducing that from 80.
>> I'll leave it to the crowd to argue about size from there. I do think
>> regular transactions should have the ability to include some metadata.
>>
>
> I'd be in favor of bringing it down to 40 for 0.9.
>
> That'd be enough for <8 byte header/identifier><32 byte hash>.
>
> 80, as the standard line length, is almost asking for "insert your
> graffiti message here". I also see no need for 64 bytes hashes such as
> SHA512 in the context of bitcoin, as that only offers 256-bit security (at
> most) in the first place.
>
> And if this is not abused, these kind of transactions become popular, and
> more space is really needed, the limit can always be increased in a future
> version.
>
> Wladimir
>
--
--
Gavin Andresen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140224/9c038dc0/attachment.html>;
Gavin Andresen [ARCHIVE] /
npub1s4ā¦d44kw
2023-06-07 15:13:56
in reply to nevent1qā¦6aum
Author Public Key
npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kwPublished at
2023-06-07 15:13:56Event JSON
{
"id": "92ccf5b2971515da619a77333fc0ea897b308d350d2e727709142910c210c539",
"pubkey": "857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4",
"created_at": 1686150836,
"kind": 1,
"tags": [
[
"e",
"1ef870aa2080d76066b16301e94316a8cf8557aa7768e48cc4c5664289bfd14e",
"",
"root"
],
[
"e",
"7a678e9c9c79b82fc82042053306aecdf7d370e6358e95112e414c78dd1406b3",
"",
"reply"
],
[
"p",
"30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722"
]
],
"content": "š
Original date posted:2014-02-24\nš Original message:40 bytes is small enough to never require an OP_PUSHDATA1, too, which will\nmake writing the OP_RETURN-as-standard BIP simpler.\n\n\nOn Mon, Feb 24, 2014 at 11:39 AM, Wladimir \u003claanwj at gmail.com\u003e wrote:\n\n\u003e\n\u003e On Mon, Feb 24, 2014 at 5:03 PM, Jeff Garzik \u003cjgarzik at bitpay.com\u003e wrote:\n\u003e\n\u003e\u003e A common IRC proposal seems to lean towards reducing that from 80.\n\u003e\u003e I'll leave it to the crowd to argue about size from there. I do think\n\u003e\u003e regular transactions should have the ability to include some metadata.\n\u003e\u003e\n\u003e\n\u003e I'd be in favor of bringing it down to 40 for 0.9.\n\u003e\n\u003e That'd be enough for \u003c8 byte header/identifier\u003e\u003c32 byte hash\u003e.\n\u003e\n\u003e 80, as the standard line length, is almost asking for \"insert your\n\u003e graffiti message here\". I also see no need for 64 bytes hashes such as\n\u003e SHA512 in the context of bitcoin, as that only offers 256-bit security (at\n\u003e most) in the first place.\n\u003e\n\u003e And if this is not abused, these kind of transactions become popular, and\n\u003e more space is really needed, the limit can always be increased in a future\n\u003e version.\n\u003e\n\u003e Wladimir\n\u003e\n\n\n\n-- \n--\nGavin Andresen\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140224/9c038dc0/attachment.html\u003e",
"sig": "21a947fc63ab9282013231c25018c13032bdb31079642d802fe3c414d27c9e9093eb4184e7b87765dacf5f2feb6c1caea4203a34199e1612719244ada50d21e3"
}