Compare
Four documents, the same five questions.
No throughput league table and no yield. The cells are what this library is willing to say about the text.
| Question | Reusable Payment Codes for Hierarchical Deterministic Wallets |
|---|---|
| What the text proposes | BIP 47, Reusable Payment Codes for Hierarchical Deterministic Wallets. 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. |
| Who may write | Justus Ranvier |
| What is settled | 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. |
| Load-bearing assumption | A peer protocol is not a consensus rule. A peer can disconnect. A block is still valid or not on its own. |
| What this library says afterwards | Status in the source: Deployed. A reading of the public specification, not a copy of it and not a certification. |
| Rights | Official external source only |