dApp Audit — A dApp audit reviews a decentralised application end to end — the contracts, the front end that builds transactions, the wallet connection flow and the backend that supports them — because users lose funds to a compromised interface as often as to a contract bug.
Your users do not interact with your contracts. They interact with your interface, and they approve whatever it puts in front of them. That makes the front end a first-class security surface: what address it calls, what allowance it requests, what it displays versus what it actually signs, and which third-party scripts can change any of that.
We review the contract layer and the delivery layer together, then look specifically at the seam between them: transaction construction, allowance hygiene, signature request formatting, chain and address validation, and the failure modes when an RPC returns something unexpected.
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.
Yes — that is the point of a dApp audit. We review transaction construction, approval flows, address validation and the build pipeline, because a compromised interface drains users regardless of how good the contracts are.
Yes. We check what is displayed versus what is signed, whether EIP-712 payloads are readable, whether allowances are bounded, and whether a malicious response from any data source can change the destination of a transaction.
Then we focus on build reproducibility, dependency integrity and the guarantees a self-hosting user can actually verify — plus the contract-level protections that hold even with a hostile front end.
Yes, along with dependency pinning, subresource integrity and third-party script access. These are the mechanisms that decide whether a supply-chain compromise reaches your users.
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.