Contract review & security testing
Static analysis, invariant fuzzing and line-by-line manual review of your contracts. Every finding comes with a failing test you can run, a severity and a suggested fix.
Deliverables
Static analysis, invariant fuzzing and manual review. Every finding comes with a failing test.
Scoped review plan
What is in scope, what is not, and which properties we will try to break.
Findings with proof
Each issue gets a severity, a proof-of-concept test and a suggested fix.
Invariant suite you keep
The fuzzing harness stays in your repo and keeps running after we leave.
Fix verification
We re-run everything against your fixes and confirm each finding is closed.
Written summary
A plain report your team, investors or a later auditor can read.
For a launch that will hold significant value, we still recommend an independent audit on top. Our review makes that audit shorter and cheaper, not unnecessary.
How we work on this
Each step produces something you can read or run, so progress is never a matter of trust.
- 1
Scope
Read the code, docs and tests. Agree on scope, the properties to test and the timeline.
- 2
Automated pass
Static analysis to clear the obvious classes of bug quickly, triaged by hand.
- 3
Manual review
Line by line, with the business logic and economics in mind.
- 4
Fuzz campaigns
Invariant fuzzing across long random call sequences to find the paths nobody wrote down.
- 5
Report & verify
Findings with tests and fixes, then a verification pass on your changes.
What we test hardest
- Reentrancy and call ordering
- Access control and privileged roles
- Rounding and share-price inflation
- Oracle manipulation and stale prices
- Proxy storage-layout collisions
- Flash-loan driven economic paths
Tools we use
More in Blockchain
Common questions
It is a security review with tests. We do not issue certification badges, and we will tell you when an independent audit is warranted.
Yes. That is most of this work. We start from your docs and tests and ask questions early.
You still keep the invariant suite and a written account of what was tested and how.
Have a project in mind?
Tell us what you are building and what must not go wrong. An engineer who would work on it will reply.