# Vaultfire Solana V3 Supported-Candidate Source Identities

> **Evidence scope:** source-only. These values are pinned build identities, not
> deployed addresses, executable-account observations, upgrade-authority
> evidence, or authorization to deploy.

The canonical record for all fifteen source dispositions and identities is
[`v3-program-dispositions.json`](./v3-program-dispositions.json). This partner
view intentionally repeats only the six supported candidates:

| Program | Pinned source identity |
|---|---|
| `ai_accountability_bonds` | `7UP91JrXSfLSPkGE6SKLREX6Vm7MmuDbk1m4cUuVr3M7` |
| `ai_partnership_bonds` | `H95dFPhN4AZZbQPHYU34UfCNiiiw7y8ik4ZFSy9sfxZb` |
| `identity_registry` | `E5e8JogsRqjXAEa3RKxFFVShRfD8TMjoAporRMvMLuYE` |
| `multisig_governance` | `78wgFpYaAnFXJGPLkUCc2xXo9FjwXvkiTCi39EKzovx6` |
| `privacy_guarantees` | `9jwLscZsufQERhh4wnc8p5hNYTw6Sz5CrkC3Kejjb1vK` |
| `vaultfire_adapter` | `6DFwZ6RGdeAS1ZxbmfPvnh61S67V2764dbKe7HzqV45C` |

The other nine identities are canonical classification tombstones only. They
must not appear in generated IDLs, SBF artifacts, deployment maps, rehearsal
arguments, or partner deployment instructions.

A future executable-evidence run must start from a clean committed candidate.
The release gate checks these IDs against `declare_id!`, validates each as a
unique 32-byte base58 public key, binds each generated IDL and ELF to the pinned
identity, and records source and manifest digests. The immutable local preload
still does not establish mainnet deployment.
