Proposal “OrchardPay“ (Active)Back

Title:OrchardPay = ZK and Data Contracts combined!
Owner:OrchardPayTL
Monthly amount: 1 DASH (29 USD)
Completed payments: no payments occurred yet (24 month remaining)
Payment start/end: 2026-08-06 / 2028-07-21 (added on 2026-07-29)
Final voting deadline: in 1 month
Votes: 0 Yes / 0 No / 0 Abstain
Will be funded: No. This proposal needs additional 306 Yes votes to become funded.
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many 8410614191c3f2df69a224a1c34ebc745288700515fdece6ad3764bfc1c987fe funding yes

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

Proposal description

OrchardPay is here!

Design write-ups:

Code: github.com/orchardpaytl/orchardpay

You will be able to find the flatpak release here ^^, when it's ready!

What is OrchardPay?
  • An anonymous contact and E2EE messaging and payment dapp, built on Dash Platform, combining zero-knowledge shielded transactions with Platform data contracts.
  • No public social graph — DashPay's contact-request documents are public and queryable, so anyone can see who has requested contact with whom. OrchardPay's contactAnchor documents carry no public identifying or connecting data; the only way to find one is to already know its document ID, delivered privately in a shielded on-chain transaction memo that only the intended recipient can decrypt.
  • One channel, unlimited uses — DashPay's contact-request documents exist just to exchange an extended public key. OrchardPay's contactAnchor and encryptedMessage documents form a general private channel: messages, payment requests, and other structured content all share the exact same encrypted shape, so nobody watching Platform can tell them apart. New message types can be added later without touching the data contract.
  • Payments carry real meaning — sending a payment performs an actual shielded value transfer, correlated to its message through an on-chain memo, not just a record that a payment happened. Direct sends are also possible, so anyone can send to a name without having to do a contact request exchange.

Roadmap
  1. Wait for the next DET (Dash Evo Tool) release and pull in the freshest upstream updates.
  2. Release a testnet flatpak so anyone can try OrchardPay.
  3. After a couple of weeks of testnet feedback, ship the Mainnet release.


Quantum Worries
  • Yes, a future quantum computer could eventually crack today's shielded addresses.
  • Once quantum-resistant addresses and signing are ready, they're meant to be a straight drop-in replacement for the current setup.
  • There will be a testnet period for the quantum-resistant version first.
  • But this won't be a smooth "migration" — it will be a clean break. A brand new OrchardPay version, and users start fresh: new wallet, new contacts, everything.
  • Why not just wait for quantum resistance instead of shipping now? Because Dash's own history shows this kind of upgrade can take years to design, and real quantum computers capable of breaking things could be many years beyond that.
  • OrchardPay is here now, and it's real. No reason to sit on the sidelines waiting for a threat that's still years away.


Next Possibilities
  • OrchardParty — turning OrchardPay contacts into private group chats.
  • Forking the Android and iOS DashPay-style apps to bring OrchardPay to mobile.

This post is mostly an advertisement for OrchardPay, but I also wanted to measure the sentiment of people about OrchardPay. So the 1 Dash is the bar I use to measure people's interest in OrchardPay. If it ever passes, the 1 Dash will go toward feeding the AI. The entire project is vibe coded.

I don't know if we need to wait for developers. We just need to start building!



Find me on DashDiscord as OrchardPayTL.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment