Overview
DAIT is a sovereign Layer-1 for verifiable AI compute. This page covers what the chain is, what makes it different, and the seven custom modules that ride on top of cosmos/evm.
What DAIT is
DAIT is a Cosmos SDK chain with a parallel EVM, built by forking github.com/cosmos/evm v0.6.0 (Cosmos SDK v0.53.x, CometBFT v0.39.x, Block-STM parallel EVM, Apache-2.0). On top of the standard Cosmos modules it adds seven DAIT-specific ones for staking tiers, hardware-attested compute, marketplace economics, off-chain channels, native messaging, and AI-agent accounts.
The thesis is simple. AI inference is too expensive to run inside an L1 execution loop, but it can be witnessed by an L1: hosts execute work inside a hardware-attested TEE, post a signed receipt, and the chain verifies the receipt and credits the host. No zk-circuit on the hot path. No oracle committee voting on outcomes.
Key concepts
| Concept | What it means here |
|---|---|
| TEE attestation | Intel TDX, AMD SEV-SNP, or NVIDIA NRAS quote that proves a piece of code ran inside a confidential VM on a known platform with a known measurement. |
| PoUW credit | A non-transferable, decaying score earned by hosts when they post a valid attested inference receipt. Validators are paid block rewards weighted by delegated PoUW. |
| State channel | An off-chain Nitro / ForceMove session opened with one tx and closed with one tx. Inference calls inside the channel never touch L1 until the channel closes or is challenged. |
| SPUR-IC receipt | The over-the-wire signed receipt format that travels in X-DAIT-Receipt headers. Same on the wire across TypeScript, Python, and Go. |
| Trinity, Quartet | The 3-validator genesis ceremony, then promotion to 4 in Hour 1, exercising the on-chain validator-add flow on Day 1. |
Why not an L2?
Two reasons. First, AI compute auctions need their own block space and their own reward weighting; sharing a chain that prices DEX trades by gas works against you. Second, TEE attestation verification is determinism-sensitive (no system clock, no network access from inside the verifier) and that fits cleanly into a custom Cosmos module but is a fight inside an EVM precompile.
The result is a chain where every parameter was chosen for AI-compute economics: 999ms blocks targeting 369ms after IAVLx lands, 99M block gas, 189 active validators out of a 999-slot standby pool, fair launch with no presale.
The seven modules
x/staking_tiers- User, Heavy, Node, Supernode, Validator, Oracle. Each tier is a stake floor with tier-specific slashing.x/tee_attest- Verifies TDX, SEV-SNP, and NRAS quotes on-chain. Quote bodies live off-chain (DA pointer); only the result and content hash are persisted.x/pouw- Mints PoUW credits from attested receipts via commit-reveal. Credits decay with a 14-day half-life.x/compute_market- Reverse Dutch auction. Tenant escrows, auction settles, lease streams uDAIT block-by-block to the winning host.x/state_channel- Open, transact off-chain, close. 24h challenge window, highest signed turn_num wins.x/messaging- On-chain pubkey + contact graph, off-chain Waku transport, libsignal for 1:1 and OpenMLS for groups.x/agent- AI agents as first-class accounts on top ofx/accounts. Operator + hotkey two-key model with rolling-24h spend policies.
Where to go next
- If you want to run a local devnet right now, jump to the quickstart.
- If you are evaluating the chain, read the three roles next.
- If you are a smart-contract developer who already speaks EVM, head to EVM JSON-RPC.