Property specification
Translate intended protocol behavior into explicit, reviewable security properties before verification begins.
Formal Verification for Smart Contracts and Protocol Security
Define security properties for critical protocol behavior and evaluate whether the scoped implementation satisfies those specifications.
How it works
A property is only as complete as its specification
Formal verification can evaluate precisely defined behavior. It remains bounded by the selected properties, the modeled environment, and the assumptions connecting the model to the deployed system.
Engagement coverage
Built around the questions that matter
The final work is defined against the exact code, system model, and security objective supplied during scoping.
SpecificationsInvariantsState transitionsSolidityProtocol properties
State-transition modeling
Model the actions and state changes that can affect the properties in the agreed scope.
Protocol invariants
Evaluate properties such as conservation, authorization, solvency, or state integrity when relevant to the system.
Assumption review
Document environmental, integration, and modeling assumptions that bound what a result means.
Counterexample analysis
Investigate failed properties or counterexamples to determine whether they expose an implementation issue, model issue, or missing assumption.
Verification artifacts
Deliver the agreed specifications and outcome record without implying guarantees beyond the reviewed model and scope.
FAQ
Formal Verification FAQ
What is formally verified?
A formal-verification engagement evaluates explicitly defined properties against a scoped model of the implementation. It does not automatically prove every possible security property.
Which properties can be considered?
Depending on the protocol, the scope may include authorization, conservation, solvency, state integrity, or other precisely defined invariants.
Does verification replace manual review?
No. Specifications can omit an important requirement, and integration or economic risks can exist outside a model. Manual review and formal verification answer different questions.
What does a failed property mean?
It requires analysis. A counterexample may reveal an implementation defect, an incorrect model, an incomplete assumption, or a property that needs refinement.
Start with the scope
Let’s secure what you’re building
Share your scope, target date, and architecture. The security team will review the details and respond with the next steps.