public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Sergio Lerner <sergiolerner@certimix.com>
To: Alex Kotenko <alexykot@gmail.com>,
	 bitcoin-development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Paper Currency
Date: Mon, 19 May 2014 09:55:20 -0300	[thread overview]
Message-ID: <5379FF38.4050909@certimix.com> (raw)
In-Reply-To: <CALDj+Bbsb6JiLabTBx21k02dDvnmZZDCXmJ2mnh7DngBon202w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 704 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1974 bytes --]

  parent reply	other threads:[~2014-05-19 12:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-17 15:31 [Bitcoin-development] Paper Currency Jerry Felix
2014-05-17 15:45 ` Matt Whitlock
2014-05-17 16:07 ` Chris Pacia
2014-05-17 16:40   ` Gregory Maxwell
2014-05-18 11:47     ` Alex Kotenko
2014-05-18 12:14       ` Andreas Schildbach
2014-05-18 12:51         ` Alex Kotenko
2014-05-19 13:06           ` Brooks Boyd
2014-05-19 13:50             ` Alex Kotenko
2014-05-18 13:50       ` Natanael
2014-05-18 18:47         ` Alex Kotenko
2014-05-18 20:10           ` Natanael
2014-05-19 10:26             ` Alex Kotenko
2014-05-19 12:55       ` Sergio Lerner [this message]
2014-05-19 13:34         ` Martin Sip
2014-05-19 13:53         ` Alex Kotenko
2014-05-19 14:47         ` [Bitcoin-development] patents Adam Back
2014-05-19 15:09           ` Mike Hearn
2014-05-19 18:27             ` Peter Todd
2014-05-19 18:40               ` Mike Hearn
2014-05-19 18:43             ` Gregory Maxwell
2014-05-19 18:46               ` Peter Todd
2014-05-19 18:49               ` Mike Hearn
2014-05-19 22:15             ` Bernd Jendrissek
2014-05-20 10:30           ` Jeff Garzik
2014-05-18 13:50 ` [Bitcoin-development] Paper Currency Andreas Schildbach
2014-05-19 12:21 ` Mike Hearn
2014-05-19 18:20   ` Justus Ranvier
2014-05-19 18:39     ` Peter Todd
2014-05-18 19:54 Jerry Felix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5379FF38.4050909@certimix.com \
    --to=sergiolerner@certimix.com \
    --cc=alexykot@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox