On this page
Dash is an active cryptocurrency network designed for payments, with a second layer of service nodes supporting additional functions. Its development has expanded beyond the original digital-cash pitch: Dash Evolution adds infrastructure for applications and decentralized data. The project maintains official documentation for both the payment network and this application layer as of October 8, 2026.
The distinction between those layers is important. Sending DASH, running a regular masternode and operating an Evolution masternode are different activities, with different software and resource requirements.
How the payment network works
DASH is the native coin of its own blockchain. Miners use the X11 proof-of-work algorithm to produce blocks. Masternodes provide additional services, including transaction and chain-locking functions, rather than replacing mining altogether.
InstantSend is designed to lock transaction inputs, reducing the risk that the same funds can be spent twice. ChainLocks uses masternode quorums to help protect the accepted chain against reorganizations. These mechanisms address specific payment and settlement problems; they do not make every wallet, exchange or merchant integration secure.
For example, an exchange can still delay crediting a deposit under its own policies. A merchant can still use a custodial processor. The speed of the blockchain feature and the time it takes a separate business to recognize a payment are not necessarily the same.
Regular masternodes and Evolution nodes
Dash's documentation specifies 1,000 DASH collateral for a regular masternode and 4,000 DASH for an Evolution masternode, also called an evonode. Evolution nodes have higher operating requirements and serve Platform as well as Core; regular masternodes serve Core.
Collateral establishes eligibility under protocol rules. It is not a subscription fee that buys a fixed return. Operators also need reliable infrastructure, suitable software and correct registration. Downtime or configuration mistakes can affect participation, and paying server expenses is separate from holding the collateral.
Shared-node products add another relationship. A person buying a share through an intermediary may not control the actual collateral or the node. The provider's custody, withdrawal and accounting arrangements therefore matter alongside Dash's native rules.
What Evolution adds
Dash describes Platform as a technology stack for decentralized applications. Its Drive and DAPI components provide data storage and an application interface. Official Evolution materials describe data contracts and searchable decentralized storage, rather than simply another payment confirmation mechanism.
This is a meaningful update to the older profile, which largely stopped at masternode payments. It also creates new evaluation questions: how applications authenticate users, who can modify their records, what data they store and what ongoing costs they impose.
An application using Dash infrastructure is not automatically endorsed by every Dash participant. The network's existence and an individual application's reliability are different claims. A polished interface should not substitute for a clear account of permissions and recovery procedures.
Supply, funding and rewards
Dash issues coins through its protocol and uses a budget system for approved proposals. Masternode voting is part of that funding process. This creates a mechanism for supporting work without treating every expenditure as proof that the intended result was delivered.
A project-funded proposal can be evaluated by its scope, milestones and outputs. Voting and payment records are useful evidence, but they answer different questions from software quality or merchant adoption.
The old article's annual reward estimate has been removed. Actual token rewards depend on network conditions and the relevant rules, while expenses and market prices affect their economic result. Supply estimates and node counts can change over time.
Privacy, markets and practical limits
Dash has historically offered transaction-mixing features. Mixing should not be described as guaranteed anonymity: transaction patterns, counterparties and information disclosed outside the chain can affect privacy. Service providers may also apply their own asset-support policies.
DASH can be encountered on cryptocurrency exchanges and payment services, but support depends on provider and jurisdiction. An old statement that it is available almost everywhere is not reliable enough for a current guide. The relevant checks are the supported network, fees, deposit status and withdrawal availability.
Dash is best understood as a payment network with specialized service-node functions and a newer application layer. The original masternode idea explains part of its history; the distinction between Core and Evolution explains more of the project that exists today.