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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <turkeybreast@yahoo.com>) id 1VKe7j-00084y-VR
for bitcoin-development@lists.sourceforge.net;
Sat, 14 Sep 2013 00:54:08 +0000
X-ACL-Warn:
Received: from nm35.bullet.mail.ne1.yahoo.com ([98.138.229.28])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1VKe7i-0005CV-Kg
for bitcoin-development@lists.sourceforge.net;
Sat, 14 Sep 2013 00:54:07 +0000
Received: from [127.0.0.1] by nm35.bullet.mail.ne1.yahoo.com with NNFMP;
14 Sep 2013 00:54:01 -0000
Received: from [98.138.226.180] by nm35.bullet.mail.ne1.yahoo.com with NNFMP;
14 Sep 2013 00:51:12 -0000
Received: from [98.139.212.146] by tm15.bullet.mail.ne1.yahoo.com with NNFMP;
14 Sep 2013 00:51:12 -0000
Received: from [98.139.212.197] by tm3.bullet.mail.bf1.yahoo.com with NNFMP;
14 Sep 2013 00:51:11 -0000
Received: from [127.0.0.1] by omp1006.mail.bf1.yahoo.com with NNFMP;
14 Sep 2013 00:51:11 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 659938.47561.bm@omp1006.mail.bf1.yahoo.com
Received: (qmail 83378 invoked by uid 60001); 14 Sep 2013 00:51:11 -0000
X-YMail-OSG: .yjdlpkVM1kOlCGS3lJP353JeL7sDxH3eNzDRBEmOTgMOKR
VNoRb0nWYuaFrTsLhKZsgZrOcBYq0d9Z8.xb5TMsah8jek9ebEtdC1fQ35ZX
xCh3LQJmd3jQSVe._lQPg.OGX89e3FJ1r46IMrzgwTvBGMSjzcLxlv.cXDxP
oLrwywWwzBHMe.wZ3.JaMgxKM7zSn18sU._K1C1RdWP1jc9xmyfHfDQWMmeO
l3Yqifwng63iGyQyduO5uMKC5fo2fWZRIsnrXjIKJGLgHbWgXBbKH1NgK4qx
LTl_1fN73TpksgICB9GqtsCRAl9F2ItWFZvxtL.crqIlP.Z71Yn8KwPTINOz
gbGv0azegF2BgjGnYencmrw8Q9XNHAsXd3UHorX.W16dxLMDwwQuYXxiDM3j
1YJ7ph.VmJildJknKH9zAVeOVlp5mZP9lMAFl.S0Jvs8Js5BsTrRpsg9yGKt
EQ5c9gObz5oxMBLrKNUB4mcauSal3PsI39xYTOR09gQtCVmj62dbXtMhfsis
sd7PNNPo3DonbVrzQ3uEPTvD_fUHDRaHbRYDb8i6LGxdnDuCZOwZHE3.4XZG
DDizTAi7vIlOnTjokKejR5QDhhl45Y3FkLDnNEG7YxEMAoDoXHPF1UF4L6G_
sjGHkOP7J4zDQAx1QkTC7cML7depakOqeI6jC7uWUjmrZDofanyGec75PnfZ
1oXNaYMjIAiF5hK2C3F4tHeUCg2btI5.F2bg-
Received: from [82.84.185.219] by web162705.mail.bf1.yahoo.com via HTTP;
Fri, 13 Sep 2013 17:51:11 PDT
X-Rocket-MIMEInfo: 002.001,
aHR0cDovL3d3dy5wcm9vZm9mZXhpc3RlbmNlLmNvbS8KCmFuZAoKaHR0cHM6Ly9naXRodWIuY29tL3NwZXNtaWxvL3N4L2Jsb2IvbWFzdGVyL3NyYy9zeC1lbWJlZC1hZGRyCgpFbWJlZGRpbmcgZGF0YSBpbiB0aGUgYmxvY2tjaGFpbiBhcyBhIGhhc2ggaXMgb3V0IHRoZXJlIGFuZCBhIHJlYWxpdHkuCgpJIHN1Z2dlc3QgdGhhdCB0aGVyZSBzaG91bGQgYmUgYSBuZXcgcGF5bWVudCB0eXBlIHRoYXQgaXMgdW5zcGVuZGFibGUgdG8gc3VwcG9ydCB0aGlzLgpMaWtlIHlvdSBoYXZlIHB1YmtleV9oYXNoLCBwdWIBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.157.561
Message-ID: <1379119871.76503.YahooMailNeo@web162705.mail.bf1.yahoo.com>
Date: Fri, 13 Sep 2013 17:51:11 -0700 (PDT)
From: Turkey Breast <turkeybreast@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="1391001287-638849088-1379119871=:76503"
X-Spam-Score: -0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(turkeybreast[at]yahoo.com)
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.229.28 listed in list.dnswl.org]
-0.9 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain 1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1VKe7i-0005CV-Kg
Subject: [Bitcoin-development] New Output Script Type
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Turkey Breast <turkeybreast@yahoo.com>
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 00:54:08 -0000
--1391001287-638849088-1379119871=:76503
Content-Type: text/plain; charset=us-ascii
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.
--1391001287-638849088-1379119871=:76503
Content-Type: text/html; charset=us-ascii
<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>http://www.proofofexistence.com/</div><div><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">and</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">https://github.com/spesmilo/sx/blob/master/src/sx-embed-addr</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new
roman,new york,times,serif; background-color: transparent; font-style: normal;">Embedding data in the blockchain as a hash is out there and a reality.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">I suggest that there should be a new payment type that is unspendable to support this.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">Like you have pubkey_hash, pubkey, script_hash, ..., "embed_hash"<br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><br></div><div
style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">Maybe just a script with a single 20 byte push data.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">Advantages:</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">* Optimisation possibilities (you know this can't be spent, and the script can't be processed).</div><div
style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">* Avoid indexing in an address database Bitcoin addresses which are currently being</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">used to index data. They will never be spent, yet they will be indexed because they look</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">identical to normal Bitcoin addresses.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color:
transparent; font-style: normal;">By separating this class of Bitcoin usage, we can improve the core Bitcoin payments system.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"></div></div></body></html>
--1391001287-638849088-1379119871=:76503--
|
