the unknowns board
Every build the audit bench cannot yet name. The bench recovers the bytecode of covenants no audited source explains, clusters them into structural families, and lists them here as open problems — each one waiting for the person who pins it first.
A place on this board is not an accusation and not a ranking of trust. It means one thing: kascov has not matched the build to audited source yet. Families sort by how many trades ride on them — that measures what is at stake if a build stays unaudited, never how trustworthy it is. Nothing here is priced or published as a verdict until a person reads the build and pins it.
mainnet
This board renders
/data/mainnet/verification.json
in your browser. With JavaScript off, read the file directly; the
audit_bench block is the same data.
testnet-10
This board renders
/data/testnet-10/verification.json
in your browser. With JavaScript off, read the file directly; the
audit_bench block is the same data.
How to win a stamp
- Pick a family. Win it the spotlight on the vote, or just call it in #what-to-audit-next.
- Submit the source you believe it is in the Discord,
naming a compiler from the pinned allowlist — today that is
silverc, the same compiler the builder uses, and the list grows only by a commit to the public repo. - kascov recompiles and compares bytes. Outside a family’s parameter slots the match must be byte for byte; a single-deployment family must match its exact program hash.
- A byte-match earns the auditor role and the permanent stamp. The family’s “first pinned by” line is written by a reviewed commit — the match is machine-verified, but the permanent name lands only after a human confirms the pin. No name ever lands here automatically.
A pinned-by slot on this board stays empty until someone earns it, and an earned one stays forever. That is deliberate: an empty slot is an open problem, and an open problem is an invitation.