public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gavin Andresen <gavinandresen@gmail.com>
To: Wladimir <laanwj@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] On OP_RETURN in upcoming 0.9 release
Date: Mon, 24 Feb 2014 11:45:16 -0500	[thread overview]
Message-ID: <CABsx9T1qrmgu7nBF4yOsFfUjMrqpGK-J_GeCqWswZskO59B0ZA@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJC1FgCW9spkViMPvuWNS84Ys33pj=RP1ZpzBCa++e-iMQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1991 bytes --]

  reply	other threads:[~2014-02-24 16:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 16:03 [Bitcoin-development] On OP_RETURN in upcoming 0.9 release Jeff Garzik
2014-02-24 16:16 ` Pieter Wuille
2014-02-24 16:32   ` Jeff Garzik
2014-02-24 16:33   ` Jeff Garzik
2014-02-24 16:39 ` Wladimir
2014-02-24 16:45   ` Gavin Andresen [this message]
2014-02-24 16:50     ` Pavol Rusnak
2014-02-24 17:23   ` Mark Friedenbach
2014-02-24 23:06     ` Andreas Petersson
2014-02-24 23:13       ` Gregory Maxwell
2014-02-24 23:13       ` Luke-Jr
2014-02-28  5:25     ` Troy Benjegerdes
2014-02-28 14:42       ` Warren Togami Jr.
2014-02-28 19:25         ` Mark Friedenbach
2014-02-28 19:36           ` Justus Ranvier
2014-02-28 20:10         ` Drak
2014-02-24 17:10 ` Jeff Garzik
2014-02-24 22:12 ` Jeremy Spilman
2014-02-24 22:50   ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABsx9T1qrmgu7nBF4yOsFfUjMrqpGK-J_GeCqWswZskO59B0ZA@mail.gmail.com \
    --to=gavinandresen@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=laanwj@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox