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
210
211
212
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <m.sip@volny.cz>) id 1WmNxU-0005Ol-Hf
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 13:50:28 +0000
Received-SPF: neutral (sog-mx-3.v43.ch3.sourceforge.com: 217.16.176.4 is
neither permitted nor denied by domain of volny.cz)
client-ip=217.16.176.4; envelope-from=m.sip@volny.cz;
helo=smtp.pipni.cz;
Received: from smtp.pipni.cz ([217.16.176.4])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WmNxS-00034V-HG
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 13:50:28 +0000
Received: from mail4.pipni.cz ([93.185.104.7])
id 1WmNho-0005UJ-Di; Mon, 19 May 2014 15:34:16 +0200
Received: from 247.216.broadband17.iol.cz ([109.80.216.247] helo=boss)
id 1WmNhe-0001Os-17 by authid <martin.sip@cupido.cz>;
Mon, 19 May 2014 15:34:06 +0200
From: "Martin Sip" <m.sip@volny.cz>
To: "'Sergio Lerner'" <sergiolerner@certimix.com>,
"'Alex Kotenko'" <alexykot@gmail.com>,
"'bitcoin-development'" <bitcoin-development@lists.sourceforge.net>
References: <BAY173-W1475F72C70BC089A82C20FCC300@phx.gbl> <5377892C.8080402@gmail.com> <CAAS2fgS-Ewj3T0-d=h7ET9dCz3+NPPYVOLDWd7T7oYY95x-sUA@mail.gmail.com> <CALDj+Bbsb6JiLabTBx21k02dDvnmZZDCXmJ2mnh7DngBon202w@mail.gmail.com>
<5379FF38.4050909@certimix.com>
In-Reply-To: <5379FF38.4050909@certimix.com>
Date: Mon, 19 May 2014 15:34:05 +0200
Message-ID: <001601cf7367$01666ff0$04334fd0$@volny.cz>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0017_01CF7377.C4F02A50"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQHxHiySbg9dEAGuHxzv8/3Y5dn0igLUpD8zAexwcQoCT6M6gAFzVZXJmsBwNjA=
Content-Language: cs
X-GeoIP: CZ
X-pipni-MailScanner-ID: 1WmNhe-0001Os-17
X-pipni-MailScanner: Found to be clean
X-pipni-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=2.388, required 6, AWL 0.06, BAYES_00 -1.90,
DOS_OUTLOOK_TO_MX 2.84, FSL_HELO_NON_FQDN_1 0.00,
HELO_NO_DOMAIN 0.00, HTML_MESSAGE 0.00, KHOP_THREADED -1.50,
RCVD_IN_RP_RNBL 1.31, RDNS_NONE 0.79, SPF_NEUTRAL 0.78)
X-pipni-MailScanner-SpamScore: 2
X-pipni-MailScanner-From: m.sip@volny.cz
X-Spam-Score: 1.7 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [217.16.176.4 listed in list.dnswl.org]
0.7 SPF_NEUTRAL SPF: sender does not match SPF record (neutral)
1.0 HTML_MESSAGE BODY: HTML included in message
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay
lines
X-Headers-End: 1WmNxS-00034V-HG
Subject: Re: [Bitcoin-development] Paper Currency
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: Mon, 19 May 2014 13:50:28 -0000
This is a multipart message in MIME format.
------=_NextPart_000_0017_01CF7377.C4F02A50
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Alex,
I think the problem of making paper bitcoins is equivalent to the idea of
creating paper implementation of bitcoin sidechain. Hard one in my mind. If
we could resolve this one in secure and decentralized way it would be the
same breakthrough as bitcoin itself is.
Martin Sip
On 18/05/2014 08:47 a.m., Alex Kotenko wrote:
One problem we couldn't figure out here though - how to protect the notes
from unauthorized redeem. Like if someone else tries to reach your wallet
with his own NFC - how can we distinguish between deliberate redeem by owner
and fraudulent redeem by anybody else with custom built long range NFC
antenna? Any ideas?
The firmcoin has two capacitive buttons that you have to press in sequence
to redeem to coins. No long range antenna can do that.
Best regards,
Sergio.
PS: the device has patents pending
------=_NextPart_000_0017_01CF7377.C4F02A50
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite lang=3DCS =
link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-fareast-language:EN-US'>Alex,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-fareast-language:EN-US'>I think the problem of making paper =
bitcoins is equivalent to the idea of creating paper implementation of =
bitcoin sidechain. Hard one in my mind. If we could resolve this one in =
secure and decentralized way it would be the same breakthrough as =
bitcoin itself is.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-fareast-language:EN-US'>Martin Sip<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><p =
class=3DMsoNormal>On 18/05/2014 08:47 a.m., Alex Kotenko =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New";color:#003300'><o:p> </o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New";color:#003300'><o:p> </o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New";color:#003300'>One problem we couldn't figure out here though - how =
to protect the notes from unauthorized redeem. Like if someone else =
tries to reach your wallet with his own NFC - how can we distinguish =
between deliberate redeem by owner and fraudulent redeem by anybody else =
with custom built long range NFC antenna? Any =
ideas?<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New";color:#003300'><o:p> </o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New";color:#003300'><o:p> </o:p></span></p></div></div></blockquote>=
<p class=3DMsoNormal>The firmcoin has two capacitive buttons that you =
have to press in sequence to redeem to coins. No long range antenna can =
do that.<br><br>Best regards,<br> Sergio.<br><br>PS: the =
device has patents pending <o:p></o:p></p></div></body></html>
------=_NextPart_000_0017_01CF7377.C4F02A50--
|
