A Solidity audit is a security review of EVM contract source at a frozen commit, targeting the bug classes the Solidity compiler does not catch — reentrancy, access-control gaps, accounting and rounding errors, proxy storage collisions, and unsafe assumptions about external tokens and oracles.
Solidity gives you very little for free. The compiler will stop an integer overflow since 0.8, and it will stop you calling a function that does not exist, but it will not tell you that your withdraw function updates state after the external call, that your initialiser can be run twice, that your vault mis-rounds in the depositor's favour, or that your upgrade shifts a storage slot under live balances. Every one of those is a normal Solidity program that compiles cleanly.
We review Solidity from the invariants down. We write out what must always hold — solvency, share-price monotonicity, supply conservation, who may call what — then attack each one with a combination of line-by-line reading and Foundry invariant campaigns against forked mainnet state. Static analysers (Slither, Aderyn) run to widen coverage on the mechanical classes; they never set severity. Exploitable findings ship with a proof-of-concept test you can run yourself.
We fix a commit hash, agree the in-scope contracts and read your architecture docs, then build a threat model: who the actors are, what the trust boundaries are, and which invariants must never break. Nothing is reviewed against assumptions we have not written down.
Line-by-line review by at least two auditors working independently, focused on authorisation, accounting, upgrade paths, external integrations and the gap between what the code does and what the documentation claims it does. Most critical findings come from this phase, not from tooling.
Static analysers appropriate to the language, plus property-based fuzzing and invariant testing to push the system into states no unit test covers. Tooling is used to widen coverage, never to replace the manual pass.
Candidate findings are proven on a forked network with a working proof of concept. We report what an attacker can actually do and what it costs them, not a theoretical severity label.
Every finding gets a severity rating, reproduction steps, the affected code, the impact in concrete terms and a specific remediation. You get a draft for discussion before anything is finalised.
We re-test every remediation against the original proof of concept and check that the fix has not opened a new path. The final report is yours to publish.
Everything that depends on intent. A static analyser can flag a missing return check; it cannot know that your liquidation is profitable to grief, that your oracle window is short enough to move, or that your fee accrual quietly rounds against depositors. Those come from reading the code against your invariants.
Anything from 0.6 upward in regular practice, and older code when the engagement calls for it. Legacy code changes the priorities — unchecked arithmetic and pre-0.8 patterns become first-class findings.
Yes. A test suite that passes tells you what the team thought about. The gaps in it are frequently where the finding is, and we hand back invariant tests you can keep running in CI.
Yes. Assembly-heavy code takes longer per line because the type system is no longer helping, and we scope it accordingly rather than pretending it reads at the same rate.
A repository or contract address, a commit hash to freeze the scope, whatever architecture or spec documentation exists, and a point of contact who can answer design questions. If documentation is thin we will write our understanding of the system back to you and ask you to confirm it — that step alone catches design-level bugs.
A single token contract is 24–48 hours. A typical dApp or mid-sized protocol runs one to two weeks. Large DeFi systems, L2s, bridges and ZK circuits are scoped per project after we have seen the code. We will give you a fixed timeline with the quote, not an estimate that moves.
Yes. Fix review is part of the engagement, not an upsell. We re-run the original proof of concept against your patched code and confirm the fix has not introduced a new path.
Send the repository and a commit hash through the contact form, message @bugtester25 on Telegram, or book a 30-minute scoping call. 200+ protocols audited · $4B+ secured · 0 hacks post-audit. Prefer email? info@safeedges.in.