Nexus Market Dossiers

What a dossier covers

One mechanism, in depth, from first principles. How a v3 onion address is constructed. How a two of three multisig arrangement holds an order. How the fingerprint captcha defeats a cloned front end. How PGP signatures prove an announcement came from the key it claims. Each is written so somebody who has never met the subject can follow it without reading the others first.

Why mechanisms rather than advice

Advice ages badly and is easy to follow without understanding, which means it is also easy to abandon at the first inconvenience. A mechanism explained properly produces the advice as a consequence. Somebody who understands why an address cannot be forged does not need to be told to check it.

The level they are pitched at

Technical but not academic. No cryptographic proofs, no protocol specifications quoted at length. Enough detail that the guarantees are clear and the limits are honest, and no more than that. Where a mechanism has a boundary, the dossier says where it stops working, because a protection described without its limits is worse than none.

What they are not

Not implementation guides. Nothing here describes how to run a service, only how the pieces behave from the outside, which is the position a visitor is actually in.