# Vaultfire V3 Public Source Status

Vaultfire V3 is a publicly reviewable source candidate for Base and Solana. It
has not been deployed or activated, and it is not represented as
production-ready or partner-ready. The candidate identity is the commit and
tree referenced by release tag `v3-source-2026-08-27`, not the mutable GitLawb
`main` branch. The verification command below rejects any other commit.

## Exact public candidate

| Item | Value |
| --- | --- |
| GitLawb branch | `main` |
| Release tag | `v3-source-2026-08-27` |
| Candidate identity | Commit and tree referenced by the release tag |
| Public audit attestation ref | `attestations/v3-source-2026-08-27` |
| Previous public baseline | Commit `6cb01addc5473d8514d1b19e98942d203edc03d6` |
| Previous AI-assisted closure | `C0 / H0 / M0 / L0` at that baseline |
| V2 live/default | Yes |
| V3 deployed or activated | No |

The configured GitLawb remote uses a DID-key repository URL. Repository commits
and the annotated release tag use a generic automation identity and are
unsigned; Git metadata alone does not establish signer authentication. The
public attestation branch binds an AI-assisted audit report and checksum to the
tagged commit and tree. No independent human auditor, organization, or
cryptographic auditor signature is claimed.

Clone and verify the exact source:

```bash
git clone --branch v3-source-2026-08-27 --recurse-submodules gitlawb://did:key:z6MkryiNsYdFEMHv95wxzSQ1vtFXPyVQQrxXdPw3tE5HpfxV/vaultfire
cd vaultfire
./scripts/verify-v3-source.sh
```

For an existing clone, fetch and detach the reviewed release explicitly:

```bash
git fetch origin tag v3-source-2026-08-27
git switch --detach v3-source-2026-08-27
git submodule update --init --recursive
./scripts/verify-v3-source.sh
```

## What V3 is designed to provide

- **Bounded accountability:** Signed terms cap liabilities and slashing instead
  of allowing open-ended economic exposure.
- **Mutual consent:** Typed EIP-712 authorization and ERC-1271 compatibility
  bind participation to explicit approvals.
- **Objective enforcement:** Canonical source records, exact address and
  runtime-codehash checks, and repeated revalidation constrain enforcement.
- **Safe settlement:** Pull-payment credits, conservation checks, pause-safe
  exits, and deterministic timeout handling protect principal.
- **Restrictive governance:** Selector, target, value, argument, runtime, and
  policy-digest constraints reduce arbitrary governance execution.
- **Protected decisions:** Behavioral, biometric, profiling, surveillance,
  flourishing, reputation, loyalty, and cross-chain inputs cannot control a
  supported protected decision.
- **Additive migration:** V2 remains the live default. V3 modules are isolated,
  individually gated, and not automatically activated by this source release.

## Base candidate

The Base source candidate is frozen to the following source identities:

| Component | SHA-256 |
| --- | --- |
| `AccountabilityBondV3Safe.sol` | `fffa87569e1afbc74301eccb099815a27b2954586e13f05b8c8e766a096ccffa` |
| `BondStateV3.sol` | `d22611af5957320446ed95784497d0e0280860786eba8e34b76e2e960fc2d14b` |

AI-assisted exact-hash Base and bond reviews covered lifecycle
boundaries, pause behavior, factory pinning, governance restrictions, identity
authentication, mandate hardening, conservation, rounding, replay resistance,
and pull-payment solvency.

The runtime-size gate sets a 22,528-byte project ceiling, preserving a
2,048-byte policy margin below EIP-170. During AI-assisted candidate
preparation, the complete Base source graph was compiled with Foundry Forge
1.7.1, Solidity 0.8.24, the pinned gitlink dependencies, and the checked-in
optimizer/via-IR configuration. That run reported 31 passing deployable
runtimes; the largest,
`AccountabilityBondV3Safe`, measured 22,460 bytes, leaving 68 bytes below the
project ceiling and 2,116 bytes below EIP-170. A separate isolated-shard run
reported 246 of 246 non-fork Solidity tests passing.

Those heavyweight run logs and compiler artifacts are deliberately not retained
in this source-only tree, and `scripts/verify-v3-source.sh` does not reproduce
them. Reviewers should treat the numbers as reported preparation results and
rerun the commands in [`v3-src/README.md`](./v3-src/README.md) before relying on
them. They are not deployed-bytecode, fork/RPC, ownership, role, or live-chain
evidence. Any Base source, dependency, compiler, or settings change requires a
complete rebuild and remeasurement.

## Solana candidate

The supported Solana surface contains six programs. Four additional programs
require redesign and five are retired; the release gate excludes both groups.

| Solana check | Evidence and status |
| --- | --- |
| Source-policy regressions | 68/68 passed |
| Native Rust | Preparation run reported locked/offline metadata, formatting, 9 unit tests plus doc tests, and Clippy `-D warnings` passing |
| SBF reproducibility | Preparation run reported six programs built twice with all six artifact pairs byte-identical |
| Generated IDLs | Preparation run reported six source-derived IDLs verified for instructions, types, accounts, PDA seeds, relationships, layouts, enums, and errors |
| Local validator | Preparation run reported six immutable programs loaded and verified on loopback with disabled upgrade authority |
| External RPC or mainnet | Not used; no deployment evidence |

The pinned validation environment used Anchor 0.32.1, Agave/Solana 2.3.0, and
Rust 1.89.0. Every singleton initializer and the package deployment command
remain intentionally fail-closed. No production program accounts, deployment
transactions, program keypairs, upgrade authority, mainnet verification, or
partner acceptance is claimed.

The generated SBF, IDL, and validator outputs are deliberately excluded from
this source-only tree. Accordingly, the canonical Solana records keep
`executableEvidenceAvailable=false`; the quick verifier reproduces only the 68
source-policy tests. Reviewers can independently reproduce the heavier checks
with the pinned commands in
[`repos/vaultfire-solana/README.md`](./repos/vaultfire-solana/README.md).

## SDK, specification, operations, and partner evidence

| Surface | Exact result |
| --- | --- |
| V2 preservation | 36 ABIs and 134 runtime identities verified |
| Open specification | 64/64 normal, 64/64 optimized, external exact-commit conformance 29/29 |
| Migration ledger | 2,147 items; 30/30 normal and 30/30 optimized |
| Operations gates | 27/27 normal and 27/27 optimized; release remains blocked |
| Partner package | 309/309 normal and 309/309 optimized; readiness remains blocked |
| x402/PR7 | 129/129 full suite; direct suites 86/86, 33/33, and 18/18 |
| TypeScript SDK | Build and typecheck passed; 68/68 tests; two-build determinism across 55 files |
| Solana source-policy tests | 68/68 |

The V2 migration and remediation surfaces are directly reviewable in the
[baseline compatibility matrix](./baseline/V2_COMPATIBILITY_MATRIX.md) and the
[V2-to-V3 compatibility matrix](./pr7/compat/V2_V3_COMPATIBILITY_MATRIX.md).

The final SDK ABI closure is:

| Deployment | Functions | ABI identity |
| --- | ---: | --- |
| Accountability | 36 | `0x0c18d05c868716fad4bfc1fcfad2da51c83f247de06a7e3871dcece768a9526f` |
| Partnership | 55 | `0x954aeee609e92a621e726dcae77be193085651626941d582ca2f7f3b7c073d8c` |
| Governance | 45 | `0xcf81d69fed252f21bfd7661ff53868aa81b9ce1a4a1c89edbec9eaabffa7ad0a` |
| Mandate Registry | 24 | `0xe31e9d196bf5a37c328313f688b0d6eff881847e6c46437c1fc617faff8e80e3` |

## Closure audit scope and limits

The previous AI-assisted closure re-audit checked its exact commit and tree, repository
hygiene, allowlist and purge decisions, protected V2 preservation, Base
snapshot, migration ledger, operations package, open specification,
exact-commit conformance, partner package, x402/PR7 surfaces, SDK build and test
results, deterministic generated outputs, and bounded Solana source tests.

Subsequent candidate preparation ran native Base compilation and tests plus
native Rust, SBF, generated-IDL, reproducibility, and local-validator checks for
Solana. Their generated outputs are not bundled in this source-only tree. A new
exact-commit read-only review is part of the source-publication process.
Fork/RPC, wallet, signing, mainnet, deployed-address, ownership, and production
operations evidence remain outside this source release.

## Current release boundary

| Claim | Current state |
| --- | --- |
| Public source | Yes |
| Exact source separately AI-assisted re-audited | Yes |
| V2 remains live/default | Yes |
| V3 deployed | No |
| V3 activated | No |
| Base partner pilot authorized | No |
| Solana partner pilot authorized | No |
| Live x402 publication evidence complete | No |
| Partner organizational and human evidence complete | No |

The following release flags remain false:

- `sourceComplete`
- `evidenceComplete`
- `deploymentAuthorized`
- `deployed`
- `activated`
- `partnerReady`

Remaining gates include independent human security review, live-chain address
and runtime verification, x402 owner evidence, governance role
assignment, responder coverage, operational drills, independent human
authorization, legal and privacy review, insurance, partner acceptance,
commercial terms, support/SLA selection, incident-plan acceptance, and
change-RACI acceptance.

## Bottom line

Vaultfire V3 is ready for public technical review and preliminary partner
diligence. It is not yet ready for a production partner deployment, and an
independent human security audit remains open. A partner can evaluate the
architecture, exact source, tests, and AI-assisted review evidence now;
deployment requires the remaining technical, operational, legal, and human
gates to close without changing the reviewed bytes.
