Roadmap & Reports

Dingo is Blink Labs' Go implementation of a Cardano node.

This page tracks where the work came from, what exists today and what the treasury-funded roadmap is intended to deliver for DReps, SPOs and developers.

View Dingo on GitHub Read Treasury Proposal

Dingo's Path

Past work built the pieces. This funded roadmap takes Dingo from testnet block production to production readiness.

Since 2021

  • Blink Labs builds Cardano infrastructure in Go.
  • gOuroboros mini-protocol foundation.
  • Apollo, Ogmigo, Kugo and UTxO RPC Go SDK support.

Prior Catalyst + self-funded work

  • Initial Dingo development.
  • Plutigo Plutus evaluator.
  • ouroboros-mock conformance framework.
  • Archive-node storage, proxying and pruning.
  • Adder indexing/event pipeline.

Proposal Baseline

  • Dingo operated as a Cardano relay node, syncing across eras.
  • 314 conformance tests passing.
  • Plutus V1/V2/V3 at 100% conformance.
  • ChainSync, mempool, governance transaction support.
  • VRF/KES block forging primitives.
  • Preview block-production.

Q2 2026: Complete

  • ✓ Praos consensus completion.
  • ✓ Hard fork combinator.
  • ✓ Genesis bootstrap.
  • ✓ Stable preview/preprod sync.
  • ✓ Preprod block production.
  • ✓ Linear Leios prototype with IO Engineering.
  • ✓ Musashi Dojo developer environment.

Q3 2026: In progress

  • Operational hardening.
  • Storage scalability at mainnet scale.
  • UTxO set management.
  • Long-running stability.
  • Security audit kickoff.

Q4 2026: Planned

  • Dijkstra readiness.
  • Plutigo V4.
  • Leios consensus integration.
  • Node-to-Client and LocalStateQuery gaps.

Ecosystem 2026 target

  • Dijkstra hard fork expected by end of year.

Q1 2027: Target

  • Audit completion.
  • Mainnet block-production readiness.
  • Mithril integration.
  • Operator documentation.
  • Ecosystem integration.

Upcoming Work

  • Continue mainnet-scale storage and long-running stability validation, including cross-node ledger comparisons and target-volume benchmarks.
  • Advance Dijkstra readiness, Plutigo V4, Leios consensus integration, and remaining Node-to-Client and LocalStateQuery work.
  • Complete the claim process for matured M-4 through M-7 milestones and engage the auditor so the board can resume M-10 and the security audit can begin.

Risks and Issues

  • Mainnet-scale validation remains open. Backend conformance and storage optimizations progressed, but target-volume benchmarks and weeks of continuous-operation evidence are still needed to complete the Q3 scope.
  • Security audit not yet started. M-10 remains funded but Paused pending auditor engagement. The planned Q3 kickoff carries into Q4, leaving less time for the audit and remediation before the Q1 mainnet-readiness target.

Funding Use

A simple view of how treasury funding moved from ADA approval into the USDCx contract used for Dingo delivery. Transaction-level records and formal progress updates live in the public journal and reports linked below.

Received

6,900,000 ADA

Treasury withdrawal approved for the Dingo roadmap.

Kraken OTC Conversion

5,630,001 ADA → 1,531,360.27 USDC

Includes a 1 ADA test transaction plus the 5,630,000 ADA OTC trade. Recorded in the public journal.

Returned To Treasury Contract

1,531,307.86 USDCx

Bulk USDCx bridge used for vendor funding and treasury remainder. Separate test bridge: 99.99 USDCx.

Contingency at Funding

2,974.53 USDCx Remaining amount after vendor milestone funding.

+ 900,001.18 ADA Recorded when vendor milestones were funded.

Vendor Schedule

1,528,333.33 USDCx

+ 370,000 ADA

Total milestone allocation from the funding metadata.

Claimed To Date

458,333.33 USDCx

+ 92,500 ADA

4 of 14 milestones claimed, based on journal entries and their withdrawal metadata.

Unclaimed Schedule

1,070,000.00 USDCx

+ 277,500 ADA

Remaining scheduled milestone amounts, including any paused milestones.

Latest Updates

Progress report summaries and recent treasury transactions are generated from the public Markdown reports and journal during the Pages build.

Latest Progress Report

Progress Report - Q3 2026

Q3 focused on making Dingo more reliable under sustained use: storage and mempool work, ledger correctness, recovery, and testing across database backends. The Leios prototype continued to track Musashi, while Dijkstra and Plutus V4 work carried forward into the next quarter's scope.

July introduced a DAG mempool and lock-free ledger snapshots, expanded reward and governance processing, and kept Leios aligned with four successive Musashi prototype revisions. August added real SQLite, PostgreSQL, and MySQL conformance runs and hardened block production, database lifecycle handling, and Leios fetch and recovery paths. September improved SQL hot paths, added database and ledger-pipeline metrics, and introduced a Koios-backed from-genesis parity run. Throughout the quarter, gOuroboros supplied protocol and ledger fixes, Plutigo advanced V4 support, and ouroboros-mock expanded the fixtures used to test Dingo.

Read the full report
Earlier reports

Recent Treasury Journal

Browse the full journal