Smart contract security audit for Solidity and EVM
Deployed contracts cannot be patched quietly. We review the code, the economics and the deployment plan before it goes live, and re-review after fixes.
- Solidity
- EVM-compatible chains
- Upgradeable proxies
- Token, DeFi, NFT and governance contracts
What it is
A smart contract audit is a line-by-line security review of your contracts and how they interact, combining static analysis and fuzzing with manual reasoning about state, access control and incentives.
We work from a frozen commit, agree the scope and threat model up front, and deliver findings with concrete exploit scenarios so your team can judge each one. After you fix, we verify the fixes and update the report for publication.
What we check
- Access control and privilege: owner and role logic, initialisers, upgrade paths and what a compromised key could do.
- Reentrancy, call ordering and external call handling, including cross-function and cross-contract paths.
- Arithmetic and accounting: rounding, precision loss, overflow assumptions, fee and share calculations.
- Oracle, price and time dependencies, flash-loan and sandwich exposure, and MEV-sensitive logic.
- Token standard compliance and edge cases: approvals, hooks, rebasing or fee-on-transfer tokens, and non-standard behaviour.
- Upgradeability and storage layout, pause and emergency mechanisms, and the deployment and migration scripts.
- Gas and denial-of-service vectors: unbounded loops, griefing and block-stuffing assumptions.
What you receive
- An audit report: each finding with severity, affected code, exploit scenario, evidence and a recommended fix.
- A fix-verification round and a final report marked with each finding's status, suitable for publishing.
- A summary of the threat model, assumptions and what was out of scope, so readers know what the audit does and does not cover.
- A review call with your developers to discuss findings and trade-offs.
Typical timeline
1 to 4 weeks
Depends on lines of code and complexity. Fix verification is included within the engagement window.
Pricing
Quoted for your app
Discussed on a short call, then a fixed price in writing before anything starts. Request a quote
Who it's for
- Teams preparing a mainnet launch, a token sale or a protocol upgrade.
- Projects asked for an audit report by exchanges, launchpads, partners or their community.
- Teams integrating external protocols and wanting a second opinion on the interaction risks.
Next step
Tell us about the app. We discuss scope and price on a short call, then send a fixed quote in writing.
We only test applications you own or are explicitly authorized to test.
How quoting works
Tell us about the app
Platform, roughly how big it is and what you are worried about. Two minutes on the form.
Scoping call
A short call with an engineer to agree what is in scope, what is out, and when. Pricing is discussed here.
Written proposal
A fixed price, timeline, deliverables and rules of engagement in writing. You sign, we schedule.
Common questions
When should we get a smart contract audit?
Before mainnet deployment, a token sale or an upgrade, on a frozen commit. Deployed contracts can't be patched quietly, so the audit has to happen first.
Does an audit guarantee our contracts are safe?
No. An audit lowers risk within its scope and the commit reviewed. Later changes, key management, oracles and off-chain infrastructure can still fail, so the report states its scope and assumptions plainly.
Can we publish the audit report?
Yes. After the fix-verification round you get a final report marking each finding's status, written to be published.
Further reading
Often paired with
- AI Reverse-Engineering Exposure AuditWe point AI-assisted reverse engineering tools at your shipped app and report what they recover: logic, endpoints, secrets, data shapes and how much of the product could be rebuilt.
- Penetration Testing (VAPT)Vulnerability assessment and penetration testing of your web application and its APIs: authentication, authorization, injection, business logic and the OWASP Top 10, verified by hand.
Next step
Find out what your app gives away. Book a free exposure call.
Thirty minutes with an engineer, not a sales deck. Tell us what you ship; we tell you what we'd look at first and what an audit would involve.
We only test applications you own or are explicitly authorized to test.