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 <laa...@gmail.com> wrote:

> On Mon, Feb 24, 2014 at 5:03 PM, Jeff Garzik <jgar...@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
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
Bitcoin-development mailing list

Reply via email to