From: 21E14 <21xe14@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] A look back and a look forward
Date: Fri, 9 Jan 2015 19:36:18 +0000 [thread overview]
Message-ID: <CAFZQHkF8mpPcGw0QnVed0rAxC7oOo2C6aNWrL3a+-vMYC2KroQ@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3VXnX7B7wQ4LOUCs+aifx747svyo5Gysw1SG0bgcT+WA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2979 bytes --]
> I think the observation about Target vs Bitcoin exchanges is a sharp one,
> but I'm not sure how your proposal helps. You say it's an optional
identity
> layer, but obviously any thief is going to opt out of being identified.
Let me translate it to this year's vocabulary. Think of BCIs as a
sidechain: let the legacy financial system migrate, to the extent desired,
to a more heavily regulated pegged sidechain with a stronger identity
layer. Let protocol-level rules regulate this nexus between the custodial
(sidechain) and non-custodial address spaces (blockchain). This isn't
entirely unlike the rules currently governing coin issuance i.e. coinbase
transactions. Let the market forces play it out. Iterate as needed. I
suspect that in retrospect it'll seem obvious. Many moons from now the
balance might shift between the two, but it won't matter much. The system
will have means to recover from catastrophic failure modes.
To help internalize such an evolution, please consider the layers the
Bitcoin protocol builds on top of: segment 52:32 ("The Internet is being
upgraded") of the BBC documentary "Inside The Dark Web" (
https://www.youtube.com/watch?v=qXajND7BQzk#t=3152). Kaspersky's comments a
few minutes earlier (50:06) aren't entirely out of context here either.
Clearly, the need is acute for Bitcoin to become institutional i.e. for
"billions of dollars of human value" to flow through it, as one Money 20/20
participant put it.
On Fri, Jan 9, 2015 at 2:00 PM, Mike Hearn <mike@plan99.net> wrote:
> This needn't be so, once an optional identity layer, modeled after the
>> Internet itself, is provided, as proposed in late August of last year on
>> this mailing list
>>
>
> I think the observation about Target vs Bitcoin exchanges is a sharp one,
> but I'm not sure how your proposal helps. You say it's an optional identity
> layer, but obviously any thief is going to opt out of being identified.
>
> For things like the Bitstamp hack, it's not clear how identity can help,
> because they were already doing KYC for all their customers. To take that
> further at the protocol level would require* all* transactions to have
> attached identity info, and that isn't going to happen - it wouldn't be
> Bitcoin, at that point.
>
> I think that long term, it's probably possible to defend private keys
> adequately, even for large sums of money (maybe not bitstamp-large but
> we'll see). You can have very minimalist secure hardware that would have
> some additional policies on top, like refusing to sign transactions without
> an identity proof of who controls the target address. Very tight hot
> wallets that risk analyse the instructions they're receiving have been
> proposed years ago.
>
> No such hardware presently exists, but that's mostly because
> implementations always lag behind a long way behind ideas rather than any
> fundamental technical bottleneck. Perhaps the Bitstamp event will finally
> spur development of such things forward.
>
[-- Attachment #2: Type: text/html, Size: 3761 bytes --]
prev parent reply other threads:[~2015-01-09 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 18:36 [Bitcoin-development] A look back and a look forward 21E14
2015-01-09 14:00 ` Mike Hearn
2015-01-09 19:36 ` 21E14 [this message]
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=CAFZQHkF8mpPcGw0QnVed0rAxC7oOo2C6aNWrL3a+-vMYC2KroQ@mail.gmail.com \
--to=21xe14@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.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