Skip to content

Primary service

Formal verification for EVM and Solana.

We write the property, model the behavior that matters, and return a proof or counterexample.

EVM

  • Solidity specifications for the functions that move value.
  • State and protocol invariants.
  • Arithmetic and accounting properties.
  • Access-control and authorization properties.
  • SMT-style checks where the property can be encoded and the model is honest about loops and calls.

Solana

  • Rust and Anchor properties across instructions, not a single handler in isolation.
  • Account validation, ownership, and signer constraints.
  • Authorization invariants.
  • State-transition properties.
  • Arithmetic and accounting, including decimals and rounding.

What you receive

Scope
The code, the properties, and what was left outside the model.
Specifications
The properties as written, not as a slide.
Results
Which properties held, and under which assumptions.
Counterexamples
A trace when a property fails. Illustrative traces on this site are labeled as such.
Limits
What the model does not cover. A proof is not a claim that the protocol is safe.

What a proof is not.

Testing covers inputs. Static analysis flags patterns. Audits find attacks a specification may not name.

A proof applies only to the written property, stated assumptions, and model.

Discuss a verification project