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

explain the usage of versions with regards to payment code behavior

Browse Source
This commit is contained in:
Justus Ranvier 2016-04-19 13:01:55 -05:00
parent 5d0b400823
commit 8b11b61981
No known key found for this signature in database
GPG Key ID: 930BC878BE23DF46
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
bip-0047.mediawiki
View File

@ -84,7 +84,19 @@ Hardened derivation is used at this level.
Except where noted, all keys derived from a payment code use the public derivation method.
==Standard Payment Codes (v1)==
==Versions==
Payment codes contain a version byte which identifies a specific set of behavior.
Unless otherwise specified, payment codes of different versions are interoperable. If Alice uses a version x payment code, and Bob uses a version y payment code, they can still send and receive transactions between each other.
Currently specified versions:
* Version 1
** Address type: P2PKH
** Notification type: address
==Version 1==
===Representation===
@ -127,6 +139,8 @@ It is assumed that Alice can easily obtain Bob's payment code via a suitable met
Prior to the first time Alice initiates a transaction to Bob, Alice MUST inform Bob of her payment code via the following procedure:
Note: this procedure is used if Bob uses a version 1 payment code (regardless of the the version of Alice's payment code). If Bob's payment code is not version 1, see the appropriate section in this specification.
# Alice constructs a transaction which sends a small quantity of bitcoins to Bob's notification address (notification transaction)
## The inputs selected for this transaction MUST NOT be easily associated with Alice's notification address
# Alice derives a unique shared secret using ECDH: