Questions · How to participate
Frequently asked questions
- Is the VCC live today?
- Not as a running network. What exists is published: this charter and threat model, an open-source verification core with a real cryptographic attestation layer, and this site. Multi-party verification and the public transparency view are still ahead on the roadmap.
- Does participating mean opening our books?
- No. Verification is privacy-preserving by construction. It proves that a claim holds (for example, that a training run stayed under a FLOP ceiling) without revealing weights, data, or what you are actually doing. The reciprocal reveal escrow keeps detailed evidence encrypted until an agreed trigger fires, and even then disclosure is simultaneous for everyone.
- Who controls the platform?
- No single lab or state, by design. Governance, hosting, and the authority to change rules are intended to be multi-stakeholder and capture-resistant: an adversarial board, a ratchet that makes tightening verification easy and weakening it hard, and diversified funding.
- Is this asking labs to unilaterally slow down?
- No. The platform is built to be useful even if a slowdown never triggers (provenance, export-control compliance, IP-preserving audit). Its job is to make a credible, mutual, verifiable pause possible, never to advocate that any single party stop alone.
- How can our organization get involved?
- Founding partners (labs, government bodies, academic cryptography groups), funders, and red-teamers are all relevant now. The adversarial mix of early participants is what determines whether anyone trusts the regime. Reach out below or open a discussion on GitHub.
- Where is the code, and how is it licensed?
- Everything is open. The verification logic is permissively licensed (Apache-2.0) for maximum auditability; the adversarial test tooling is released under coordinated disclosure, because an open cookbook for spoofing verification is exactly what a defector wants.
Still have a question?
Open a discussion on GitHub, or reach the team directly.