https://img.leopedia.io/DQmPmbNGAVF74FhhoicQwLJc8vpfwpNaMctHr2Jp5ezY9Sa/image.png

Dash is integrating shielded transactions for the Evolution chain, leveraging Zcash Orchard technology to keep user transactions confidential with top-level security and fast finality.

The Evolution Chain and Privacy

In mid-2024, Dash launched Evolution, a parallel network for data applications—from adding usernames, contact lists, and encrypted metadata functionality to the main network, to enabling all manner of Web3 applications, from decentralized social media to, eventually and hopefully, much of the internet itself.

In contrast with the Bitcoin-like Core chain with an integrated CoinJoin, the Evolution chain works differently, and Dash's existing privacy features don't apply. Naturally, this means that credit transfers are fully transparent, and that isn't something that works for all users when Evolution is used at scale.

Orchard Pool

Our developers have begun integration of a shielded credit pool based on Zcash's Orchard technology. The Zcash developers have spent the last decade building and improving zero-knowledge encrypted privacy, and much of this architecture is compatible with ours.

There are several differences. First, as the Evolution chain is proof-of-stake (even though Dash as a whole is hybrid proof-of-work/proof-of-stake essentially) instead of proof-of-work like Zcash, syncing light clients can be done much more efficiently. Additionally, Dash has instant permanent transaction finality on both chains, so this means we will be able to deliver high-level privacy in seconds instead of minutes.

Shielded Tokens

After the shielded credit pool is live, we will work on shielded tokens next.

Dash already has a rich native token functionality with a wide range of features, configurations, and use cases. We will be adding shielded functionality to token transfers as well. This is similar in concept to Zcash Shielded Assets, though with Dash's more comprehensive token functionality, and through separate shielded pools for tokens rather than one unified pool. There are separate privacy, usability, and scaling trade-offs that are offered by each approach that we can cover in-depth in a future post.

What's Next?

We expect to be able to launch shielded transfers soon, naturally pending security audits and further code review. Adding a shielded pool for token transfers will follow. Then, it's up to us and our partners to make sure this critical new functionality is supported in every wallet and service possible.

We are on a mission to make money and data permissionless, secure, easy to use, and work for everyone. A big part of that is confidentiality. Join us.

Posted Using INLEO