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 ) 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 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 , bitcoin-development References: <5377892C.8080402@gmail.com> In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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--