TrustTrustTrust

• Reads public data from Solana and shows who controls a program, a token or a wallet, down to the keys.
• Keeps a public Register of pledges, each one a timestamped record that a wallet wrote about its own post-quantum keys.
• Lets a wallet write that record with one small transaction it signs itself.

• It does not hold, move or lock anyone’s funds, and it never sees an existing private key.
• It does not grade, rank or judge any project, program or key.
• It has no token and charges no fee.

Nothing. The scanner, control pages, reports and the table need no wallet at all.

Entering the Register is one transaction that your wallet signs: it moves 1 lamport from your wallet to the Register address and carries a short text memo. You also pay the network fee. Nothing else is in it.

Below is exactly what the transaction contains. A screenshot of each major wallet’s confirmation screen is added here before launch.

If a site using our name asks for one, it is a fake. Our only domain and our only Register address are listed here. Nothing else is us.

No. Solana’s core teams have a published plan that lets owners move to post-quantum keys using their existing wallet, by proving they know its seed. You do not need a record to keep your funds safe.

The Solana Foundation says quantum computing is still years away and that no change is required today.

In your browser, inside a Web Worker. Secret keys are encrypted with your passphrase before they leave the worker, and only into a file you download. They are never sent over the network, logged or stored by the site.

Or offline, with the command-line tool in the public repository. It uses the same code and needs no network. You paste only the two public-key hashes into the site.

The footer of every page shows the commit of the live build. To check it, clone the public repository at that commit, run npm ci and npm run build, and compare.

To make keys without trusting this website at all, run the offline tool: npm run keygen -- --wallet <your address>. To check a backup file: npm run keygen -- verify <file>.

Post-quantum keys come from @noble/post-quantum, version 0.7.1, pinned to that exact version.

Its authors state: “The library has not been independently audited yet.” and “at version 0.6.1, in Apr 2026, it was audited by ourselves (self-audited)”.

Its Falcon is Falcon Round 3, not the final FN-DSA standard, which NIST has not yet published. Encodings may differ from what Solana eventually ships.

Not yet. The record format, the key and certificate code, and the readiness checklist wording go to one independent reviewer before the format freezes and before the first mainnet record. Their name, the date and their notes will be published here, unedited.

Records are nearly free to make, so anyone with a script can inflate a raw count. We handle that in the open.

A wallet gets a number only if, at its first record, it held at least 0.1 SOL just before that transaction, and the oldest of up to 10,000 earlier transactions is at least 30 days older than the record. Both facts come from the chain, are decided once, and anyone can recompute them.

Numbers are given in order of first record and never change. The first 10,000 are Genesis. Every page shows numbered records and all records side by side.

The check raises the cost of faking numbers. It does not make it impossible.

Everything on control pages, reports and the protocol table is read from the chain at the time shown on the page. We list what we cannot decode instead of guessing. We do not grade anyone. When we are told about an error, we fix it.

There is no Claviger token. Anything that claims to be our token is not ours.

Write to the contact above. If something is wrong with the Register, the site can switch to read-only mode: scanning, control pages and reports keep working, and nothing new can be entered until it is fixed.