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
This BIP can be be considered final in terms of enabling compatibility with wallets that implement version 1 and version 2 reusable payment codes, however future developments of the reusable payment codes specification will not be distributed via the BIP process.
21
+
22
+
The Open Bitcoin Privacy Project RFC repo should be consulted for specifications related to version 3 or higher payment codes: https://github.com/OpenBitcoinPrivacyProject/rfc
23
+
18
24
==Abstract==
19
25
20
26
This BIP defines a technique for creating a payment code which can be publicly advertised and associated with a real-life identity without creating the loss of security or privacy inherent to P2PKH address reuse.
@@ -158,7 +164,7 @@ Note: this procedure is used if Bob uses a version 1 payment code (regardless of
158
164
## Alice selects the private key corresponding to the designated pubkey: <pre>a</pre>
159
165
## Alice selects the public key associated with Bob's notification address: <pre>B, where B = bG</pre>
160
166
## Alice calculates a secret point: <pre>S = aB</pre>
161
-
## Alice calculates a 64 byte blinding factor: <pre>s = HMAC-SHA512(x, o)</pre>
167
+
## Alice calculates a 64 byte blinding factor: <pre>s = HMAC-SHA512(o, x)</pre>
162
168
### "x" is the x value of the secret point
163
169
### "o" is the outpoint being spent by the designated input
164
170
# Alice serializes her payment code in binary form.
0 commit comments