mirrors/bitcoin-bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-01-19 05:45:07 +01:00
Code Issues Projects Releases Wiki Activity

Merge pull request #598 from commerceblock/os_bip175-style-fix

Browse Source 
BIP175: fixed headers style
This commit is contained in:
Luke Dashjr 2017-10-03 06:53:26 +00:00 committed by GitHub
commit f6beebafd2
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
bip-0175.mediawiki
View File

@ -72,7 +72,7 @@ The coin type field is identical to the same field in BIP-0044.
Hardened derivation is used at this level.
===Payment Address Generation===
===Payment address generation===
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>.
@ -100,7 +100,7 @@ For a given contract documents denoted by c<sub>1</sub> ,...,c<sub>n</sub>, paym
7. Compute address of the public extended key (P2PKH) from step 6.
===Payment Address Verification===
===Payment address verification===
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:
@ -115,7 +115,7 @@ The merchant should actively monitor the blockchain for the payment to the payme
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.
The act of making the payment to that address thus serves as a receipt for the customer.
===Hash to Partial Derivation Path Mapping===
===Hash to partial derivation path mapping===
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.
@ -145,7 +145,7 @@ we can compute payment base as follows:
In the below examples, we are going to use SHA256 as a cryptographic hash function, and the above contract base public key.
====Payment address generation:====
====Payment address generation====
As an input, we have a contract that consists of two documents, below are contents:
@ -195,7 +195,7 @@ document 2:
1HYjhPTtMmpBJBd5tVepZDAVdvPA7o8KHJ
====Verification example 1 (negative test):====
====Verification example (negative test)====
Similar to the input above, except this time we have a contract that consists of one document, below is the content: