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
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
|
Return-Path: <omarshib@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 929EB516
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 14 Aug 2017 06:05:37 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4A9E0A6
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 14 Aug 2017 06:05:37 +0000 (UTC)
Received: by mail-wm0-f46.google.com with SMTP id i66so35386205wmg.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 13 Aug 2017 23:05:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=s9MfeKkAqgTz/sKlMejfObKmebDfG0jjcrHWhpa7E+E=;
b=VAFL7vB5s6bTwfYjoGjto2929MQLCbR66UCXth3jblpRDRHJC/V72jp1o5Vrt8VM30
LTaWVy291IWAuCCcTgMk1MpNlJfs5iJ4nAINWiKwsgIDbsJViWUAZkj0O+NCiXTsz61R
ptsJcevs98pYWyRcdCCfgDFEGNFKVws3w2b65P/zsFtsJFaQJpcuh+s9eSvmNd827F8R
e4RqSlK+DJriaCLGfNiSAbqkgDIlBNDS8H75tZugZ6XMEc1pTsJODubncNflnXowsXZj
0kZ3pEiUg/grFAqsX9drNDVRfXNFgzZ72oBiVi9tS6r/NK2fhc4bfvk6rFujUw4w3aoU
iksA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=s9MfeKkAqgTz/sKlMejfObKmebDfG0jjcrHWhpa7E+E=;
b=qGpk7Kp7DToekdDZZ9ecDOEotbfOyRMn2eqT1Vn5gBZb4DNWN1t6Ypg+xH4/Hcc0a4
zSgm6hiERkszIezOc6W4Lu7/rDFCdm1drMMdcGzL2JVwz5zyssRuemN1Vdh/WYEyrDdx
bLu5OKIMJeHb9MADeTNBkcL+ZFgJMcaHHNuBpiUudVYdKk+DoZgQ7tL6LiHYitaniYFY
TjbrKZb9N16NaCmoZyezX54dTlt0WTPP50FHwGVKDgByRCKMSEXf3RPbhxvEMEutbDiC
golS8Ir5m2q46Ri+mR1UicSuzxwGSlGdeUWAhR/Fu5DWCCjky8LUsXrZiMy7HWtH4tRD
JbQg==
X-Gm-Message-State: AHYfb5hS9L2WO+HgAvk2o/+xX8adCwj9SKY/LEi1mFgFw0j0LyOFwGcf
fZ0LuUZOvicvnPjgiirl3X9AFI8T5TD1prE=
X-Received: by 10.28.193.203 with SMTP id r194mr3305959wmf.85.1502690735660;
Sun, 13 Aug 2017 23:05:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.171.232 with HTTP; Sun, 13 Aug 2017 23:05:35 -0700 (PDT)
From: omar shibli <omarshib@gmail.com>
Date: Mon, 14 Aug 2017 09:05:35 +0300
Message-ID: <CAE3EOfgJdrO29GCftwORcq0087X0Y74gYtuMWvO1EWEkrT-7rg@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="94eb2c13158e81a4da0556b073a9"
X-Mailman-Approved-At: Tue, 15 Aug 2017 02:32:01 +0000
Subject: [bitcoin-dev] BIP proposal, Pay to Contract BIP43 Application
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Aug 2017 06:05:37 -0000
--94eb2c13158e81a4da0556b073a9
Content-Type: text/plain; charset="UTF-8"
Hey all,
A lot of us familiar with the pay to contract protocol, and how it uses
cleverly the homomorphic property of elliptic curve encryption system to
achieve it.
Unfortunately, there is no standard specification on how to conduct such
transactions in the cyberspace.
We have developed a basic trade finance application that relies on the
original idea described in the Homomorphic Payment Addresses and the
Pay-to-Contract Protocol paper, yet we have generalized it and made it
BIP43 complaint.
We would like to share our method, and get your feedback about it,
hopefully this effort will result into a standard for the benefit of the
community.
Abstract idea:
We define the following levels in BIP32 path.
m / purpose' / coin_type' / contract_id' / *
contract_id is is an arbitrary number within the valid range of indices.
Then we define, contract base as following prefix:
m / purpose' / coin_type' / contract_id'
contract commitment address is computed as follows:
hash document using cryptographic hash function of your choice (e.g. blake2)
map hash to partial derivation path
Convert hash to binary array.
Partition the array into parts, each part length should be 16.
Convert each part to integer in decimal format.
Convert each integer to string.
Join all strings with slash `/`.
compute child public key by chaining the derivation path from step 2 with
contract base:
m/<contract_base>/<hash_derivation_path>
compute address
Example:
master private extended key:
xprv9s21ZrQH143K2JF8RafpqtKiTbsbaxEeUaMnNHsm5o6wCW3z8ySyH4UxFVSfZ8n7ESu7fgir8imbZKLYVBxFPND1pniTZ81vKfd45EHKX73
coin type: 0
contract id: 7777777
contract base computation :
derivation path:
m/999'/0'/7777777'
contract base public extended key:
xpub6CMCS9rY5GKdkWWyoeXEbmJmxGgDcbihofyARxucufdw7k3oc1JNnniiD5H2HynKBwhaem4KnPTue6s9R2tcroqkHv7vpLFBgbKRDwM5WEE
Contract content:
foo
Contract sha256 signature:
2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae
Contract partial derivation path:
11302/46187/26879/50831/63899/17724/7472/16692/4930/11632/25731/49056/63882/24200/25190/59310
Contract commitment pub key path:
m/999'/0'/7777777'/11302/46187/26879/50831/63899/17724/7472/16692/4930/11632/25731/49056/63882/24200/25190/59310
or
<contract_base_extended_pub_key>/11302/46187/26879/50831/63899/17724/7472/16692/4930/11632/25731/49056/63882/24200/25190/59310
Contract commitment pub key:
xpub6iQVNpbZxdf9QJC8mGmz7cd3Cswt2itcQofZbKmyka5jdvQKQCqYSDFj8KCmRm4GBvcQW8gaFmDGAfDyz887msEGqxb6Pz4YUdEH8gFuaiS
Contract commitment address:
17yTyx1gXPPkEUN1Q6Tg3gPFTK4dhvmM5R
You can find the full BIP draft in the following link:
https://github.com/commerceblock/pay-to-contract-protocol-specification/blob/master/bip-draft.mediawiki
Regards,
Omar
--94eb2c13158e81a4da0556b073a9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Hey all,</div><div><br></div><div>A lot of us familia=
r with the pay to contract protocol, and how it uses cleverly the homomorph=
ic property of elliptic curve encryption system to achieve it.</div><div>Un=
fortunately, there is no standard specification on how to conduct such tran=
sactions in the cyberspace.</div><div><br></div><div>We have developed a ba=
sic trade finance application that relies on the original idea described in=
the Homomorphic Payment Addresses and the Pay-to-Contract Protocol paper, =
yet we have generalized it and made it BIP43 complaint.</div><div><br></div=
><div>We would like to share our method, and get your feedback about it, ho=
pefully this effort will result into a standard for the benefit of the comm=
unity.</div><div><br></div><div>Abstract idea:</div><div><br></div><div>We =
define the following levels in BIP32 path.</div><div>m / purpose' / coi=
n_type' / contract_id' / *=C2=A0</div><div><br></div><div>contract_=
id is is an arbitrary number within the valid range of indices.</div><div><=
br></div><div>Then we define, contract base as following prefix:=C2=A0</div=
><div>m / purpose' / coin_type' / contract_id'</div><div><br></=
div><div>contract commitment address is computed as follows:</div><div>hash=
document using cryptographic hash function of your choice (e.g. blake2)</d=
iv><div>map hash to partial derivation path</div><div>Convert hash to binar=
y array.</div><div>Partition the array into parts, each part length should =
be 16.</div><div>Convert each part to integer in decimal format.</div><div>=
Convert each integer to string.</div><div>Join all strings with slash `/`.<=
/div><div>compute child public key by chaining the derivation path from ste=
p 2 with contract base:</div><div>m/<contract_base>/<hash_derivati=
on_path></div><div>compute address</div><div>Example:</div><div><br></di=
v><div>master private extended key:=C2=A0</div><div>xprv9s21ZrQH143K2JF8Raf=
pqtKiTbsbaxEeUaMnNHsm5o6wCW3z8ySyH4UxFVSfZ8n7ESu7fgir8imbZKLYVBxFPND1pniTZ8=
1vKfd45EHKX73</div><div>coin type: 0</div><div>contract id: 7777777=C2=A0</=
div><div><br></div><div>contract base computation :</div><div><br></div><di=
v>derivation path:=C2=A0</div><div>m/999'/0'/7777777'=C2=A0</di=
v><div>contract base public extended key:=C2=A0</div><div>xpub6CMCS9rY5GKdk=
WWyoeXEbmJmxGgDcbihofyARxucufdw7k3oc1JNnniiD5H2HynKBwhaem4KnPTue6s9R2tcroqk=
Hv7vpLFBgbKRDwM5WEE=C2=A0</div><div><br></div><div>Contract content:</div><=
div>foo</div><div><br></div><div>Contract sha256 signature:</div><div>2c26b=
46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae=C2=A0</div><div=
><br></div><div>Contract partial derivation path:</div><div>11302/46187/268=
79/50831/63899/17724/7472/16692/4930/11632/25731/49056/63882/24200/25190/59=
310</div><div><br></div><div>Contract commitment pub key path:</div><div>m/=
999'/0'/7777777'/11302/46187/26879/50831/63899/17724/7472/16692=
/4930/11632/25731/49056/63882/24200/25190/59310</div><div>or</div><div><=
contract_base_extended_pub_key>/11302/46187/26879/50831/63899/17724/7472=
/16692/4930/11632/25731/49056/63882/24200/25190/59310</div><div><br></div><=
div>Contract commitment pub key:</div><div>xpub6iQVNpbZxdf9QJC8mGmz7cd3Cswt=
2itcQofZbKmyka5jdvQKQCqYSDFj8KCmRm4GBvcQW8gaFmDGAfDyz887msEGqxb6Pz4YUdEH8gF=
uaiS</div><div><br></div><div>Contract commitment address:</div><div>17yTyx=
1gXPPkEUN1Q6Tg3gPFTK4dhvmM5R</div><div><br></div><div><br></div><div>You ca=
n find the full BIP draft in the following link:</div><div><a href=3D"https=
://github.com/commerceblock/pay-to-contract-protocol-specification/blob/mas=
ter/bip-draft.mediawiki">https://github.com/commerceblock/pay-to-contract-p=
rotocol-specification/blob/master/bip-draft.mediawiki</a></div><div><br></d=
iv><div><br></div><div>Regards,</div><div>Omar</div></div>
--94eb2c13158e81a4da0556b073a9--
|
