Documentation

Launch certificates

On reaching Closed, the campaign transcript folds into one verifiable object: token T at address A launched under manifest M, audited by X with finding counts C, satisfying property bits P at suite version v, verified at tier T, distributed per the on-chain ledger. Any third-party protocol — a DEX listing gate, a lending market, an index — can check it with zero trust in Drydock.

Contents

The creation journal; the funding-record digest; the attested trailer and which path bound it; the re-proof journal; the deployment record; the verification tier; and a mechanical funding-concentration digest (top-1/5/10 contributor shares, unique-contributor count) so consumers can discount self-funded raises without anyone exercising judgment inside the protocol.

What it deliberately never claims

Nothing about project quality, team intent, future work, or token value. A campaign can be manifest-true, cleanly audited, honestly distributed, and worthless. The certificate attests process, never quality — and every client rendering it is required to say so.

Consuming certificates

v1 certificates are a concatenation of independently verifiable artifacts (journals, the signed trailer, chain state), checkable in-browser via the WASM verifier. Recursive folding into a single proof is future work (paper Section 9). Integrating a listing gate or a safety scanner:contact@drydockprotocol.org.