Developers Office Hours #65 - Dingo: High-Performance Cardano Node (12 June)

Developers Misc Dev Talk
,
1

dev
dev1200×630 104 KB

:rocket: Dingo: High-Performance Cardano Node

Join Chris Gianelloni (CEO, Blink Labs) for a discussion on Dingo, an alternative high-performance Cardano node and block producer written in Go.

We’ll explore its vision, current direction, and what’s coming next, along with its role in strengthening Cardano through implementation diversity.

:date: Friday, 12 June

:eight_o_clock: 14:00 UTC

:link: AddEvent

Be the first to know when the next Developers Office Hours are scheduled.

You can subscribe directly to the calendar here: Cardano Developers | AddEvent

Join the discussion below! We’ll update this thread with the recording link as soon as it’s live.

1 Like
2

Summary: Next-Gen Node Diversity with Dingo

In the 65th edition of the Developers Office Hour, the host speaks with Chris Gianelloni, CEO of Blink Labs, about Dingo. Dingo is a high-performance Cardano node and block producer written entirely in the Go programming language. This alternative implementation represents a massive milestone for ecosystem resilience and node diversity.

From Data Node to Block Producer
Dingo originally started as a data node, which meant it relied on a trusted Haskell node to validate the blockchain. However, the team has since evolved Dingo into a fully capable block producer. This means Dingo now operates in a “trust no one” space; it performs all validation itself using the same consensus rules as the standard Haskell node. Developers and stake pool operators can now run Dingo without relying on any external vendor or third-party infrastructure.

Architecture and Cloud-Native Storage
Under the hood, Dingo separates its storage into two distinct databases. The first is a blob store that uses an LSM tree to efficiently save raw blocks, while the second is a relational metadata database. Dingo features a pluggable storage backend, allowing it to write metadata directly to an external PostgreSQL database. This effectively replaces the need for resource-heavy stacks like Cardano DB Sync, enabling developers to build applications using standard SQL queries. Furthermore, Dingo is designed to be cloud-native, supporting object storage (like AWS S3) and envelope encryption via hardware security modules for enterprise key management.

Rich API Support
To drastically reduce the burden on developers, Dingo natively supports a wide array of popular APIs. Out of the box, it offers the UTxO RPC API, the Rosetta/Mesh API, and a “mini Blockfrost” API that was built specifically to support wallet development. A node operator can flexibly configure Dingo to act solely as a secure block producer, or simultaneously run it in API mode to serve data to DApps.

Roadmap and Mainnet Readiness
Currently, Dingo is actively producing blocks on the preview testnet, accounting for a significant percentage of network activity. The main remaining gap before achieving complete feature parity with the Haskell node is validating the exact reward calculations from the genesis block forward. Over the next quarter, Blink Labs will conduct a full external security audit and ensure compatibility with the upcoming Ouroboros Leios and Dystra era hard forks before officially declaring the node ready for the Cardano mainnet.

Top Five Q&A (FAQ) about the Dingo Node

Question 1: What is Dingo, and why is node diversity important?
Answer: Dingo is an alternative Cardano node and block producer written in Go. Node diversity is critical for network resilience because it eliminates a single point of failure. Having multiple independent implementations ensures that a single bug in one codebase cannot take down the entire Cardano network, and it encourages collaboration to harden the ledger protocol.

Question 2: How does Dingo handle database storage differently?
Answer: Dingo uses two separate databases: a fast blob store using LSM trees for raw blocks, and a relational metadata database. It allows operators to write metadata directly to an external PostgreSQL database. This completely removes the need for additional heavy infrastructure like Cardano DB Sync.

Question 3: What APIs are built into Dingo?
Answer: Dingo natively exposes several popular APIs to make developer integration seamless. This includes the UTxO RPC API, the Rosetta API, and a customized mini Blockfrost API that provides the necessary endpoints for building wallets and decentralized applications.

Question 4: Can Dingo be used in enterprise cloud environments?
Answer: Yes, Dingo is built with a cloud-native design. It supports writing data directly to cloud object storage (such as AWS S3 or Google Cloud Storage) and integrates with cloud hardware security modules (HSMs) for advanced key management and envelope encryption.

Question 5: When will Dingo be ready for the Cardano mainnet?
Answer: While Dingo is successfully producing blocks on the preview testnet, the team is completing a few final steps before recommending mainnet use. This includes finalizing exact reward calculations, undergoing a rigorous third-party security audit, and preparing for the upcoming Dystra era hard fork.

1 Like