Team readiness report

Reading the chain…

Inspect · Preserve · Compare

Keep a record of who holds the keys.

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.

Build a report ↓Explore an example →

Your projects

A place for every review.

Restore project

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

Import JSON

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:01 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

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: 0
Immutable or without authority: 0
Wallet keys entered: 0
Not decoded: 1

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.

Token mintPFireKhT…F8HNbrAdditional token controls not decodedNeeds review

PFireKhT5WG7axMSLBmMRpvYH7cgHx9CRWHU8F8HNbr

Observed 2026-10-13 18:01 UTC to 2026-10-13 18:01 UTC.

Transfer fee config may carry additional controls that are not decoded.
Review this token extension’s authority and operating rules.
Metadata pointer may carry additional controls that are not decoded.
Review this token extension’s authority and operating rules.
Token metadata may carry additional controls that are not decoded.
Review this token extension’s authority and operating rules.

TokenPFireK…HNbr
Mint authority
- NoneNone
Freeze authority
- NoneNone

PFireK…HNbr

Slot 456533083 · confirmed
2026-10-13T18:01:14.551Z

Source details

Account exists: Yes
Owner: TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb
Data SHA-256: 48c2b568552f80a663662302b8787ecb7a8768a2f5f89eb2caab8ed999e7324d
Data read: Full account data

PFireK…HNbr

Slot 456533057 · confirmed
2026-10-13T18:01:08.510Z

Source details

Account exists: Yes
Owner: TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb
Data SHA-256: 48c2b568552f80a663662302b8787ecb7a8768a2f5f89eb2caab8ed999e7324d
Data read: Full account data

Key inventory

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.
We could not decode 1 address. Check it by hand.
Keep this inventory current. Knowing every key that controls something is the first step of any key migration.

Snapshot identity and coverage

Built at: 2026-10-13T18:01:14.556Z
Decoder: claviger-controls/1
Schema: 1
SHA-256: 7dadaef036dd9fd01be0c603fdaabb4bcee891716a4bc2810e429fedfc0bf334

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.