Dingo: Why Node Diversity Matters for Cardano

ADAvault supports the Dingo treasury proposal. Node diversity is one of the most important infrastructure investments the Cardano ecosystem can make, and we believe the treasury should fund it.

Why Node Diversity Matters

Today, Cardano runs on a single node implementation written in Haskell. That means every stake pool, every relay, and every block producer runs the same codebase. A critical bug in that single implementation affects the entire network simultaneously — there is no fallback.

Ethereum learned this lesson and invested heavily in client diversity. The result is a more resilient network with multiple independent implementations (Geth, Nethermind, Besu, Erigon) that can catch each other’s bugs. A critical vulnerability in one client doesn’t take down the whole network — operators can switch to an alternative while the issue is patched.

Cardano needs the same resilience. A Go implementation like Dingo provides exactly that.

Where Dingo Stands

The numbers speak for themselves: 1,226 commits, 205,500 lines of code, 48 releases, and a node that boots. Getting through chain sync and the Ouroboros handshake protocols is non-trivial — this is real, substantive progress.

Charles Hoskinson has publicly endorsed the project after meeting the team in person, and his confidence carries weight given his deep understanding of the complexity involved:

Having spent time with the team in Japan while on the tour and at the node diversity summits, I have full confidence they can deliver on time. I highly recommend people fund Dingo

— Charles Hoskinson (@IOHK_Charles) March 8, 2026

The Technical Challenge

Re-implementing cardano-node is not a port — it’s a ground-up re-implementation from specification. The Haskell codebase is 300K+ lines with deep dependencies on the formal verification ecosystem. The ledger rules alone span multiple eras (Byron through Conway), and the Plutus script evaluator must produce bit-for-bit identical results to avoid consensus divergence.

This is hard work, and it takes time. But it’s exactly the kind of foundational infrastructure that treasury funds should support. The ROI for network resilience is substantial — even a single prevented chain-wide incident would justify the investment many times over.

Other Efforts: Torsten (Rust)

Dingo isn’t the only alternative node implementation in progress. We’re also tracking Torsten, a Rust implementation by Michael Fazio of Sandstone Pool. It’s early stage — around 40,000 lines of Rust across a well-structured 10-crate workspace — and can connect to preview testnet, sync to tip via Mithril, and respond to local queries.

However, it’s important to be clear-eyed about where it stands. The consensus-critical paths — VRF verification, ledger state replay, reward calculations — are not yet producing correct results. This isn’t a criticism of the effort; it’s a reflection of the exceptionally high compliance and security bar that any node implementation must clear before it can be trusted on a production network. Getting Ouroboros Praos, multi-era ledger validation, and Plutus script evaluation bit-for-bit correct against the reference implementation is the bulk of the work, and it’s the hardest part.

We’ll continue to watch Torsten’s progress with interest. More implementations attempting this challenge — regardless of where they are today — is a healthy sign for the ecosystem.

Our Position

As stake pool operators running four pools on the Cardano network, we have a direct interest in network resilience. A single-implementation network is a single point of failure, and that’s a risk we’d like to see addressed.

We encourage delegators and DReps to consider supporting the Dingo treasury proposal. This is infrastructure-level investment in Cardano’s long-term security and stability.