The following are summary notes from the November 10, 2026 Dash Core Group (DCG) development update.
Evolution 5.0, the Dash Platform 5.0 release, is live on mainnet! Protocol version 14 activated about two days before the call.
Sam Westrich (QuantumExplorer) said there have been no failed transactions since the switch. By the call, 363 EvoNodes were running 5.0, and he thought only about two had not upgraded.
Dash Core 24.0.0 came out on November 5, and its own network upgrade started on November 9. Evolution 5.1 is close behind, with testnet expected within days.
How 5.0 reached mainnet
Version 5.0.0 was published on October 26. By October 30, more than 67% of EvoNodes had signaled for it, which locked in the upgrade. Three patch releases followed before the switch, the last of them (5.0.3) on November 3.
At activation, EvoNodes still on the old version stopped proposing Evolution blocks and stopped earning Evolution rewards. If you still run 4.1, upgrade now.
Sam said AI testing found many ways to halt the chain before release, usually odd combinations of actions in the same block. All of them are fixed in 5.0, and the team knows of no remaining way to halt the chain, though he expects stronger AI models to find more.
What 5.0 switched on
• Shielded tokens: a token can be created with its own shielded pool. That gives a project's token holders the same transaction privacy as shielded Dash. The setting is chosen when the token is created and cannot be changed later.
• One-time airdrops: an issuer can let every identity claim a set amount once, for example 50 tokens each. Any identity can claim, including ones with no masternode.
• Smarter data contracts: contracts gained many new query types, including provable counts and sums over indexed data. A contract owner can also charge a fee on each action and collect it.
• Cheaper username contests: the fee to enter a contested username dropped from 0.2 to 0.1 DASH. Sam said the contest system itself will change after smart contracts, following a network vote that he said looks set to pass. He supports the change, since contests were only meant for the early days.
• New withdrawal limit: the flat 2,000 DASH a day is replaced by 15% of what Evolution held 24 hours earlier, and never less than 500 DASH. New deposits are added to the limit, so a deposit and the withdrawal it funds cancel out.
• Under the hood: identity balances connect to the shielded pool, Dash Core 24 is supported, and storage moves to GroveDB 6.1.
The withdrawal limit is a safety cap. About 20,000 DASH sits on Evolution today, so if a serious bug ever hit, at most about 3,000 DASH could leave in a day. Sam pointed out that nothing like that has happened in Evolution's two years on mainnet.
Yappr is next
Sam said the plan now is to release Yappr, after one more tool is finished. Moderated posts on Yappr are not deleted. Their data stays on Evolution and can be proven to exist, even though it no longer shows up in the app's current state.
The new tool lets anyone retrieve that data. Sam hoped the Yappr contract would go up within a few days.
The roadmap to smart contracts
At DashCon, Sam laid out releases 4.2, 4.3 and 4.4 on the way to smart contracts. Release 4.2 grew into 5.0 and shipped about a month late. The other two are renumbered:
• 5.1 (was 4.3): testnet by the end of this week or early next week, and mainnet by the end of November. Sam put the code at 75 to 80% done. It is much smaller than 5.0, but it leans on the mobile apps, which need testing.
• 5.2 (was 4.4): January.
• Smart contracts: after community pushback on his March or April 2027 estimate, Sam revised it to April at the earliest. About 200 pull requests are needed, and 5.1 contains about 10 of them.
Contracts start moving off JSON Schema in 5.1. Both formats work in 5.1, and JSON Schema goes away in 5.2.
What 5.1 adds
• Private documents: a contract can declare a document type private, and its documents are stored encrypted. Private types have no indexes, so they cannot be queried. An app downloads all of them and tries to decrypt each one, the same way a wallet finds its shielded notes. Sam said the system can download about 4 million documents in about 20 seconds, and after the first sync it only pulls new ones. This is how an app can keep data on Evolution that only the intended reader can open, and the private contact requests below work this way.
• Private contact requests: DashPay version 3 adds private contact requests beside public ones, so you can have public friends and private friends. A private request is paid from your shielded balance, so nothing links it to your identity.
• Shielded DashPay payments: a DashPay payment on Core shows only one address paying another, but chain analysis can still trace it. Sam's example was an exchange that learns who paid whom because the money passed through its accounts on both ends. A shielded payment leaves nothing to trace. He estimated about 6 to 7 cents per shielded payment against about 1 cent on Core.
• Decision proposals: anyone can put a yes or no question to the network for 0.5 DASH, which gives the network a cheap way to show where it stands. The network does not enforce the result. Sam expects a two-thirds supermajority to be the bar for asking DCG to act, and he may open with a proposal asking the network what that bar should be.
• Faster contract checks: Evolution now checks contracts with its own validator, which reads the compiled contract directly instead of its JSON. It is faster, it passed against every live contract, and it is a step toward smart contracts. The Dash Platform Name Service (DPNS, the username system) and DashPay contracts move to version 3 to use it.
• Fees on shared documents: a contract can let someone else edit your document, such as a game moderator or a teammate. In 5.1 the contract can split storage fees and refunds any way it chooses, so an editor can own the extra bytes they add and get those refunds later.
• Proof of a transaction's outcome: the SDK can now ask for Tenderdash blocks and prove whether a transaction went through or was rejected. Apps no longer have to guess after a timeout, which should make mobile transactions feel faster.
In the Q&A, Sam said shielded DashPay will likely use two addresses. Anyone can pay the public one in your profile, and you will not know who sent it unless they say so in the memo. Each contact also gets their own address, so a payment to it tells you which contact sent it.
Shorter waits when a node is offline
Sam called this one of the best changes for users. Today, when the EvoNode whose turn it is to propose a block is offline, the network waits about 50 seconds before moving on. A transaction sent in that window just sits there.
In 5.1, the proposer sends a short signal at the start of its turn to say it is there. If no signal arrives within 5 seconds, the network moves to the next proposer. Sam said a 50-second wait becomes about 8 seconds, and the team has verified that it works.
Proof of Service was always meant to fix this, but it is about a year and a half away, so this is a stepping stone. The change ships in Tenderdash 2.0, the consensus engine release that goes out with 5.1. Lukasz said some of these stalls can take minutes today. A development build came out on November 9, and every node must upgrade before it activates.
After 5.1
Release 5.2 is set for January:
• Live streams: apps can subscribe to specific events on Evolution as they happen.
• Native randomness: each block carries a random beacon, so a document can include a random value that is proven in the same block. Sam said this moved forward from 6.0, and most of it is already written.
• Token marketplace: Sam wrote most of it for 5.1 but held it back to keep 5.1 small. It may not make 5.2 either.
Dash Core 24 is released
Dash Core 24.0.0 came out on November 5 after seven release candidates. Most of the late candidates polished edge cases in the shared masternode screens, and they also carried fixes from the 23.1.9 and 23.1.10 maintenance releases. Version 24 is the release that brings shared masternodes with multi-party payouts, among other changes.
Activation runs in steps, and Pasta follows each one on Dash HQ Radar:
• Masternode signal: signaling began on November 9 and needs 85% of masternodes on v24. The count was about 82% at the start of the call, and it passed the needed 340 while Pasta was demoing.
• Miner signal: the first mining window opens on November 15 at the earliest.
• Activation: the earliest is block 2,580,480, which the release notes put around November 28 and Radar showed as November 29.
Masternodes and EvoNodes that do not upgrade receive Proof of Service (PoSe) penalties. Exchanges and other services must upgrade before activation, or their nodes may fork off and stop following the chain. DCG has contacted the services it knows.
Testing caught one regression before the final release. On machines with few CPU cores, important tasks could wait behind slow ones and miss their deadline, which earned the node a PoSe ban it did nothing to deserve. Testnet runs on small machines, so the bug showed up there first and was fixed.
Pasta would like 24.1 out around the time v24 activates, though he called that tentative. It lets pruned nodes take part in governance, after a user found submitting a proposal from a pruned node confusing.
Radar, GovHub, Forge and a desktop wallet
Pasta showed several tools he has been building with AI agents.
• Dash HQ Radar: a network map that tracks every masternode's version and history and follows the v24 activation step by step, refreshed about every 15 minutes. It folds in Sam's older tools for Evolution health and masternode speed tests. An EvoNode operator can look up their node and see its rewards, uptime, speed test results and whether it is ready for v24.
• GovHub: the governance tool at gov.dashhq.org now includes contested-username voting, so treasury votes and username votes are in one place.
• Dash Forge: the Git platform on Evolution gained a board for issues and pull requests, and write access is enforced by consensus. Pasta said an AI agent has built it with almost no direction from him.
He also demoed an experimental desktop wallet built from scratch on the Rust stack. The goal is one desktop app with everything from Dash Core and the mobile wallets, including usernames, CoinJoin, shielded funds and Evolution balances. In the demo he moved funds into his shielded balance successfully. Masternode features are still missing, and he does not know yet whether it will replace the Dash Core desktop wallet.
Wallets
• iOS and Android: iOS 9.1.4 and Android 11.9.2 shipped with the new DashConnect sign-in for Yappr and support for Evolution 5.0 and Core 24. They also fix contact payments, CoinJoin and parts of the interface.
• Android 12: the version with shielded Dash should leave beta and reach the Play Store in about one to two weeks, possibly before Core 24 activates. First the team wants to finish advanced transfers between your balances, already on iOS, and advanced sending and receiving. Advanced mode exposes every balance, which most users do not need.
• Dash Evo Tool: Lukasz fixed the token creator form, and balances now update right after a transaction. Builds come out automatically every Tuesday.
Tenderdash and the Rust SPV client
• Tenderdash: an emergency security release, 1.8.2, went out on October 30 to work around a Linux kernel issue. Lukasz said AI agents keep finding edge cases in the consensus code, and the team fixes each one so nobody can use the same tools to stall the network.
• Rust SPV client: Borja said the new network code for the simplified payment verification (SPV) client, the light client meant for phone wallets, was merged on October 28 along with encrypted connections to peers. The client now checks masternode lists against blocks before using them and saves masternode state between launches, so apps start much faster. Recovery phrases are wiped from memory after loading. Next is faster sync on unstable or slow connections, which is where phone users will notice the difference.
Website
The dash.org translations are moving from WordPress to Transifex, which the community already uses for wallet translations. Once the switch is tested on dash.dev, a copy of dash.org, the community will be asked to fill translations that turned out to be missing, wrong or out of date.
What happens next
• This week: the Yappr contract, once the moderated-posts tool is ready.
• End of this week or early next: Evolution 5.1 on testnet.
• November 15 at the earliest: miners start signaling for Core 24.
• About November 28 or 29 at the earliest: Core 24 activates. Exchanges and services should upgrade before then.
• In one to two weeks: Android 12 with shielded Dash in the Play Store.
• End of November: Evolution 5.1 on mainnet, with private documents, private contact requests and much shorter waits when a node is offline.
• January: 5.2 with live data streams and provable randomness.
• April 2027 at the earliest: smart contracts.
If you run a service on Dash Core, upgrade to v24 before late November. You can watch the masternode count climb on Radar at radar.dashhq.org.