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 ) 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 ; Mon, 19 May 2014 15:34:06 +0200 From: "Martin Sip" To: "'Sergio Lerner'" , "'Alex Kotenko'" , "'bitcoin-development'" References: <5377892C.8080402@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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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

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