Compound Merkle Path Format
Sending proofs for several transactions separately repeats the same hashes over and over. This defines a compact form that carries proofs for many transactions at once with the shared parts included only once.
Damian Orzepowski
Beered by 5 people
5 standards · 3 topics
61 62 +1Background Evaluation Extended Format (BEEF) Transactions
A recipient cannot check a payment without the transactions it came from and the proofs tying them to the chain, and fetching those separately is slow and reveals what you are looking at. This packages everything needed to verify a payment into one compact bundle.
74 BSV Unified Merkle Path (BUMP) Format
Different proof formats each solved part of the problem, leaving processors and clients converting between them. This defines one format that is cheap for a transaction processor to produce and convenient for a client to check.
Darren Kellenschwiler, Tone Engel +22023
84 Linked Key Derivation Scheme
Deriving a shared key normally needs one party's private key, which rules out cases where neither side can act. This extends the derivation so a key can be worked out from both parties' public keys alone.
2024
85 Proven Identity Key Exchange (PIKE)
Two people who want to transact need each other's public key, and sending it over a channel someone could tamper with is a real risk. This uses a short code shared out of band to confirm the key really came from the right person.