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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <alexy.kot.all@gmail.com>) id 1WmO0l-0005Zp-6b
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 13:53:51 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.179 as permitted sender)
client-ip=209.85.220.179; envelope-from=alexy.kot.all@gmail.com;
helo=mail-vc0-f179.google.com;
Received: from mail-vc0-f179.google.com ([209.85.220.179])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WmO0k-0006ye-6S
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 13:53:51 +0000
Received: by mail-vc0-f179.google.com with SMTP id im17so9475606vcb.38
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 May 2014 06:53:44 -0700 (PDT)
X-Received: by 10.52.182.227 with SMTP id eh3mr12222864vdc.40.1400507624612;
Mon, 19 May 2014 06:53:44 -0700 (PDT)
MIME-Version: 1.0
Sender: alexy.kot.all@gmail.com
Received: by 10.58.211.135 with HTTP; Mon, 19 May 2014 06:53:04 -0700 (PDT)
In-Reply-To: <5379FF38.4050909@certimix.com>
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>
From: Alex Kotenko <alexykot@gmail.com>
Date: Mon, 19 May 2014 14:53:04 +0100
X-Google-Sender-Auth: 3IaPTPUejlB4b5teeY7wFblTdFQ
Message-ID: <CALDj+BaG=t-j51kb4y_LYuhBwHZDnps0pSUZHyzLghkD+ChrVQ@mail.gmail.com>
To: Sergio Lerner <sergiolerner@certimix.com>
Content-Type: multipart/alternative; boundary=bcaec547c49b786ba804f9c117ac
X-Spam-Score: -0.3 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(alexy.kot.all[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.3 HTML_FONT_FACE_BAD BODY: HTML font face is not a word
-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: 1WmO0k-0006ye-6S
Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net>
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:53:51 -0000
--bcaec547c49b786ba804f9c117ac
Content-Type: text/plain; charset=UTF-8
Hmm, this is firmcoin thing looks like what I mean. They don't have a
solution yet, and prices they quote smartcards are unacceptable, but if
they will manage to get down in selfcost - that may work. Ok, I'll follow
them and see what it will come to.
Best regards,
Alex Kotenko
2014-05-19 13:55 GMT+01:00 Sergio Lerner <sergiolerner@certimix.com>:
> Alex,
>
> I think that what you are talking about more or less something like
> the Firmcoin
>
> Check: http://firmcoin.com/?p=92
>
>
>
> 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
>
--bcaec547c49b786ba804f9c117ac
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:courier =
new,monospace;color:#003300">Hmm, this is firmcoin thing looks like what I =
mean. They don't have a solution yet, and prices they quote smartcards =
are unacceptable, but if they will manage to get down in selfcost - that ma=
y work. Ok, I'll follow them and see what it will come to.</div>
<div class=3D"gmail_default" style=3D"font-family:courier new,monospace;col=
or:#003300"><br></div><div class=3D"gmail_extra"><br clear=3D"all"><div><di=
v dir=3D"ltr"><span style=3D"color:rgb(0,51,0);font-family:'courier new=
',monospace">Best regards,=C2=A0</span><div>
<div><div style=3D"text-align:left"><font color=3D"#003300" face=3D"'co=
urier new', monospace" style=3D"text-align:-webkit-auto">Alex Kotenko</=
font></div></div></div></div></div>
<br><br><div class=3D"gmail_quote">2014-05-19 13:55 GMT+01:00 Sergio Lerner=
<span dir=3D"ltr"><<a href=3D"mailto:sergiolerner@certimix.com" target=
=3D"_blank">sergiolerner@certimix.com</a>></span>:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
=20
=20
=20
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
Alex,<br>
<br>
=C2=A0=C2=A0=C2=A0 I think that what you are talking about more or less=
something
like the Firmcoin<br>
<br>
=C2=A0=C2=A0=C2=A0 Check: <a href=3D"http://firmcoin.com/?p=3D92" targe=
t=3D"_blank">http://firmcoin.com/?p=3D92</a><div class=3D""><br>
<br>
<br>
<div>On 18/05/2014 08:47 a.m., Alex Kotenko
wrote:<br>
</div>
<blockquote type=3D"cite">
<div dir=3D"ltr">
<div><br>
</div>
<div><br>
</div>
<div>One problem we couldn't
figure out here though - how to protect the notes from
unauthorized=C2=A0redeem. Like if someone else tries to reach you=
r
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=C2=A0NFC antenna? Any ideas?</d=
iv>
<div><br>
</div>
<div><br>
</div>
</div>
</blockquote></div>
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>
=C2=A0Sergio.<br>
<br>
PS: =C2=A0 the device has patents pending
</div>
</blockquote></div><br></div></div>
--bcaec547c49b786ba804f9c117ac--
|
