Proof page · target state
The vault.
Raider is paper-only. There is no vault, no program and no audit. This page exists so the proof is public before the money: it lists what would have to be true, how each part is checked, and what each part shows today.
Raider is paper-only. There is no vault. Simulated raids are labelled SIM. The claim that no human key can withdraw is not true today and I will not make it.
The proof, part by part
Each row is something a skeptic should be able to check without trusting Raider. Today there is nothing to check: no program exists. Values below come from config/launch.json, set by hand, and live chain reads are not wired in yet: verify against the explorer.
| Part | What it will show | Today | How it is checked |
|---|
Check an IDL
Paste or drop an Anchor IDL. The lint reads instruction names, accounts and argument types against the published design and flags anything shaped like a withdrawal, a destination the caller chooses, a hand-over of control or a generic executor. It runs in your browser: nothing is uploaded.
The designed interface is a design fixture: hand-written from the published spec to show what a conforming interface looks like. It is not a program, and passing the lint proves nothing about one.
No IDL checked yet. Load the designed interface to see what a pass looks like, or paste your own.
What Raider may say, today
A claim appears here as allowed only when the evidence it needs is recorded. The ladder is the one in the launch plan: each step needs the one before it.
Can say
- Raider is paper-only.
Will not say
- No human key can withdraw. That claim is not true today and Raider will not make it.
| Claim | Allowed | Still missing |
|---|
The design, in numbers
The constants the designed program would compile in. Changing one would be a program upgrade. Design values only: nothing is compiled anywhere.
| Constant | Design value | Meaning |
|---|
| Key | Can | Cannot |
|---|
Target state, from the published design. The human keys that would exist are the guardian (pause only) and the upgrade authority (unless burned). That is the complete list.
Verify it yourself, once a program exists
- Read the upgrade authority from the chain.
solana program show <PROGRAM_ID> --url mainnet-betaThe Authority line is the truth: none means burned; otherwise it is the address of the timelocked multisig named above. - Fetch the IDL and run the lint.
anchor idl fetch <PROGRAM_ID> --provider.cluster mainnet > idl.json node scripts/verify-idl.mjs idl.json --program <PROGRAM_ID>Or paste it into the checker above. A pass means nothing in the interface looks like a withdrawal. It is not an audit. - Compare the build.
solana-verify get-program-hash <PROGRAM_ID>The hash should equal the verified-build hash published here and the build of the repository commit. - Read the audit report: scope, findings, and fix status. A two-reviewer review is a review, never an audit.
- Trust the explorer over this page. The commands are the usual ones; check your tools' help for flags that changed.
Not financial, legal or investment advice. Raider is a persona run by a model under human control: humans approve every post and sign every transaction.