You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: bip-0175.mediawiki
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ The coin type field is identical to the same field in BIP-0044.
72
72
73
73
Hardened derivation is used at this level.
74
74
75
-
===Payment Address Generation===
75
+
===Payment address generation===
76
76
77
77
For a given contract documents denoted by c<sub>1</sub> ,...,c<sub>n</sub>, payment base extended public key denoted by <code>payment_base</code>, and cryptographic hash function denoted by <code>h</code>.
78
78
@@ -100,7 +100,7 @@ For a given contract documents denoted by c<sub>1</sub> ,...,c<sub>n</sub>, paym
100
100
101
101
7. Compute address of the public extended key (P2PKH) from step 6.
102
102
103
-
===Payment Address Verification===
103
+
===Payment address verification===
104
104
105
105
For a given Bitcoin address, <code>payment_base</code> extended public key, contract documents denoted by c<sub>1</sub>,...,c<sub>n</sub>, and cryptographic hash function denoted by <code>h</code>, we can verify the integrity of the address by the following steps:
106
106
@@ -115,7 +115,7 @@ The merchant should actively monitor the blockchain for the payment to the payme
115
115
Because the address is generated from the payment base and the contract, the merchant must implicitly agree to those terms in order to spend the funds.
116
116
The act of making the payment to that address thus serves as a receipt for the customer.
117
117
118
-
===Hash to Partial Derivation Path Mapping===
118
+
===Hash to partial derivation path mapping===
119
119
120
120
At this section, we define hash to partial BIP32 derivation path mapping procedure that maps between an arbitrary hex number to a partial BIP32 derivation path.
121
121
@@ -145,7 +145,7 @@ we can compute payment base as follows:
145
145
146
146
In the below examples, we are going to use SHA256 as a cryptographic hash function, and the above contract base public key.
147
147
148
-
====Payment address generation:====
148
+
====Payment address generation====
149
149
150
150
As an input, we have a contract that consists of two documents, below are contents:
151
151
@@ -195,7 +195,7 @@ document 2:
195
195
1HYjhPTtMmpBJBd5tVepZDAVdvPA7o8KHJ
196
196
197
197
198
-
====Verification example 1 (negative test):====
198
+
====Verification example (negative test)====
199
199
200
200
Similar to the input above, except this time we have a contract that consists of one document, below is the content:
0 commit comments