1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1VKeNN-0005bY-Fz
for bitcoin-development@lists.sourceforge.net;
Sat, 14 Sep 2013 01:10:17 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.177 as permitted sender)
client-ip=209.85.212.177; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f177.google.com;
Received: from mail-wi0-f177.google.com ([209.85.212.177])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VKeNL-00084N-Lt
for bitcoin-development@lists.sourceforge.net;
Sat, 14 Sep 2013 01:10:17 +0000
Received: by mail-wi0-f177.google.com with SMTP id cb5so1511327wib.10
for <bitcoin-development@lists.sourceforge.net>;
Fri, 13 Sep 2013 18:10:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=EpPnPmiQeDng8r/p9CXLUQcaPOoZjFYbuxUZjMx/guE=;
b=I6F6VtodSxxUr5rZMl7WlnltZ6dWmsw098yyA+ISKpO/jhTsOZVjCzS4vLtlg4Nt2T
uoizIWxpwfp8TQ5Q6So/JVHNava8Kc1df28a7VcXveYSHxkPWcyT9tpy584p4CEsO5AB
DxOFi+LesVKto7kJ8yvqOZRj83RsrBPJBHCHMOt7ahU/8V4g0nc0YeP4bq4iGyVWTF3F
S8DKKqQiNmxHE+PvQTC13qRe1IGVfJrLfogR6PE96dIIRMtwWXqboD2wvuLP4L5myduf
DTn/XnqMD7W6oRGXEux6QvXq/7uuHFIIPAaEUQ1XyDvS2X2CSO+cNCERzfHCGScppf84
OqGQ==
X-Gm-Message-State: ALoCoQnCqbx8WNd49etgixiLviOpSqLn1y5Os2R3gmEz5LBSvvF/EILvRLrA0PrJ2S7IJfBd7Cbk
MIME-Version: 1.0
X-Received: by 10.180.206.244 with SMTP id lr20mr4582538wic.45.1379121008756;
Fri, 13 Sep 2013 18:10:08 -0700 (PDT)
Received: by 10.194.236.69 with HTTP; Fri, 13 Sep 2013 18:10:08 -0700 (PDT)
In-Reply-To: <1379119871.76503.YahooMailNeo@web162705.mail.bf1.yahoo.com>
References: <1379119871.76503.YahooMailNeo@web162705.mail.bf1.yahoo.com>
Date: Fri, 13 Sep 2013 21:10:08 -0400
Message-ID: <CAJHLa0Px3bj7RAyQ6EytGEoN0D8vSPRtYQ42NOR_jyKJ71GoUQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Turkey Breast <turkeybreast@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VKeNL-00084N-Lt
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New Output Script Type
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 14 Sep 2013 01:10:17 -0000
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/
|
