DeFi Security Audit — A DeFi security audit reviews both the code and the economics of a protocol: not only whether functions execute correctly, but whether the incentives, price sources, liquidation paths and composability assumptions still hold when an attacker arrives with a flash loan and full control of transaction ordering.
The largest DeFi losses are rarely pure implementation bugs. They are correct code operating on wrong assumptions: a price feed that can be moved, a bad-debt path with no backstop, a bonding curve that can be walked, a reward accounting model that can be farmed by entering and exiting inside one block. A reviewer who only reads Solidity will pass these.
We model your protocol as an adversary would: what is the cheapest capital that moves the system into a state you did not anticipate, and what does the attacker take out? That means invariant testing on solvency and share pricing, flash-loan-funded exploit simulation on a forked network, and a written review of every external protocol you depend on — because your risk includes their design decisions.
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.
| Severity | What it means |
|---|---|
| Critical | Direct loss of funds or permanent freezing of assets, exploitable by any actor. |
| High | Loss of funds or protocol insolvency under realistic conditions, or requiring a privileged actor to misbehave. |
| Medium | Broken protocol behaviour, denial of service, or value leakage that does not directly drain the contract. |
| Low | Edge-case incorrectness with limited impact, or an issue requiring implausible preconditions. |
| Informational | Code quality, gas efficiency, documentation mismatch and defence-in-depth suggestions. |
Single token contract: starts from $999, report in 24–48 hours. dApp, GameFi or RWA project: starts from $2,999. DeFi protocol, L2 / rollup, Bridge, ZK circuit, AI agent / MCP: scoped per project after we have seen the code.
Economics. We test whether the incentives and price sources survive an adversary with flash-loan capital and control over ordering — bad debt, share inflation, reward recycling, governance capture — not just whether the functions are implemented correctly.
Yes. We write the invariant and fuzzing harness as part of the review and hand it over, so your CI keeps testing the same properties long after the engagement ends.
Yes, and we prioritise differently: what is exploitable now, what can be mitigated by a parameter change today, and what needs an upgrade. Anything critical is reported the day we find it.
We treat every dependency as untrusted and document what you are assuming about it — pause rights, upgradeability, fee changes, re-entrancy through callbacks. Composability risk is written into the report as an explicit assumption list you can monitor.
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.