From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: <5377892C.8080402@gmail.com> <5379FF38.4050909@certimix.com> From: Alex Kotenko Date: Mon, 19 May 2014 14:53:04 +0100 X-Google-Sender-Auth: 3IaPTPUejlB4b5teeY7wFblTdFQ Message-ID: To: Sergio Lerner 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 Subject: Re: [Bitcoin-development] Paper Currency X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 : > 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
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.


Best regards,=C2=A0
Alex Kotenko


2014-05-19 13:55 GMT+01:00 Sergio Lerner= <sergiolerner@certimix.com>:
=20 =20 =20
Alex,

=C2=A0=C2=A0=C2=A0 I think that what you are talking about more or less= something like the Firmcoin

=C2=A0=C2=A0=C2=A0 Check: http://firmcoin.com/?p=3D92



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=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?


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,
=C2=A0Sergio.

PS: =C2=A0 the device has patents pending

--bcaec547c49b786ba804f9c117ac--