ShipGate · Contract Prover
A proof you can sign, anchor, and re-verify.
Most audits hand you a PDF. This hands you math. Prove a single contract, or point us at a whole repo (paste or git URL) — we discover every contract, prove all its safety properties with Foundry + Halmos symbolic execution and cvc5, then issue signed certificates bound to the deployed bytecode, independently re-verifiable by anyone.
Symbolic proof (Halmos) — not a Slither-style static scan. Web3 app builds on the demo include static gates separately. One proof bundle = one certificate.
How the guarantee holds
- · Non-vacuity enforced— a mutant must be refuted, so proofs can't be vacuously true.
- · Degraded never ships green — if the solver times out or tooling is missing, the verdict degrades; it is never reported as proven, and you are not charged.
- · Bytecode-bound— the certificate is keccak-anchored to the contract's code and re-verifiable at /certificate.
Continuous assurance for audit teams is the Audit plan ($4,900/seat, 250 proofs/mo) — one proof bundle per certificate; Pro and Business tiers include smaller bundles if you are piloting volume.
Where this fits:continuous, machine-checked proof that sits between your Foundry tests and a full manual audit — re-run on every commit so a regression can't slip through. It proves the invariants you declare; it does not replace human review of your economic and governance design.
Web app, not a contract? Point the gate at a Next.js + Prisma repo — lift its ISL spec and prove tenant isolation + authorization-completeness over your own code, or run it in CI with wholestack prove ..