Team readiness report
Reading the chain…
Reading the chain…
Inspect · Preserve · Compare
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.
Your projects
Keep labelled addresses and report history together. Projects stay in this browser; download a backup to move them to another device.
01 / Inspect
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
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
Built 2026-10-13 16:20 UTC · mainnet-beta
Before and after
Keep a baseline, read the addresses again, then compare their supported controls.
Coverage is limited to the account types and control paths we decode. An unresolved path is an open question.
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.
Observed 2026-10-13 16:20 UTC to 2026-10-13 16:20 UTC.
Upgrade authority
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.
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.