Dingo Passes Three Cardano Conformance Test Suites

Dingo passed all 10,536 test cases across three functional suites on the Node Diversity Conformance platform, according to its October 18 report. The results follow Blink Labs’ October 17 release of v0.85.0, which aligned the independent Cardano node’s reports with the current test datasets.

Dingo’s Results Across Three Functional Suites

The largest suite covers CBOR, the binary format Cardano uses to encode transactions and blocks. Dingo passed all 9,200 cases, correctly handling valid inputs, re-encoding them to the expected result, and rejecting invalid data.

Ledger validation accounted for another 277 cases. Each supplies a defined initial state, protocol parameters, and ledger era. Dingo accepted transactions marked valid and rejected those marked invalid with the expected validation failure.

All 1,059 UPLC test vectors also passed. UPLC is the language into which Plutus smart contracts are compiled. Its conformance scenario checks execution results separately from consumed execution budgets, which contribute to transaction fees paid in ADA.

Dingo’s overall platform score is 86.19% because the four scenarios receive equal weight. The fourth, a performance benchmark using real-world scripts, recorded a 44.77% pass rate across 10,000 reported cases. That figure measures compliance with the benchmark’s performance criterion, rather than relative speed against another node.

Shared Tests for Independent Cardano Nodes

Developed in Go, Dingo handles Ouroboros networking and consensus, ledger validation, and application access to blockchain data. It provides a separately developed implementation alongside the established Haskell cardano-node and clients such as the Rust-based Amaru.

Those implementations must agree on network rules. An ADA transfer or smart contract execution must receive a consistent validity decision regardless of which client processes it. Differences in transaction acceptance or execution-cost calculations can affect agreement about whether a block is valid.

Shared test datasets allow teams to check that behavior against the same inputs and expected outcomes. Each project runs the tests through its own continuous integration system and publishes reports, which Node Diversity Conformance collects and displays.

The scenarios include the fixtures and instructions needed to repeat the checks. Operators and developers can therefore reproduce a reported result and investigate discrepancies using the same test cases.

Dingo v0.85.0 Expands Developer APIs

The release also expands Dingo’s interface compatible with the Blockfrost API, adding wallet and decentralized application queries alongside historical and governance queries. Applications can use familiar request formats while Dingo supplies the underlying blockchain data.

Other changes address chain selection, Leios message handling, data storage, and resource management.

Blink Labs continues to state that Dingo is not ready for production block generation on mainnet. Developers can test the expanded API operations against Dingo instances on Preview, Preprod, Musashi, and local development networks, including queries for wallet activity, historical records, and governance data.