Asset safety
Assets cannot be created, destroyed, transferred, or withdrawn outside intended rules.
How it works
From protocol risk to mathematical proof.
Salo proves defined properties across every execution represented by the model.
Process
A rigorous path to assurance.
-
01
Identify critical properties
We define the financial, security, and state-transition guarantees the protocol must preserve.
-
02
Model relevant behavior
We translate the implementation and its assumptions into a form suitable for exhaustive analysis.
-
03
Analyze modeled paths
Our verification engine determines whether each property can be violated.
-
04
Deliver actionable results
You receive proof outcomes, explicit assumptions, and concrete counterexamples for failures.
What we verify
Properties tied to real protocol risk.
Every engagement is built around the guarantees unique to the protocol, not a generic checklist.
Accounting correctness
Balances, collateral, fees, interest, and conservation-of-value invariants remain consistent.
Access control
Privileged operations are reachable only by authorized actors under intended conditions.
State transitions
Contracts cannot enter invalid states or perform prohibited transitions.
Upgrade safety
New implementations preserve established guarantees and do not introduce forbidden behavior.
Protocol-specific invariants
Your domain assumptions become precise, reviewable, machine-checked properties.
Engagements
Verification that fits your process.
Pre-deployment
Prove critical properties before launch or a major release.
Upgrade verification
Confirm that changes preserve existing guarantees.
Independent second opinion
Add mathematical analysis alongside an audit or internal review.
Continuous verification
Re-run essential properties as the protocol evolves.
Why verification
Testing finds examples.
Verification covers behavior.
Explore selected executions and discover concrete failures.
Prove defined properties across all executions represented by the model.
Start with one critical guarantee