Skip to content

Services

Verification first. Audits beside it.

Formal verification checks written properties. Security review looks for adversarial failure modes.

Formal verification
WorkQuestionWhat it can return
Formal verificationDoes this property hold in the model?A proof or a counterexample, with assumptions.
TestingDid these inputs fail?Examples. Not a proof of the cases you skipped.
Static analysisDoes this pattern appear?Alerts. Useful, and not a theorem.
Manual auditWhat can an attacker do in this code?Findings with a reproduction. Absence is not proved.
  • Manual review of Solidity against the properties you cannot afford to violate. Storage layout and initializer re-entry are in scope when the system upgrades. Fuzzing only where a property earns it.

    Fits whenContracts that will hold value, or already do, including proxies and upgrade diffs.

    You leave withA report ordered by invariant, with proofs, and a fix-verification pass.

Start with the property, or with the code.

Discuss a verification project