Cardano’s Dingo Node Advances Testnet Block Production as Go-Based Infrastructure Expands

Blink Labs has presented a new development update for Dingo, an alternative Cardano node implementation written in Go. During Developers Office Hours #65, Blink Labs CEO Chris Gianelloni described how Dingo has moved from its original role as a data node toward infrastructure that can validate Cardano data, produce blocks on test networks and serve local APIs for applications.

For Cardano, the update is relevant because Dingo addresses a core infrastructure issue: node diversity. A network that depends too heavily on one dominant implementation carries operational risk, while independent clients can help expose assumptions, improve testing and give developers more ways to build against the same protocol.

Dingo Strengthens Cardano Node Diversity With a Go-Based Client

Dingo is an open-source Cardano node project developed by Blink Labs. The project began as a data node designed to capture blockchain data, index it and serve it through APIs. Gianelloni said the original performance focus came from that indexing role, where Dingo was designed to combine functions that are often handled through a larger stack involving cardano-node, DB Sync and Postgres.

The project now covers a wider set of infrastructure functions. Dingo can operate as a data node, API service and testnet block producer, depending on how it is configured. Its Go-based implementation adds another technical route for Cardano infrastructure, alongside the established Haskell node and other alternative client work in the ecosystem.

That client diversity can increase network resilience because separate implementations test the protocol from different code bases. Gianelloni said work with other Cardano infrastructure teams has helped identify where some assumptions are tied to a specific implementation rather than the protocol itself.

Blink Labs has also connected Dingo’s development to a Cardano treasury proposal focused on production readiness, Dijkstra hard fork readiness, Leios support and mainnet block production. The proposal requested ADA funding for continued work on Dingo as a production-grade block producer.

Preview Block Production Moves Dingo Beyond Data Indexing

Gianelloni said Dingo is already producing blocks on Cardano’s Preview network. During the presentation, he said Dingo had produced around 3 percent of blocks over the previous day on Preview and around 4 percent across the latest 100 blocks shown at the time.

That activity moves Dingo into a more practical testnet role, but it does not make the project mainnet ready. Blink Labs continues to present Dingo as software under active development, with current use focused on Preview, PreProd and devnet environments rather than production mainnet operation with real funds.

The move toward block production also changes the trust model behind Dingo’s data services. A pure data node needs another validating node in the stack. As a block producer, Dingo can validate chain data locally and then use that validated data as the basis for its own API services.

Gianelloni also presented example applications built around Dingo. Dingo Swap uses Dingo data and the UTxO RPC API on Preview, GovLens reads governance data from Dingo’s metadata database, and Dingo Explorer uses a Blockfrost-compatible API served locally by Dingo.

APIs, Mithril Sync and Security Work Define the Road to Mainnet

Dingo is being developed as an infrastructure stack for multiple developer use cases. The project supports UTxO RPC, a Mini Blockfrost API surface, Rosetta API support and metadata output to Postgres. That setup allows developers to build applications, dashboards and reports using familiar database tools while relying on data indexed and validated through Dingo.

The project also uses Mithril for faster bootstrapping. Gianelloni said Mithril Sync is one of the main recommended ways to get Dingo operational, especially in API mode, although Dingo still needs to process and index the data after the initial synchronization.

Blink Labs also described several remaining steps before broader production use. These include reward calculation validation, security hardening, mainnet-scale testing, storage optimization and an external security audit. Gianelloni said the team wants to complete the audit and address any remediation items before telling operators that Dingo is ready for mainnet use.

Dingo currently changes the state of Cardano’s testnet infrastructure, not the status of mainnet operations. It now has Preview block production, local API examples, a Postgres metadata model, observability tooling and a roadmap tied to security review and scaling work. For Cardano’s node diversity effort, the update gives Dingo a concrete role as a working Go-based implementation that developers and operators can test before any wider production deployment.