$KEEPER — the audit

what gets checked, and why you shouldn’t take my word for it.

The audit has not been run yet

This page fills in with live chain data the first time the audit runs against the contract. Until then it is empty on purpose — an audit page showing results before an audit happened would be worth nothing.

What it checks

Mint authority. Whether anyone can still print more supply. It should be revoked.

Freeze authority. Whether anyone can freeze a holder’s wallet. It should be revoked.

Liquidity. Whether the LP is burned.

The dev holding, against what was promised. Not a generic check — it reads the specific promises published before launch and compares them to the chain.

The lock. Current holding measured against the earliest recorded run, which is the only way a snapshot tool can answer “did they sell during the window they promised not to.”

Why the record can’t be quietly edited

Every run is appended to a log where each entry carries the SHA-256 hash of the entry before it. Editing or deleting any earlier record breaks every hash that follows, and the verifier reports exactly where it broke.

That proves the log hasn’t been rewritten since it was written. It does not prove when an entry was written — for that, a chain hash gets posted publicly, and everything before it is anchored from that moment.

Read the code instead of trusting the page

The tool that produces this page is public. It has no Solana SDK dependency — the mint layout is parsed directly and base58 is implemented in the repo — so there is no third-party library you have to trust before you trust the output.