From: 21E14 <21xe14@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP: Custodial Identities
Date: Thu, 21 Aug 2014 02:32:29 +0000 [thread overview]
Message-ID: <CAFZQHkFb_TtpV3RKoM5vAmXitph2xiAX36vXz50MdYuhNMfz+w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2488 bytes --]
Thank you for your feedback regarding Custodial Identities. I will address
it to the mailing list for transparency.
Think of it as a 1-of-2 multisig edge case where Custodian Identities are
actively managed by the Bitcoin Assigned Custodial Identities
Authority/Regional Bitcoin Custodial Identity Registries. Once the optional
identity layer is integrated, there are so many applications beyond dispute
resolution, if you could effortlessly inject Custodian Identities into the
blockchain itself as easily as providing 1-of-2 public keys.
Bitcoin Custodial Identities can be applied to coinbase transactions as
well, in any or all jurisdictions, thus providing further incentive to keep
nodes honest, or enabling a recovery mechanism in catastrophic failure
events, such as a break in SHA-256. Custodians provide account addresses
out of unused address space further alleviating address collisions as a
psychological barrier to adoption. Custodial to non-custodial transactions
could behave much like the UTXO of a coinbase transaction, which has the
special condition that it cannot be spent (used as an input) for at least
100 blocks. It's based on open market competition, and there will probably
always be users willing to live outside of the BCI address space.
>>On Tue, Aug 19, 2014 at 10:23 PM, 21E14 <21xe14@gmail.com> wrote:
>>
>>As suggested before submitting a BIP, I am sending this to the mailing
list.
>>
>>
>>Bitcoin is often described as “the currency of the Internet”, “the TCP/IP
of money”, or simply “the Internet of Money”. What is needed is an optional
identity layer — a Bitcoin Assigned Custodial Identities >>Authority, much
like the Internet Assigned Numbers Authority, to oversee global Custodial
Identity allocation. Such an authority delegates Custodial Identity Spaces
to Regional Bitcoin Custodial Identity >>Registries, much like the RIRs
(Regional Internet Registries) managing the allocation of Internet number
resources.
>>
>>A Bitcoin Custodial Identity (BCI) account address would consist of a
Custodial Identifier allocated by the BACIA/RBCIRs (much like a bank’s
routing number), and an account address (much like an account >>number).
Bitcoin Custodial Identities allow dispute resolution in the legal system
for transactions in the BCI address space. Free market would drive and
determine the demand for custodial accounts. P2PKH >>users not affected.
>>
>>Feedback is appreciated.
[-- Attachment #2: Type: text/html, Size: 2663 bytes --]
next reply other threads:[~2014-08-21 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 2:32 21E14 [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-20 2:23 [Bitcoin-development] BIP: Custodial Identities 21 e14
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=CAFZQHkFb_TtpV3RKoM5vAmXitph2xiAX36vXz50MdYuhNMfz+w@mail.gmail.com \
--to=21xe14@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