From: Alex Kotenko <alexykot@gmail.com>
To: Natanael <natanael.l@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Paper Currency
Date: Sun, 18 May 2014 19:47:46 +0100 [thread overview]
Message-ID: <CALDj+BbEY8+3feH8WQOr2f-VW1xZfq_WPgi3DmMAfOkZwJ2oJQ@mail.gmail.com> (raw)
In-Reply-To: <CAAt2M19KJTysuaFfT8rthsMk07UhQL3owBF4Q0Cc4SoKg3UBqw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Erm, few things here.
- I can't see really how to embed electronics capable to run an SPV
client into printed paper. I know that passive NFC tags can be printed on
paper, but not actual chips and/or power modules. So we are talking about a
completely different things here.
- even with paper notes printed proprietarily by some business the notes
itself still can have routes for independent blockchain-based verification,
and you won't need to trust anybody to test it. You will have to trust
security of the notes itself, but this is same as when you trust the phone
manufacturer when you're putting your bitcoin wallet on it.
So really I see only issues of technical security in here, and this is
the problem I'm seeking solutions for.
Best regards,
Alex Kotenko
2014-05-18 14:50 GMT+01:00 Natanael <natanael.l@gmail.com>:
> Now you are talking about Trusted Platform Modules. Like smartcards,
> actually. Devices that won't leak their keys but let the holder spend the
> coins. It could even have it's own simple SPV wallet client to make it
> easier to handle. And they'd use the attestation features provided by the
> TPM to prove the software it's unmodified top the current holder.
>
> But then you still have to trust the manufacturer of the device, and you
> have to trust it has no exploitable side channels.
>
> - Sent from my phone
> Den 18 maj 2014 13:52 skrev "Alex Kotenko" <alexykot@gmail.com>:
>
>
[-- Attachment #2: Type: text/html, Size: 2837 bytes --]
next prev parent reply other threads:[~2014-05-18 18:48 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 [this message]
2014-05-18 20:10 ` Natanael
2014-05-19 10:26 ` Alex Kotenko
2014-05-19 12:55 ` Sergio Lerner
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=CALDj+BbEY8+3feH8WQOr2f-VW1xZfq_WPgi3DmMAfOkZwJ2oJQ@mail.gmail.com \
--to=alexykot@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=natanael.l@gmail.com \
/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