public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Turkey Breast <turkeybreast@yahoo.com>
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New Output Script Type
Date: Fri, 13 Sep 2013 21:10:08 -0400	[thread overview]
Message-ID: <CAJHLa0Px3bj7RAyQ6EytGEoN0D8vSPRtYQ42NOR_jyKJ71GoUQ@mail.gmail.com> (raw)
In-Reply-To: <1379119871.76503.YahooMailNeo@web162705.mail.bf1.yahoo.com>

See https://github.com/bitcoin/bitcoin/pull/2738

On Fri, Sep 13, 2013 at 8:51 PM, Turkey Breast <turkeybreast@yahoo.com> wrote:
> http://www.proofofexistence.com/
>
> and
>
> https://github.com/spesmilo/sx/blob/master/src/sx-embed-addr
>
> Embedding data in the blockchain as a hash is out there and a reality.
>
> I suggest that there should be a new payment type that is unspendable to
> support this.
> Like you have pubkey_hash, pubkey, script_hash, ..., "embed_hash"
>
> Maybe just a script with a single 20 byte push data.
>
> Advantages:
>
> * Optimisation possibilities (you know this can't be spent, and the script
> can't be processed).
> * Avoid indexing in an address database Bitcoin addresses which are
> currently being
> used to index data. They will never be spent, yet they will be indexed
> because they look
> identical to normal Bitcoin addresses.
>
> By separating this class of Bitcoin usage, we can improve the core Bitcoin
> payments system.
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT
> 2. Standardize and globalize service processes across IT
> 3. Implement zero-touch automation to replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>



-- 
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc.      https://bitpay.com/



      parent reply	other threads:[~2013-09-14  1:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-14  0:51 [Bitcoin-development] New Output Script Type Turkey Breast
2013-09-14  1:00 ` Mark Friedenbach
2013-09-14  1:10 ` Jeff Garzik [this message]

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=CAJHLa0Px3bj7RAyQ6EytGEoN0D8vSPRtYQ42NOR_jyKJ71GoUQ@mail.gmail.com \
    --to=jgarzik@bitpay.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=turkeybreast@yahoo.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