NFT Due Diligence — NFT due diligence reviews a collection's contracts and configuration — mint mechanics, allowlist integrity, metadata storage and mutability, royalty enforcement, and the privileged powers the deployer retains — to establish what the team can still change after mint and what a buyer is actually acquiring.
Most NFT losses are not clever exploits. They are mint functions that can be called by the deployer for free, metadata pointing at a mutable server, an allowlist that can be regenerated, or an owner function that can transfer any token. Buyers rarely check, and the information is entirely on-chain.
We review the contract mechanics, then the off-chain dependencies that decide whether the asset survives the team losing interest, then the privileged control surface — with a plain statement of what the deployer can still do after mint.
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.
What the team can still do after you buy: change metadata, mint more, transfer your token, redirect royalties or pause transfers. Everything else is opinion; this is verifiable on-chain.
Yes — it is one of the more common requests. We review the deployed bytecode and current configuration, not the marketing, and report what the deployer retains.
We report the mechanisms objectively: unlimited mint authority, mutable metadata, withdrawable funds, force transfer. Those are facts about the contract. We do not speculate about intent.
We check where it lives, who can change it, whether IPFS content is actually pinned, and what happens to your token if the hosting stops being paid for.
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.