1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <21xe14@gmail.com>) id 1XKIB2-0007rW-Bh
for bitcoin-development@lists.sourceforge.net;
Thu, 21 Aug 2014 02:32:36 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.194 as permitted sender)
client-ip=74.125.82.194; envelope-from=21xe14@gmail.com;
helo=mail-we0-f194.google.com;
Received: from mail-we0-f194.google.com ([74.125.82.194])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XKIB1-00036u-Cn
for bitcoin-development@lists.sourceforge.net;
Thu, 21 Aug 2014 02:32:36 +0000
Received: by mail-we0-f194.google.com with SMTP id u56so2951230wes.1
for <bitcoin-development@lists.sourceforge.net>;
Wed, 20 Aug 2014 19:32:29 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.59.42 with SMTP id w10mr17295904wjq.15.1408588349135;
Wed, 20 Aug 2014 19:32:29 -0700 (PDT)
Received: by 10.194.15.36 with HTTP; Wed, 20 Aug 2014 19:32:29 -0700 (PDT)
Date: Thu, 21 Aug 2014 02:32:29 +0000
Message-ID: <CAFZQHkFb_TtpV3RKoM5vAmXitph2xiAX36vXz50MdYuhNMfz+w@mail.gmail.com>
From: 21E14 <21xe14@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7b86dde02f89a205011a882a
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: 1XKIB1-00036u-Cn
Subject: Re: [Bitcoin-development] BIP: Custodial Identities
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 21 Aug 2014 02:32:36 -0000
--047d7b86dde02f89a205011a882a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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 =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 >>Authorit=
y, 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.
--047d7b86dde02f89a205011a882a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Thank you for your feedback regarding Custodial Identities=
. I will address it to the mailing list for transparency.<br><br>Think of i=
t as a 1-of-2 multisig edge case where Custodian Identities are actively ma=
naged by the Bitcoin Assigned Custodial Identities Authority/Regional Bitco=
in Custodial Identity Registries. Once the optional identity layer is integ=
rated, there are so many applications beyond dispute resolution, if you cou=
ld effortlessly inject Custodian Identities into the blockchain itself as e=
asily as providing 1-of-2 public keys.<br>
<br>Bitcoin Custodial Identities can be applied to coinbase transactions as=
well, in any or all jurisdictions, thus providing further incentive to kee=
p nodes honest, or enabling a recovery mechanism in catastrophic failure ev=
ents, such as a break in SHA-256. Custodians provide account addresses out =
of unused address space further alleviating address collisions as a psychol=
ogical barrier to adoption. Custodial to non-custodial transactions could b=
ehave much like the UTXO of a coinbase transaction, which has the special c=
ondition 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.<br>
<br><br>>>On Tue, Aug 19, 2014 at 10:23 PM, 21E14 <<a href=3D"mail=
to:21xe14@gmail.com">21xe14@gmail.com</a>> wrote:<br>>><br>>>=
;As suggested before submitting a BIP, I am sending this to the mailing lis=
t.<br>
>><br>>><br>>>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, o=
r simply =E2=80=9Cthe Internet of Money=E2=80=9D. What is needed is an opti=
onal identity layer =E2=80=94 a Bitcoin Assigned Custodial Identities >&=
gt;Authority, much like the Internet Assigned Numbers Authority, to oversee=
global Custodial Identity allocation. Such an authority delegates Custodia=
l Identity Spaces to Regional Bitcoin Custodial Identity >>Registries=
, much like the RIRs (Regional Internet Registries) managing the allocation=
of Internet number resources.<br>
>><br>>>A Bitcoin Custodial Identity (BCI) account address woul=
d consist of a Custodial Identifier allocated by the BACIA/RBCIRs (much lik=
e a bank=E2=80=99s routing number), and an account address (much like an ac=
count >>number). Bitcoin Custodial Identities allow dispute resolutio=
n in the legal system for transactions in the BCI address space. Free marke=
t would drive and determine the demand for custodial accounts. P2PKH >&g=
t;users not affected.<br>
>><br>>>Feedback is appreciated.<br><br></div>
--047d7b86dde02f89a205011a882a--
|
