Diamond Proxy Audit — A diamond proxy audit is a security review of a contract system built on EIP-2535 (the Diamond Standard), where one proxy delegates calls to many implementation contracts called facets. It covers the shared storage model between facets, the function-selector routing table, the authority and initialisation logic of diamondCut, and the upgrade history of the diamond — the places where a diamond fails differently from a single-implementation proxy.
A diamond is a proxy with a routing table. Every external call is matched by its four-byte selector to a facet, and the facet runs with delegatecall in the diamond's storage. That buys modularity and escapes the contract size limit, and it multiplies the ways an upgrade can go wrong: every facet writes to the same storage, every diamondCut can add, replace or remove dozens of selectors at once, and a single initialisation call runs arbitrary code with the diamond's full authority.
Our review starts from the live selector table rather than the repository. We reconstruct which facet answers which selector at the audited commit and on-chain, check every storage struct against every other facet that touches the same slot, and treat each diamondCut in the deployment and upgrade scripts as privileged code that needs its own review. Findings that can be exploited come with a Foundry proof of concept against a fork of the deployed diamond.
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.
A diamond is an EIP-2535 proxy contract that routes each function selector to one of many implementation contracts (facets) and executes it with delegatecall in the diamond's own storage. Facets can be added, replaced or removed through diamondCut, and loupe functions report the current routing table.
Not inherently, but they have more surface. Shared storage across many facets, a routing table that changes with every cut, and an initialisation call with full authority give more ways for an upgrade to corrupt state or hand over control.
Storage collisions introduced by an upgrade: a new facet or a reordered AppStorage struct writing over slots another facet relies on. They compile, they pass unit tests, and they corrupt live state the moment the cut executes.
Yes, and it is the most valuable time to do it. We compare the proposed cut against the live selector table and storage layout, simulate it on a fork, and confirm nothing existing breaks before you execute it.
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.