We said first two weeks of February for testnet. We’re not there yet. A handful of integration issues and some unexpected dependency work pushed the timeline, and we’d rather say so than go quiet.
That said — our internal estimates from last year had testnet pencilled in for April. We’re targeting end of February now. Still ahead of where we thought we’d be, just not as far ahead as we hoped a month ago.
We’d rather take the extra time and ship something solid than rush a testnet that gives partners and developers a bad first impression.
Where we are right now
The chain is running internally. Consensus works. Blocks produce. Transactions execute. The work happening now is hardening — making sure the testnet is stable enough that external teams can build on it without hitting walls every few hours.
What’s landed recently:
- Confidential transaction processing — hardware-backed TEE enclave support merged this week. Encrypted payloads, attestation verification, replay protection. Full writeup here.
- Custom Narwhal-Bullshark DAG consensus — CometBFT replaced entirely. 100K+ TPS capacity, 300ms finality, no upstream dependency risk.
- All core modules enabled — DEX, Oracle, Lending, Stables, Privacy, Token Factory, CosmWasm smart contracts, IBC. These aren’t stubs. They run.
The pieces are in place. What remains is operational: deployment automation, monitoring, making sure the testnet holds up without someone watching it constantly.
What testnet means for partners
Once testnet is live, we stop asking partners to take our word for it.
SDK access. Partners and developer teams will be able to connect using standard Cosmos tooling — CosmJS, Keplr, any IBC-compatible wallet. We’ve got TypeScript client examples, CLI tooling, and REST/gRPC/RPC endpoints documented and ready.
Smart contract deployment. CosmWasm is enabled. Teams can deploy and test contracts against a live chain with real consensus, not a local mock.
Module integration. The DEX, oracle feeds, lending protocol, stablecoin minting — all of it is accessible on testnet. If you’re building something that touches any of these, you can start integrating against real endpoints instead of specs.
Cross-chain testing. IBC is enabled with bridge configurations for Bitcoin testnet, Ethereum Sepolia, and Solana testnet. Cross-chain flows can be validated end-to-end.
The plan from here
End of February — first external testnet deployment. Selected partners get access, RPC endpoints go live, documentation published.
March — broader testnet access, security audits begin, developer onboarding ramps up. We want feedback from real teams building real things, not just our own internal testing.
We’ll share connection details, faucet access, and SDK guides as soon as the testnet is stable and publicly reachable. If you’re a partner waiting on this — it’s close.
Timeline slipped. We said so. The chain is further along technically than our original April target assumed — we just needed more time on the operational side before handing it to external teams. A few weeks out now.