GameFi Audit — A GameFi audit reviews Web3 games as economic systems: the contracts holding assets and rewards, the randomness that decides outcomes, the off-chain game server that reports results on-chain, and the economy design that determines whether the game can be farmed to death.
Web3 games fail economically more often than they fail cryptographically. The typical loss is not a drained contract but an economy where a bot earns more than it spends — infinite reward loops, breeding or crafting arbitrage, mint conditions that can be automated, or a marketplace fee model that makes wash trading profitable.
We review the contract layer and the economy together, plus the seam almost every Web3 game has: a centralised game server that tells the chain what happened. If that server can be tricked or impersonated, no amount of contract security helps.
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.
Both. We model the economy adversarially — what a bot farm earns per dollar spent — because that is how most Web3 games actually die, not through a contract exploit.
We check the source and the commitment order: whether the outcome is knowable or influenceable before it is committed, and whether a VRF callback can be reverted or retried until the result is favourable.
Yes, and the trust boundary is the priority: how results are signed, whether they can be replayed, what the server key can mint, and what a player can prove if the server misbehaves.
Yes. We look for actions with no meaningful cost, reward criteria that scale with account count, and any loop where automated play is net-profitable at the protocol's expense.
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.