Trust is not declared — it is demonstrated. MAIEV is VEIL's evidence and validation archive. It tracks local and staged verification artifacts, remediation notes, and launch-gate evidence. External third-party audits are listed only when publicly published.
Current status: 0 external third-party audits published. Operator packet GO FOR PRODUCTION (13/13 gates local PASS) — not public launch.
VeilVM v1 has 19 native actions (IDs 0–18): markets, commit/reveal/clear, dispute, resolution, fee routing, VAI mint/burn, AMM. Companion EVM is wrap/bridge/intents only — not a second protocol. Neither chain is live on Fuji or mainnet.
Groth16 (gnark, BN254) shielded-ledger proof verification for batch settlement, exercised against a running local testnet: proof-gated acceptance, malformed-proof rejection, and settlement-deadline enforcement.
Fee routing, liquidity incentives, and VAI collateral/redemption parameters. Design and runtime paths are implemented; production parameter freeze and full stress-test evidence are still pending.
Node architecture, backup-prover takeover, and disaster-recovery drills, exercised on a local protocol-45 testnet. Public Fuji testnet deployment has not happened yet — that's the next campaign.
No external audit firm has reviewed VEIL. What exists instead is a reproducible local launch-gate suite run against a real protocol-45 testnet. Bundle 20260220-202857-launch-gate-evidence (generated 2026-02-20T20:48:20.428Z) is the latest full run — every required gate passed.
shielded-smokeaccepted=1, rejected=0, missed=0
221.6sbackup-takeoverprimary prover rejected under backup-authority gate; backup recovered and cleared 1/1
451.3ssynthetic-negativeexpected fail-close proof rejection observed (non-zero exit)
5.5smalformed-proofexpected malformed-proof rejection observed (non-zero exit)
232.5stimeout-drillexpected proof-deadline-missed rejection observed (non-zero exit)
224.6sEvery local launch-gate run publishes its bundle under public/maiev/*-launch-gate-evidence/. These are real, unaltered files from this repository — open them directly.
Every review begins with a precise scope document defining contracts, circuits, and systems under validation. Scope is published before validation commencement for community review.
External audit firms are engaged only after launch-readiness milestones require them. This archive currently prioritizes internal and staged validation evidence.
Validation proceeds through automated analysis, manual review, and reproducible evidence checks. Each phase records findings and remediation status.
Findings rated Medium or above require remediation and follow-up validation. Third-party re-audit is recorded only when an external report is published.
All validation artifacts—source snapshots, reports, and remediation notes—are cryptographically hashed and stored in MAIEV's evidence archive.
Post-deployment planning includes invariant testing, bug bounty programs, and scheduled re-validation for critical components.
Frontend evidence archive aligned to launch-gate workflow.
Local PASS/FAIL artifacts from launch-gate runner indexed into MAIEV surfaces.
Mempool hardening and threshold rollout records added to archive.
Adversarial and smoke evidence pointers synced to latest local run IDs.
Independent third-party reports will be listed here only after publication.
MAIEV tracks staged validation evidence and launch-gate artifacts. Review documentation and evidence bundles directly before relying on any readiness claim.