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

add missing change notification and minor corrections

Browse Source
This commit is contained in:
Justus Ranvier 2015-12-18 10:14:13 -06:00
parent 6bfc0151a7
commit 876af7fa87
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
bip-0047.mediawiki
View File

@ -1,5 +1,7 @@
RECENT CHANGES: RECENT CHANGES:
* (12 Oct 2015) Revise blinding method for notification transactions
* (21 Sep 2015) Correct base58check version byte * (21 Sep 2015) Correct base58check version byte
* (18 Sep 2015) Clarify decoding of notification transactions * (18 Sep 2015) Clarify decoding of notification transactions
@ -57,11 +59,15 @@ Hardened derivation is used at this level.
Except where noted, all keys derived from a payment code use the public derivation method. Except where noted, all keys derived from a payment code use the public derivation method.
==Standard Payment Codes (v1)==
===Representation===
====Binary Serialization==== ====Binary Serialization====
A payment code contains the following elements: A payment code contains the following elements:
* Byte 0: type. required value: 0x01 * Byte 0: version. required value: 0x01
* Byte 1: features bit field. All bits must be zero except where specified elsewhere in this specification * Byte 1: features bit field. All bits must be zero except where specified elsewhere in this specification
** Bit 0: Bitmessage notification ** Bit 0: Bitmessage notification
** Bits 1-7: reserved ** Bits 1-7: reserved
@ -233,7 +239,7 @@ A recipient prefers to receive notifications via Bitmessage indiates this prefer
* Setting bit 0 of the features byte to 1 * Setting bit 0 of the features byte to 1
* Setting byte 67 of the serialized payment code to the desired Bitmessage address version * Setting byte 67 of the serialized payment code to the desired Bitmessage address version
* Setting byte 67 of the serialized payment code to the desired Bitmessage stream number * Setting byte 68 of the serialized payment code to the desired Bitmessage stream number
The sender uses this information to construct a valid notification Bitmessage address: The sender uses this information to construct a valid notification Bitmessage address: