From: Jeff Garzik <jgarzik@bitpay•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] On OP_RETURN in upcoming 0.9 release
Date: Mon, 24 Feb 2014 12:10:26 -0500 [thread overview]
Message-ID: <CAJHLa0NP-78iK7dpB96YnJ0D3VftaahvZ1k4U0ziV-jAUKqdFQ@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0PXHY1qisXhN98DMxgp11ouqkzYMBvrTTNOtwX09T1kZg@mail.gmail.com>
This PR reduces the size to 40 bytes:
https://github.com/bitcoin/bitcoin/pull/3737
(Note - this is not intended to close the discussion... please do keep
sending in feedback)
On Mon, Feb 24, 2014 at 11:03 AM, Jeff Garzik <jgarzik@bitpay•com> wrote:
> An update in forthcoming 0.9 release includes a change to make
> OP_RETURN standard, permitted a small amount of metadata to be
> attached to a transaction:
> https://github.com/bitcoin/bitcoin/pull/2738
>
> There was always going to be some level of controversy attached to
> this. However, some issues, perceptions and questions are bubbling
> up, and it seemed fair to cover them on the list, not just IRC.
>
> 1) FAQ: Why 80 bytes of data? This is the leading programmer
> question, and it was not really documented well at all. Simple
> answer: 2x SHA256 or 1x SHA512, plus some tiny bit of metadata. Some
> schemes are of the nature "BOND<hash>" rather than just plain hash.
> 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.
>
> 2) Endorsement of chain data storage. Listening to bitcoin conference
> corridor discussions, reading forum posts and the occasional article
> have over-simplified the situation to "core devs endorse data storage
> over blockchain! let me start uploading my naughty movie collection!
> IM over blockchain, woo hoo!"
>
> Nothing could be further from the truth. It's a way to make data
> /less damaging/, not an endorsement of data storage in chain as a good
> idea. MasterCoin and other projects were doing -even worse- things,
> such as storing data in forever-unspendable TX outputs, bloating the
> UTXO for eternity.
>
> It seems reasonable to have a release note to this effect in the 0.9
> release announcement, IMO.
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-02-24 17:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 16:03 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
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 [this message]
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=CAJHLa0NP-78iK7dpB96YnJ0D3VftaahvZ1k4U0ziV-jAUKqdFQ@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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