INTERSECTION / DEAI × COSMOS SDK

DeAI × Cosmos SDK.

Proof-of-Compute consensus design and DeAI infrastructure on Cosmos SDK substrate — contributor engineering on Gonka.

§1 — What we ship on Cosmos SDK.

What we ship on Cosmos SDK.

The DeAI practice's Cosmos SDK work runs through Gonka, a Bitfury-backed L1 for AI compute built in Go on Cosmos SDK. Cosmos SDK supplies the chain substrate — consensus, networking, IBC, governance — without dictating the verification primitive layered on top. The DeAI-specific engineering happens above the substrate: designing the Proof-of-Compute module that turns a generic Cosmos chain into a chain that verifies ML compute. Zpoken contributes to that consensus work and built app.gonka.ai.

§3 — What DeAI on Cosmos SDK actually requires.

What DeAI on Cosmos SDK actually requires.

Cosmos SDK is a good chain substrate for DeAI because it's modular — the verification primitive can be a custom module without rewriting the chain. Three things make DeAI chains different from generic Cosmos chains.

01.

The PoC module is the chain's reason to exist.

For DeAI compute chains, the Proof-of-Compute module isn't a feature — it's the substance of the chain. A generic Cosmos chain plus a PoC module is a DeAI chain. Designing that module — the Sprint mechanism on Gonka — is the core engineering investment. The rest of the chain (IBC, governance, token mechanics) is inherited from Cosmos SDK.

02.

Off-chain artifact handling.

DeAI compute generates artifacts (inference outputs, partial proofs, attestations) that don't fit on-chain at scale. Cosmos SDK chains for DeAI need off-chain artifact storage with on-chain commitments — Gonka's MMR-based approach with on-chain root_hash + count is the canonical pattern. The on-chain layer commits; the off-chain layer stores; the verification module checks both.

03.

Application-surface integration.

Gonka exposes a network application surface — app.gonka.ai — that interacts with the chain over the Cosmos SDK API. The integration shape matters: hosts onboard, submit work, claim rewards, monitor reputation, all through the application layer. Building this surface alongside the consensus work is part of the engagement shape.

— CAPABILITYDecentralized AI→
— CASE STUDYGonka→
— ECOSYSTEMGonka — contributor→
— ENGAGEMENT

If you're building a Cosmos-SDK DeAI chain, talk to a founder.

If you're building a Cosmos-SDK-substrate DeAI chain — PoC consensus, inference verification, agent infrastructure — the engagement starts with a 30-minute call.

That call is with a founder. Shapes, discovery, and terms → /engagement

Book a call→ Open the form