Cardano's Dijkstra Testnet Went Live Oct 21. Protocol 12 Is Still Waiting.

Cardano's refreshed Dijkstra testnet opened to the public on October 21, per an October 24 update from Intersect. Pool operators can pull config files, connect, and grab test assets from a faucet. Here's the catch. It's running Conway protocol version 11 on node release 11.1.3. The new Dijkstra rules aren't live yet.

Getting there takes two more moves. A node 11.2 prerelease has to ship, then a hard-fork initiation action and a testnet governance action have to clear. So the environment exists. The upgrade doesn't.

That distinction sounds like hair-splitting until you've watched a team try to debug a wallet during a live fork. With a stable baseline, an indexer or wallet can prove it handles today's transactions correctly before anyone asks it to read changed formats. When everything shifts at once, a broken balance display and a broken node look identical from the outside. Developers burn weeks separating the two.

So what should you actually track? Not announcement volume. Compatible releases, successful syncs, transactions that submit without drama, and disclosure of bugs that got found and fixed. A version number in a roadmap isn't a release. Check what the config file demands.

The commercial backdrop makes this less academic. Cardano's stablecoin liquidity is up 61%, and money sitting in stablecoins wants an app layer that doesn't break. Reliability is the product. Liquidity without working infrastructure is a bucket with a hole in it. I'd argue the app teams building on Cardano right now matter more to the next twelve months than any single protocol feature, and those teams are judged on shipping, not on hard-fork optics. The check writers are getting pickier, and they've started asking for sync logs.

No mainnet activation date came with this. Anyone repricing ADA because a testnet went public is reading the wrong line. Follow the node release notes instead.