Security is evidence, not a feature label

Current operating boundary

V3 is source and local evaluation software. Public-chain deployment, activation, production payments and partner funds remain disabled. Historical V2 addresses and risks are separate; a source-only V3 repair cannot change immutable V2 runtime.

No blanket independent audit opinion or production-safety certification is established by this page. Past AI-assisted reviews are historical evidence only, not independent human certification of a newer source tree.

Historical external review

Vaultfire's V2 Base contracts received an external AI-assisted first-pass review through OneDollarAudit using LeftClaw Services agent #21548. That review was not an independent human audit and did not review the frozen V3 source candidate. It remains historical evidence, not certification of the current repair candidate or authorization for funds.

Keep the evidence classes separate

• A code hash identifies bytes; it does not show that deployed runtime matches reviewed source.
• Host tests, simulation, fresh native/local execution, real cryptographic proofs and deployed-chain execution are different lanes. Passing one does not finish the others.
• Explorer source verification, code presence and a registered address are not audit or safety assurances.
• A quorum authenticates multiple reports, not the truth of those reports. Correlated or malicious attestors remain a risk.

Privacy and cryptography have specific requirements

A hash or commitment is not encryption. A digest, signature or self-generated witness is not automatically a zero-knowledge proof. The presence of ML-DSA, ZK or FHE code does not make the entire system quantum-proof, private or production-ready. Read the exact module's supported verification path and blockers before relying on it.

This website does not establish live XMTP delivery. Local discussion and room drafts are stored unencrypted in the browser, not delivered encrypted messages. Do not enter secrets. Legacy browser state can remain on a device until explicitly cleared; disconnecting is not a promise of deletion.

Funds and signatures still carry risk

The V3 reward formula uses a prefunded sponsor budget and does not debit protected principal. That design boundary is not an assurance against bugs, compromised keys, wrong addresses, malicious signers or incorrect deployment. Separate remedy reserves require their own exact authorization.

Blockchain transactions may be irreversible. Do not send assets you cannot afford to lose, assume insurance, rely on automatic recovery or treat a historical contract's rules as current V3 policy. No funded wallet is needed for the local evaluation.

Check source and website identities separately

Start with the current protocol source selector, authenticate its external sidecar and extracted files, and compare the validation scope. The website publication has its own identity record; it is not automatically the protocol source commit. Unavailable current evidence is a blocker, not permission to silently use history.

If something looks wrong

Stop before signing or sending funds. Keep the exact version, source identity, network, request or transaction identifier and the observed failure. Do not share a seed phrase, private key or wallet file. Use the local recovery checklist and documented status/receipt path before retrying. This site cannot promise to reverse a transaction or recover lost funds.