Keep a record of who holds the keys.Keeparecordofwhoholdsthekeys.Keeparecordofwhoholdsthekeys.
Inspect your team’s Solana programs, mints and treasuries. Keep the evidence, return to a baseline, and see what changed in the control paths we can decode.
Keep labelled addresses and report history together. Projects stay in this browser; download a backup to move them to another device.
01 / Inspect
Start with your addresses
Up to 25 addresses. No wallet connection. Public chain reads may be cached for up to ten minutes; observation times travel with the report.
Your baselines
Saved in this browser
Names and saved snapshots stay on this device. Export JSON as a backup before clearing browser data. Up to 20 snapshots; no account or wallet connection needed.
Loading saved reports…
Current report
Your control record
Built 2026-10-13 18:59 UTC · mainnet-beta
Downloads contain this exact snapshot. A report URL opens a new read of its addresses and may show different results.
Before and after
Compare with a baseline
Keep a baseline, read the addresses again, then compare their supported controls.
1Addresses in this report
0Distinct keys found
1Addresses needing review
Supported control paths
Controlled by a single key
0
Controlled by a multisig
0
Controlled by another program
1
Immutable or without authority
0
Wallet keys entered
0
Not decoded
0
Coverage is limited to the account types and control paths we decode. An unresolved path is an open question.
Controls and evidence
mainnet-beta
Expand an address to see its control tree, unresolved questions and account observations. Reads may be cached and can span multiple confirmed slots. Source hashes cover the returned account data, including only the indicated slice where present.
Keys found in supported paths. For nested controls, inspect the complete tree above. Register records are optional pledges on mainnet-beta; they do not change signing rules.
No signer keys were resolved. The controls and coverage above explain this result.
Review checklist
Application-level post-quantum verification and a network-wide wallet migration are different capabilities. A Register record does not migrate a wallet. Use this inventory to plan future supported changes. Suggested order, by how much each key can change: upgrade authorities, mint authorities, multisig signers, treasuries.
1 item is controlled by another program. Its own rules decide who can act; check them by hand.
Keep this inventory current. Knowing every key that controls something is the first step of any key migration.
The checksum identifies the report contents. It is not a signature or independent proof of chain truth. Account reads cover supported control resolution, not a full transaction history, program-code audit, token valuation or proof of human signer independence.