A Go audit is a security review of blockchain infrastructure written in Go — Cosmos SDK modules, node clients, relayers and validator tooling — focused on state-machine determinism, module permission boundaries, unbounded work per block, and the concurrency bugs that cause consensus failure or chain halts.
In Go blockchain code the worst outcomes are usually liveness and consensus, not a drained contract. A map iterated in random order, a floating-point calculation, a call to time.Now() in state-transition logic — each produces different results on different nodes and halts the chain. An unbounded loop in an EndBlocker gives an attacker a way to fill blocks with work nobody paid for.
We review Go chain code for determinism first, then for authority: which module can call which keeper method, which module accounts can mint, and whether a governance proposal can execute a message that bypasses the checks the module enforces. Node and relayer code gets the standard offensive treatment — untrusted input parsing, RPC exposure, key handling, and goroutine lifecycle under adversarial load.
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.
Because non-determinism in state-transition code is a chain halt, not a bug report. Map iteration order alone has taken production chains down, and it looks completely ordinary in review unless you are looking for it.
Yes — RPC exposure, key custody, sentry architecture and the operational configuration. It is frequently the softest path into a chain and it is out of scope for a contract-only audit.
Reviewed explicitly. Migrations that exceed block limits or corrupt state are one of the highest-consequence failures in a Cosmos chain, and they only run once, in production.
Yes: packet lifecycle, timeout and acknowledgement handling, ordering assumptions and refund correctness, plus the relayer configuration around 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.