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 | Silent Payments |
|---|---|
| What the text proposes | BIP 352, Silent Payments. We use the following functions and conventions: ''outpoint'' (36 bytes): the COutPoint of an input (32-byte txid, least significant byte first || 4-byte vout, least significant byte first) '''Why are outpoints little-endian?''' Despite using big endian throughout the rest of the BIP, outpoints are sorted and hashed matching their transaction serialization, which is little-endian. |
| Who may write | josibake |
| What is settled | We use the following functions and conventions: ''outpoint'' (36 bytes): the COutPoint of an input (32-byte txid, least significant byte first || 4-byte vout, least significant byte first) '''Why are outpoints little-endian?''' Despite using big endian throughout the rest of the BIP, outpoints are sorted and hashed matching their transaction serialization, which is little-endian. |
| Load-bearing assumption | A gas or opcode change is not a throughput benchmark. It is a relative price and a validity rule. |
| What this library says afterwards | Status in the source: Complete. A reading of the public specification, not a copy of it and not a certification. |
| Rights | Official external source only |