Skip to content

Commit 7743737

Browse files
committed
fixed headers style
1 parent dde2742 commit 7743737

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

bip-0175.mediawiki

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ The coin type field is identical to the same field in BIP-0044.
7272

7373
Hardened derivation is used at this level.
7474

75-
===Payment Address Generation===
75+
===Payment address generation===
7676

7777
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>.
7878

@@ -100,7 +100,7 @@ For a given contract documents denoted by c<sub>1</sub> ,...,c<sub>n</sub>, paym
100100

101101
7. Compute address of the public extended key (P2PKH) from step 6.
102102

103-
===Payment Address Verification===
103+
===Payment address verification===
104104

105105
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:
106106

@@ -115,7 +115,7 @@ The merchant should actively monitor the blockchain for the payment to the payme
115115
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.
116116
The act of making the payment to that address thus serves as a receipt for the customer.
117117

118-
===Hash to Partial Derivation Path Mapping===
118+
===Hash to partial derivation path mapping===
119119

120120
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.
121121

@@ -145,7 +145,7 @@ we can compute payment base as follows:
145145
146146
In the below examples, we are going to use SHA256 as a cryptographic hash function, and the above contract base public key.
147147

148-
====Payment address generation:====
148+
====Payment address generation====
149149

150150
As an input, we have a contract that consists of two documents, below are contents:
151151

@@ -195,7 +195,7 @@ document 2:
195195
1HYjhPTtMmpBJBd5tVepZDAVdvPA7o8KHJ
196196
197197

198-
====Verification example 1 (negative test):====
198+
====Verification example (negative test)====
199199

200200
Similar to the input above, except this time we have a contract that consists of one document, below is the content:
201201

0 commit comments

Comments
 (0)