public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Pieter Wuille <pieter.wuille@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:32:52 -0500	[thread overview]
Message-ID: <CAJHLa0Nwyfs_VJcGeSEgix5wb00LfpDGmdS4u378+XO8QKwiJA@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBi0ehdE4TszJGYNBcY0VNJtDNsOfOuaz+QpH9fBjr5z7g@mail.gmail.com>

Not really -- a MasterCoin transaction or JPEG

On Mon, Feb 24, 2014 at 11:16 AM, Pieter Wuille <pieter.wuille@gmail.com> wrote:
> On Mon, Feb 24, 2014 at 5:03 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
>
>> I do think
>> regular transactions should have the ability to include some metadata.
>
> and
>
>> 2) Endorsement of chain data storage.
>>
>> Nothing could be further from the truth.
>
> These two statements are in direct contradiction with each other.
>
> --
> Pieter



-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/



  reply	other threads:[~2014-02-24 16:32 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 [this message]
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
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=CAJHLa0Nwyfs_VJcGeSEgix5wb00LfpDGmdS4u378+XO8QKwiJA@mail.gmail.com \
    --to=jgarzik@bitpay.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=pieter.wuille@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