Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.49 as permitted sender)
	client-ip=209.85.213.49; envelope-from=gavinandresen@gmail.com;
	helo=mail-yh0-f49.google.com; 
MIME-Version: 1.0
In-Reply-To: <CA+s+GJC1FgCW9spkViMPvuWNS84Ys33pj=RP1ZpzBCa++e-iMQ@mail.gmail.com>
References: <CAJHLa0PXHY1qisXhN98DMxgp11ouqkzYMBvrTTNOtwX09T1kZg@mail.gmail.com>
	<CA+s+GJC1FgCW9spkViMPvuWNS84Ys33pj=RP1ZpzBCa++e-iMQ@mail.gmail.com>
Date: Mon, 24 Feb 2014 11:45:16 -0500
Message-ID: <CABsx9T1qrmgu7nBF4yOsFfUjMrqpGK-J_GeCqWswZskO59B0ZA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Wladimir <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c1d968398eb904f329b288
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] On OP_RETURN in upcoming 0.9 release
Precedence: list

--001a11c1d968398eb904f329b288
Content-Type: text/plain; charset=ISO-8859-1

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

>
> On Mon, Feb 24, 2014 at 5:03 PM, Jeff Garzik <jgarzik@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

--001a11c1d968398eb904f329b288
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">40 bytes is small enough to never require an OP_PUSHDATA1,=
 too, which will make writing the OP_RETURN-as-standard BIP simpler.<div><b=
r></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, F=
eb 24, 2014 at 11:39 AM, Wladimir <span dir=3D"ltr">&lt;<a href=3D"mailto:l=
aanwj@gmail.com" target=3D"_blank">laanwj@gmail.com</a>&gt;</span> wrote:<b=
r>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_ext=
ra"><div class=3D"gmail_quote"><div class=3D"">On Mon, Feb 24, 2014 at 5:03=
 PM, Jeff Garzik <span dir=3D"ltr">&lt;<a href=3D"mailto:jgarzik@bitpay.com=
" target=3D"_blank">jgarzik@bitpay.com</a>&gt;</span> wrote:<br>

</div><div class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">A c=
ommon IRC proposal seems to lean towards reducing that from 80.<br>
I&#39;ll leave it to the crowd to argue about size from there. I do think<b=
r>
regular transactions should have the ability to include some metadata.<br><=
/blockquote><div><br></div></div><div>I&#39;d be in favor of bringing it do=
wn to 40 for 0.9. <br><br>That&#39;d be enough for &lt;8 byte header/identi=
fier&gt;&lt;32 byte hash&gt;. <br>

<br>80, as the standard line length, is almost asking for &quot;insert your=
 graffiti message here&quot;. I also see no need for 64 bytes hashes such a=
s SHA512 in the context of bitcoin, as that only offers 256-bit security (a=
t most) in the first place.<br>

<br></div><div>And if this is not abused, these kind of transactions become=
 popular, and more space is really needed, the limit can always be increase=
d in a future version.<span class=3D"HOEnZb"><font color=3D"#888888"><br></=
font></span></div>
<span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div>Wladimir=
<br></div></font></span></div>
</div></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>--<br>Gavin =
Andresen<br>
</div></div>

--001a11c1d968398eb904f329b288--