How Cosmos SDK / IBC smart contracts work
- Language
- Go for Cosmos SDK modules, Rust for CosmWasm contracts
- Runtime
- Sovereign app chains built with the Cosmos SDK on CometBFT consensus, connected over IBC, with optional CosmWasm (WebAssembly) contracts
Languages and tooling we review
- Go
- Cosmos SDK
- CosmWasm
- ibc-go
Cosmos SDK / IBC vulnerability classes we check
Bug classes that come from how Cosmos SDK / IBC works, checked on every Cosmos SDK / IBC audit alongside the usual logic and access control review.
- Non-determinism in modules (map iteration, floats, local time) that halts consensus
- Unbounded work in BeginBlock and EndBlock that stalls the chain
- IBC packet handling: timeouts, acknowledgements and denom tracing
- Missing signer authorization in message handlers
- CosmWasm submessage and reply handling errors
Cosmos SDK / IBC audit focus and capabilities
We tailor our review to the unique architecture and common pitfalls on Cosmos SDK / IBC.
Why teams choose Cecuro for Cosmos SDK / IBC
// Example finding severity: HIGH title: Missing access control on upgrade() impact: Arbitrary logic upgrade can brick the protocol recommendation: Restrict to time-locked admin + add emergency pause