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
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
|
Return-Path: <outlook_32F81FD1D1BD8CA0@outlook.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 2CA9B8D7
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 5 Feb 2017 21:06:22 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from BAY004-OMC2S2.hotmail.com (bay004-omc2s2.hotmail.com
[65.54.190.77])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5401E1AC
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 5 Feb 2017 21:06:21 +0000 (UTC)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com ([65.54.190.124])
by BAY004-OMC2S2.hotmail.com over TLS secured channel with
Microsoft SMTPSVC(7.5.7601.23008); Sun, 5 Feb 2017 13:06:21 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com;
s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;
bh=clJQWYMv8/PeU9/UMx25qwDf3bXHdB0KASMLLTceBQ4=;
b=NHfPjMCHMG8P2S7uI63IxJytFAyvsn3iStgiCtbCYEn9uII0NZdku6LNQE2iLujeeFGVEIJnA37jb7gA+mY6vJP+92Fltq1I2xVLn0evTDTAnEfxlLk+yUeFNy8rXfqUAb2VwrXJUNcb0/mmJFAnly+fvCXI95A6g9jKTEWvI63gqCE833cjnCjxGTl8dDW/yOxlrLIrCfGIR3Pyp6vV0KS2Due2eeMG6A8qbVMxpj85lOPJ9fvqcpL3UTUFV4fbCrYINeTILJzB516iMjDhXf5G0VlU57Wn79wiYCFZhyOQeaGVuJtp1CoeldbhtL645zznJx9t8ge7H7TzyFSW5w==
Received: from BY2NAM03FT022.eop-NAM03.prod.protection.outlook.com
(10.152.84.52) by BY2NAM03HT071.eop-NAM03.prod.protection.outlook.com
(10.152.84.192) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.7;
Sun, 5 Feb 2017 21:06:20 +0000
Received: from BL2PR03MB435.namprd03.prod.outlook.com (10.152.84.53) by
BY2NAM03FT022.mail.protection.outlook.com (10.152.84.225) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id
15.1.888.7 via Frontend Transport; Sun, 5 Feb 2017 21:06:19 +0000
Received: from BL2PR03MB435.namprd03.prod.outlook.com ([10.141.92.24]) by
BL2PR03MB435.namprd03.prod.outlook.com ([10.141.92.24]) with mapi id
15.01.0888.022; Sun, 5 Feb 2017 21:06:20 +0000
From: John Hardy <john@seebitcoin.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Thread-Topic: [bitcoin-dev] Transaction signalling through output address
hashing
Thread-Index: AQHSfbGZvr4KI3DKIEKafV3UKQG/oqFanJ6AgAAC/1OAAEw0+Q==
Sender: John Hardy <outlook_32F81FD1D1BD8CA0@outlook.com>
Date: Sun, 5 Feb 2017 21:06:19 +0000
Message-ID: <BL2PR03MB435DEA7CFB526C4DB58F740EE410@BL2PR03MB435.namprd03.prod.outlook.com>
References: <BL2PR03MB4358286BE7F0D51F99B8EC6EE4C0@BL2PR03MB435.namprd03.prod.outlook.com>,
<CAAt2M18uMt7BA_brpFM+zipodDkj_bdnZ3SXMxOpVPN+YqgMoA@mail.gmail.com>,
<BL2PR03MB435D7E36434A342BBEBC735EE410@BL2PR03MB435.namprd03.prod.outlook.com>
In-Reply-To: <BL2PR03MB435D7E36434A342BBEBC735EE410@BL2PR03MB435.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: lists.linuxfoundation.org; dkim=none (message not
signed) header.d=none; lists.linuxfoundation.org; dmarc=none action=none
header.from=seebitcoin.com;
x-incomingtopheadermarker: OriginalChecksum:CC3911F99E16CF1BE3AA0561BC73969D80A9C2CDC7F8CC01EAE58E4BF501E0F5;
UpperCasedChecksum:CCD925670661D8562794CE4AA0D77C7569CB99B0DEA0550A5F6EF9F11CB1B2F3;
SizeAsReceived:8094; Count:40
x-ms-exchange-messagesentrepresentingtype: 2
x-tmn: [N7YvtSF9QwuVzNqnjVi9UBcoKrRQabUq]
x-incomingheadercount: 40
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; BY2NAM03HT071;
5:xuRJTruhEr6oetzPs2xFhtD8sw9BUZcC8UL+NClTt14lC0Oa7H830l2vX7QeEkSeV/2AGxf545MBy1KO79Wkg2gSI2CBB0pPaJNpCf+h5ysSs2nx1YIPhoyALzJLx6WfFkFEkuMiIPct4BRzj1b38+E0yn+lpdQUaCEr51OuTTo=;
24:Q73SLeaHcgSKRJ8MJdHEXiKKXBgvtxQk4bpuI8GIqAx3EM33xLKZV12QomuhoB6Z66A73uORs1bAvhwPUac9oEnrpLpWhALXqvn57ojYG1s=;
7:flVTXn8SD1TzUCtRL0DB9rHjJQf90MBW2gFsZNVCRu2DRX2Lh/5S/R5S0Y+0ALzG5juD98r4r2WQvMeHFFO/SU07c2RbObTGN2DOrI+6GfBqxALbeh4VWeFEc678ZI63pEruorTmis5OVl406wqXc8XaNMmUMAyVs9UUO6f7n/w45Sl3fkDj9VldqgS2LLjQj4sQBIunzYlB8VhYBbKYmS0ohA3fI4P9aNJu5FkN5t9IxC5aiXXFDweec9Jm7FTkleFOf+hHVbbf4KTnAf1g3uAmkAYkhw8zvoFU41Myitk4pzs02BqOYTTm4Y96eA/x+TmZUE0Lmpo2x9Kcn2gEM6UfzjtwLl6SLoQ5zHbQ1/VtQJJgFP0ANIg7SwMbEzNOSJZ3ewbegjUFK28x6IwcVQQRI/Kgp+iUMRJAZzF5k1e33ySzYeDmUe8ljpU7DP/cHxyqzyZGMyxjyDzOLMdxLSkziZvBvv0ssT3Gh/SVFW534UlAq0Z8ZRtVT5BeZh422wXgelAHsm1S4FN2BcVPpQ==
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900005);
DIR:OUT; SFP:1102; SCL:1; SRVR:BY2NAM03HT071;
H:BL2PR03MB435.namprd03.prod.outlook.com; FPR:; SPF:None;
LANG:en;
x-ms-office365-filtering-correlation-id: 4821e2ec-3c17-4f59-bb3d-08d44e0ad56d
x-microsoft-antispam: UriScan:; BCL:0; PCL:0;
RULEID:(22001)(5061506426)(5061507331)(1603103135)(1601125107)(1603101373)(1701031045);
SRVR:BY2NAM03HT071;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0;
RULEID:(444111334)(432015086)(82015046); SRVR:BY2NAM03HT071;
BCL:0; PCL:0; RULEID:; SRVR:BY2NAM03HT071;
x-forefront-prvs: 0209425D0A
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
boundary="_000_BL2PR03MB435DEA7CFB526C4DB58F740EE410BL2PR03MB435namprd_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2017 21:06:19.8816 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2NAM03HT071
X-OriginalArrivalTime: 05 Feb 2017 21:06:21.0025 (UTC)
FILETIME=[B35E5510:01D27FF3]
X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Tue, 07 Feb 2017 08:56:18 +0000
Subject: [bitcoin-dev] Fw: Transaction signalling through output address
hashing
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 21:06:22 -0000
--_000_BL2PR03MB435DEA7CFB526C4DB58F740EE410BL2PR03MB435namprd_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Probabilistic collisions, while present, would be statistically insignifica=
nt at 4 chars length.
Implementation by wallets would just require a loop of their existing addre=
ss generation until a match is found, trivial to implement. Wallets could p=
rovide a dropdown which shows the most commonly used signals as seen on the=
block chain, or a write-in.
Signalling within OP_RETURN increases the tx size and cost. This address ha=
shing method keeps the very small economic cost of voting off the chain, ra=
ther than passing it cumulatively to everyone with the insertion of additio=
nal data.
Since I wrote this I have come across a similar idea called CryptoVoter whi=
ch I think deserves more attention than it has had.
________________________________
From: Natanael <natanael.l@gmail.com>
Sent: Sunday, February 5, 2017 4:22 PM
To: Bitcoin Dev; John Hardy
Subject: Re: [bitcoin-dev] Transaction signalling through output address ha=
shing
Censorship by miners isn't the only problem. Existing and normal transactio=
ns will probabilistically collide with these schemes, and most wallets have=
no straightforward way of supporting it.
--_000_BL2PR03MB435DEA7CFB526C4DB58F740EE410BL2PR03MB435namprd_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
<p><span style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-=
size: 12pt;">Probabilistic collisions, while present, would be statisticall=
y insignificant at 4 chars length.</span><br>
</p>
<div style=3D"color: rgb(0, 0, 0);">
<div>
<div id=3D"divtagdefaultwrapper" dir=3D"ltr" style=3D"font-size:12pt; color=
:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p><br>
</p>
<p>Implementation by wallets would just require a loop of their existing ad=
dress generation until a match is found, trivial to implement. Wallets coul=
d provide a dropdown which shows the most commonly used signals as seen on =
the block chain, or a write-in.<br>
<br>
Signalling within OP_RETURN increases the tx size and cost. This address ha=
shing method keeps the very small economic cost of voting off the chain, ra=
ther than passing it cumulatively to everyone with the insertion of additio=
nal data.</p>
<p><br>
</p>
<p>Since I wrote this I have come across a similar idea called CryptoVoter =
which I think deserves more attention than it has had.</p>
<br>
<div style=3D"color:rgb(0,0,0)">
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Natanael <natanael=
.l@gmail.com><br>
<b>Sent:</b> Sunday, February 5, 2017 4:22 PM<br>
<b>To:</b> Bitcoin Dev; John Hardy<br>
<b>Subject:</b> Re: [bitcoin-dev] Transaction signalling through output add=
ress hashing</font>
<div><br>
</div>
</div>
<div>
<div dir=3D"auto">
<div dir=3D"auto">Censorship by miners isn't the only problem. Existing and=
normal transactions will probabilistically collide with these schemes, and=
most wallets have no straightforward way of supporting it. </div>
<div class=3D"gmail_extra" dir=3D"auto"></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>
--_000_BL2PR03MB435DEA7CFB526C4DB58F740EE410BL2PR03MB435namprd_--
|
