FAQ

Four things about chain state, as of a slot: that LP tokens of a specific LP mint, in a specific amount, sit in a program-owned vault until a specific date; that the launch token’s mint and freeze authority read as renounced when the page looked; that no Token-2022 extension on the launch mint keeps a post-launch control surface; and that the lock is still active by chain time. Nothing else. Not the team, not the future, not whether the pool is the main one.

A scan is an observation; FairProof is a commitment. The founder’s LP is in a vault only the program can sign for, until a date the founder cannot move, and the record cannot be edited or re-locked with different terms. The fee is 0.25 SOL once — in the range of what a launch already spends on rent and fees (0.1–0.5 SOL).

Then the badge says Lock Expired, in amber, with a clock mark, and the page says LP is withdrawable. A badge pasted while the lock was active turns amber on its own, because the embed points at the live badge, not at a state. That honesty is why the green one means something.

Not from our surfaces. The badge is computed from a chain read; an edited verdict, a wrong contract version, or a badge flag that disagrees with the status all render Not Verified. The proof account must be owned by the program, have the right discriminator and exact size, and sit at the address derived from the mint. A screenshot can be faked; the link cannot — which is why every snippet wraps the badge in a link to the proof page, and why you should click it.

The verifier decodes every extension on the launch mint and refuses to badge a permanent delegate, a transfer hook, a live transfer-fee authority, a pausable mint, a close authority, a frozen-by-default state, a non-transferable mint, and anything it does not recognise. An immutable transfer fee below 100% is disclosed with its basis points, not refused. The full table is on the how-it-works page. Note the division of labour: the program checks the base authorities; the verifier refuses to badge extension control surfaces.

Only a program upgrade could touch vaults. The plan is for the upgrade authority, the admin and the fee treasury to be held in a Squads V4 2-of-3 multisig with a 24-hour timelock, revisited for immutability after 90 days. This is the single largest residual risk and we say so rather than soften it. The addresses are published in the docs once they are on-chain.

No external audit at launch. What exists: a self-review checklist with six findings, four fixed in code and two closed by policy, and a line-by-line pre-mainnet review. Both are published with the source at mainnet GO. Adversarially reviewed, open source at GO — that is the exact posture, and we do not describe it with a stronger word.

The proof is on-chain. The page is static with no backend, so it can be hosted anywhere, and the verifier is published with the source at mainnet GO, so anyone will be able to run it against the same accounts and get the same verdict.

No. It says four things about the chain state, as of a slot. Nothing else.

No. The minimum share is 90% of the LP supply; there is one lock per mint, no top-ups, no re-locks, no splitting. The rules are the same for everyone, which is what makes a proof comparable.

One price path, fewer accounts, fewer bugs. 0.25 SOL flat, collected inside the launch transaction; see pricing.

That no FairProof proof exists for that mint, or that the page could not complete a read. It is not a statement that the token is bad; it is the absence of a proof. Ask the founder whether they launched with FairProof and, if so, for the exact mint address — a proof is keyed to one mint and nothing else.

No. No cookies, no analytics script, no tag manager, no session replay, on these pages or on the proof page. Two parties see a request from your browser: the static host that serves the page, which receives the ordinary page request (the mint is in that URL) and nothing else, and the RPC endpoint the proof page reads the chain from, the way any RPC provider does — the page shows which one. No account read and no verdict passes through us, and we keep no logs of the mints people check.

Not yet. The program, verifier, proof page and badge are built and tested; mainnet deployment waits on the owner’s GO, and the program id and custody addresses appear on this site only when they are on-chain. Until then https://fairproof.app/<mint> answers Not Verified for every mint, honestly.

The self-serve launch app is built but not open yet: it cannot send a transaction until the mainnet GO. Launching opens to everyone at once, at GO.