Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <21xe14@gmail.com>) id 1XJvYs-0001S9-2m for bitcoin-development@lists.sourceforge.net; Wed, 20 Aug 2014 02:23:42 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.193 as permitted sender) client-ip=209.85.212.193; envelope-from=21xe14@gmail.com; helo=mail-wi0-f193.google.com; Received: from mail-wi0-f193.google.com ([209.85.212.193]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XJvYr-0000Cc-7R for bitcoin-development@lists.sourceforge.net; Wed, 20 Aug 2014 02:23:42 +0000 Received: by mail-wi0-f193.google.com with SMTP id f8so2485009wiw.8 for ; Tue, 19 Aug 2014 19:23:35 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.2.12 with SMTP id 12mr54000068wjq.54.1408501415021; Tue, 19 Aug 2014 19:23:35 -0700 (PDT) Received: by 10.194.15.36 with HTTP; Tue, 19 Aug 2014 19:23:34 -0700 (PDT) Date: Wed, 20 Aug 2014 02:23:34 +0000 Message-ID: From: 21 e14 <21xe14@gmail.com> To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=047d7b3a87608212c40501064a34 X-Spam-Score: -0.3 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (21xe14[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (21xe14[at]gmail.com) 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XJvYr-0000Cc-7R Subject: [Bitcoin-development] BIP: Custodial Identities 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: Wed, 20 Aug 2014 02:23:42 -0000 --047d7b3a87608212c40501064a34 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable As suggested before submitting a BIP, I am sending this to the mailing list= . Bitcoin is often described as =E2=80=9Cthe currency of the Internet=E2=80= =9D, =E2=80=9Cthe TCP/IP of money=E2=80=9D, or simply =E2=80=9Cthe Internet of Money=E2=80=9D. What = is needed is an optional identity layer =E2=80=94 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=E2=80= =99s 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. --047d7b3a87608212c40501064a34 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

As suggested before submitting a BIP, I am sending t= his to the mailing list.


Bitcoin is often describ= ed as =E2=80=9Cthe currency of the Internet=E2=80=9D, =E2=80=9Cthe TCP/IP of money=E2=80=9D, o= r simply =E2=80=9Cthe Internet of Money=E2=80=9D. What is needed is an optional identity layer =E2=80=94 a Bi= tcoin 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 RIR= s (Regional Internet Registries) managing the allocation of Internet number r= esources.

A Bitcoin Custodial Iden= tity (BCI) account address would consist of a Custodial Identifier allocated by the BACIA/RBCI= Rs (much like a bank=E2=80=99s routing number), and an account address (much l= ike an account number). Bitcoin Custodial Identities allow dispute resolution in the legal system for transactions in the BCI address space. Free market would drive a= nd determine the demand for custodial accounts. P2PKH users not affected.

<= p class=3D"MsoNormal" style=3D"text-indent:0.5in">

Feedback is appreciated.


--047d7b3a87608212c40501064a34--