Addresses
| Component | Type | Address |
|---|---|---|
| MissionRegistry | Solana program | HfewHudYaqgXSeurtbWCEDFFpAhVZxh5THmTLyrB7d1g |
| EvidenceRegistry | Solana program | GKFRrB1MpKb53QiQsLRTuDDjgB4KKM5YJKjoadnjtoPH |
| Fee treasury | Squads vault (3 of 4) | HEutRzinrChScDwqSW6ViTwFnvWBvHyAdrfSxNYqavPN |
| Payout vault | Squads vault (2 of 5) | 2MDj1EyzpNZvazgMiJJ2Kt2AmzE8RaBWa6Et1PbzAxV5 |
| Mission publisher | Backend signer | J1DqTrwRq8cviWXWq5GAfBqu1kpEn97TakLGRz9hyN3E |
| Evidence publisher | Backend signer | 54fFqAQm1gfuaxeGoH1DjhX7WJSaxxo3NX9KYJcvktem |
The two vaults are separate on purpose: entry fees never fund payouts. The Squads multisigs that govern them are BLkTqdp5yCYQ5SgTYrT71kspn53yzvvKrkwfcyp167uv (fee) and GBkgRZpkfENzMk2DHGDZF3Q9iVC6FtjqdF2qYBR7qGDn (payout).
The publisher keys only write mission records and evidence roots. Neither can move funds, and no key held by the backend can sign for a user.
What each release publishes
Program addresses and versions, verified source, the multisig addresses and their signers, and security review reports once available. Both registries were redeployed on 5 October 2026 under the company deployer; the vaults, the Squads and both publisher keys were unchanged.
Only use published addresses. Check the network and address, never just a token name.