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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <sergiolerner@certimix.com>) id 1WmN6I-0002wB-RS
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 12:55:30 +0000
X-ACL-Warn:
Received: from p3plsmtpa12-03.prod.phx3.secureserver.net ([68.178.252.232])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WmN6G-0002x8-QY for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 12:55:30 +0000
Received: from [192.168.0.23] ([201.231.95.129])
by p3plsmtpa12-03.prod.phx3.secureserver.net with
id 3ovM1o0032nUpUh01ovN23; Mon, 19 May 2014 05:55:23 -0700
Message-ID: <5379FF38.4050909@certimix.com>
Date: Mon, 19 May 2014 09:55:20 -0300
From: Sergio Lerner <sergiolerner@certimix.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: 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>
In-Reply-To: <CALDj+Bbsb6JiLabTBx21k02dDvnmZZDCXmJ2mnh7DngBon202w@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: multipart/alternative;
boundary="------------000309070302010003050508"
X-Spam-Score: 1.0 (+)
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 [68.178.252.232 listed in list.dnswl.org]
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WmN6G-0002x8-QY
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 12:55:31 -0000
This is a multi-part message in MIME format.
--------------000309070302010003050508
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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
--------------000309070302010003050508
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Alex,<br>
<br>
I think that what you are talking about more or less something
like the Firmcoin<br>
<br>
Check: <a class="moz-txt-link-freetext" href="http://firmcoin.com/?p=92">http://firmcoin.com/?p=92</a><br>
<br>
<br>
<div class="moz-cite-prefix">On 18/05/2014 08:47 a.m., Alex Kotenko
wrote:<br>
</div>
<blockquote
cite="mid:CALDj+Bbsb6JiLabTBx21k02dDvnmZZDCXmJ2mnh7DngBon202w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:'courier
new',monospace;color:rgb(0,51,0)"><br>
</div>
<div class="gmail_default" style="font-family:'courier
new',monospace;color:rgb(0,51,0)"><br>
</div>
<div class="gmail_default" style="font-family:'courier
new',monospace;color:rgb(0,51,0)">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?</div>
<div class="gmail_default" style="font-family:'courier
new',monospace;color:rgb(0,51,0)"><br>
</div>
<div class="gmail_default" style="font-family:'courier
new',monospace;color:rgb(0,51,0)"><br>
</div>
</div>
</blockquote>
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
</body>
</html>
--------------000309070302010003050508--
|
