Proposal “revised-dashgo-m1“ (Active)Back

Title:DashGo - Independent Node Client built in Go
Owner:prasad-chainscore
Monthly amount: 295 DASH (9960 USD)
Completed payments: no payments occurred yet (6 month remaining)
Payment start/end: 2026-02-27 / 2026-08-20 (added on 2026-03-14)
Final voting deadline: in 1 month
Votes: 2 Yes / 37 No / 0 Abstain
Will be funded: No. This proposal needs additional 336 Yes votes to become funded.
External information: www.dash.org/forum/threads/pre-proposal-dash-go-an-independent-full-node-client-for-dash.68441/
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many d9c2b93514328632fb7ed9d1d77b437d9e7e017f00bda1f1e1099159b3e3f19f funding yes

Please login or create a new DashCentral account for comfortable one button voting!

Proposal description

Note: Based on the feedback about budget constraints and importance of node-diversity for Dash’s long term resilience, we have revised the proposal with limited resources yet achieving the complete scope.

----

We propose the development of DashGo, a new, independent full-node client for the Dash network, implemented from the ground up in Go.
The primary objective of DashGo is to strengthen Dash’s long-term network resilience by reducing reliance on a single node implementation, while also improving operator experience, observability, and developer reuse.

https://raw.githubusercontent.com/prasad-kumkar/asset-store/main/dash/dashgo.png

This proposal focuses on building a production-grade alternative client that can run alongside Dash Core.

Why do we need another node client?

Today, Dash relies on a single full-node implementation. While mature and battle-tested, a single-client architecture introduces systemic risk:
  • A critical bug, consensus issue, or security flaw affects the entire network simultaneously
  • Network upgrades and experimentation are constrained by one codebase
  • Node operators lack modern, built-in observability and deployment tooling
  • Developers cannot easily reuse Dash internals without running a full node
https://raw.githubusercontent.com/prasad-kumkar/asset-store/main/dash/client_diversity_chart.png

Most resilient blockchain networks mitigate this risk by maintaining multiple independent client implementations. Dash currently does not.

Proposal

DashGo is an independent, alternative Dash full-node client written in Go, designed with a focus on the following pillars:
  1. Network Resilience: DashGo provides a second, independently implemented client that reduces single-client risk. In the event of a critical issue in the primary client, the network retains an alternative implementation capable of maintaining continuity.
  2. Modern Node Monitoring and Observability: DashGo includes native support for modern monitoring stacks such as Prometheus and Grafana. Masternode operators gain real-time visibility into node health, peer connectivity, sync status, and performance metrics without relying on external tooling.
  3. Modular and Extensible Architecture: The client is built as a set of decoupled libraries. This enables developers to reuse Dash components such as networking, consensus logic, or indexing in other applications without operating a full node.
  4. Easier Operator Onboarding: DashGo is designed for fast, reliable deployment through:
  •   One-click cloud images for AWS, GCP, and Azure
  •   Infrastructure-as-Code templates using Terraform and Helm
  •   Secure defaults, automated bootstrap, and preconfigured monitoring

https://raw.githubusercontent.com/prasad-kumkar/asset-store/refs/heads/main/dash/client_share_pies.png


Why Go?


  • Memory-safe by default compared to C++, reducing classes of bugs common in low-level systems.
  • Best suited for concurrent infra like networking, syncing, RPC, and concurrent node workloads.
  • Large ecosystem of infra developers makes long-term maintenance and hiring more practical.
  • Strong libraries and modules let us build faster on proven components.
  • Cross-platform binaries make deployment simple: write once, run anywhere.
  • Cleaner, more maintainable codebase helps support long-term client diversity.

Scope of Work

Read the full Technical Specification:[color=#333333]https://docs.google.com/document/u/1/d/e/2PACX-1vTsHCNuwF0NodA823Ujprij4XOUh5nVWu1Gjh4GWb2DfBZDKmfU5UL7cO2NEFPjDqgK19lxe-y9ATSS/pub[/color]To minimize risk and establish trust within the Dash community, the DashGo full-node specification is deliberately structured into two phases with multiple milestones.
  • Phase 1 consists of four milestones and focuses exclusively on delivering a fully independent consensus node client.
  • Phase 2 builds on this foundation by introducing Dash-specific services.
By the end of Phase 1, DashGo will be capable of independently validating the Dash blockchain and maintaining correct chain state.

Team and Budget

Chainscore Labs is a Web3 Research and Development firm founded in 2021. We have been working with leading L1 teams like Polkadot, Cardano and Ethereum to implement independent node clients that help them achieve 100% uptime. We specialize in delivering core, high-performance infrastructure for leading blockchain ecosystems. We have deep expertise in protocol engineering, cryptography, DeFi, and full-stack protocol development. More details in proposal spec. Website

To deliver Milestone 1, we are requesting a budget of $57,000, equivalent to $9,500 (~295 DASH at 32 DASH/USD) per month over 6 months. This funding will cover engineering costs for 3 protocol engineers.

Closing


Dash has always prioritized reliability and real-world usability. Investing in an independent node client is a direct investment in the network’s long-term health.
We request your vote in support of DashGo. Thank you for your consideration.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
1 point,14 hours ago
I really like the idea of having more than 1 client. As you say most mature projects have more then 1 which also decentralize the eco system.
I can see the proposal will not pass with many NO's. What i would suggest is to anchor this proposal with the dev community for sustainable solution and making sure this will align with the existing and future roadmap.
Creating a tool is one thing but maintaining and making sure it will continue to work is another huge factor.
I really like that you have a tech spec included, this means you spend some time on this. What could help is to get this reviewed by a dev team member (maybe even by @quantum_explorer) to see its viability and get some feedback on it.

Anyway i hope we can get this approved at some point. I for one support the idea of more clients for Dash!
Reply