Sapling: using any market from your Zcash wallet, one month in

Hi everyone,

Let me introduce myself first. I’m igor (@igor_zs1 on X), I founded Sapling Technologies, an independent company building on Zcash, and I write a lot of the code myself. For the past few months, I’ve been working full time on one thing: getting more people to actually use Zcash.

I care about Zcash for a simple reason: privacy only protects people if they use it, and today most people never get the chance to. Zcash has the strongest privacy in crypto, but most ZEC just sits. My work is about giving people real reasons to hold and use it.

Quick note so nobody gets confused: when I say Sapling, I mean our project, not the Sapling shielded pool. The name is a nod to Zcash.

Why I’m posting

A month ago Ben from Raydium posted here about the new ZEC holders on Solana, and the discussion that followed was one of the best things I’ve seen on this forum. We’ve been working on the same question from the other side every day, so I want to share what we built, our data, and what we’ve learned.

What Sapling does

Your Zcash wallet is all you need. You can trade markets across chains (Solana & Robinhood currently, more coming soon) and launch coins on them, all with ZEC, without ever opening another wallet. You pay in ZEC, you get paid in ZEC, and rewards come back to you in ZEC. A share of every trade goes out in ZEC, and whoever launches a coin chooses where: to its holders, to themselves, or to the Zcash Foundation.

What’s live on the Zcash side

  • Zcash-native accounts. Sign in with Zodl or Noir by scanning a QR code. No other wallet, no other chain’s wallet needed.
  • Native ZEC in and out. Deposit and withdraw real ZEC straight from your Zcash wallet.
  • Shielded payouts for every account. Rewards and proceeds can land as shielded ZEC.
  • Creator fees paid straight to a Zcash wallet. Whoever launches a coin can send their fees to any Zcash address, shielded or transparent, so the money comes home to Zcash.
  • Coins that fund Zcash. Creators can route their fees to the Zcash Foundation or to any Zcash builder they want to support.
  • Shielded receipts on Zcash mainnet. Every payout gets a receipt written as a shielded Zcash note, open source.
  • Rewards anyone can verify. Every fee, split, payout and receipt is public with its signature, and holder rewards can be checked with zero trust in us.
  • Recover from your Zcash wallet. Accounts can be exported, cut off and recovered using your Zcash wallet.
  • The Sapling Terminal. Charts, limit and stop orders, one-click trades, all paid from your ZEC balance.

The numbers, since Sep 25 (all on chain, live at sapling.cash/stats)

  • 25,750 ZEC of trading volume ($33.6M)
  • 357 coins launched
  • 86.30 ZEC paid out to holders ($112K)
  • 6.07 ZEC sent to the Zcash Foundation, chosen by the people launching ($7.5K)
  • 90% of everything the protocol earns goes back out; we keep 10% (276.74 ZEC earned in total, $357.7K)

Dollar values are counted at the time each payment happened.

What we’ve open sourced for Zcash

What I learned

  1. Paying people in ZEC works better than asking them to buy it. Most people trading on Sapling would never buy ZEC on their own. But when ZEC shows up as a reward, they hold it. 86 ZEC has gone out that way, mostly to people who had never held ZEC before.

  2. The hardest step isn’t getting ZEC, it’s getting it shielded. Moving from ZEC on another chain to a shielded address still means bridges and intents front ends, and every hop loses people. This month alone, intents had a hack and a large exit stuck for weeks. As long as activity lives on other chains, privacy stays one risky step away. That’s the strongest argument I know for bringing this activity onto Zcash itself.

  3. Give people the choice and some will choose Zcash. Nobody is forced to fund the Zcash Foundation. Creators pick where their share goes, and 6.07 ZEC has gone to the Foundation anyway.

  4. Trust has to be checkable. Every payout has a public receipt and a verifier, so anyone can see where the ZEC went without taking our word for it.

The tradeoffs, honestly

  • The markets run on other chains today, Solana and now Robinhood Chain. The Zcash side can be shielded, but the trade itself is public like any trade there.
  • A lot of what trades is memecoins. They are risky, and I’m not going to pretend otherwise. What matters to me is that every one of those trades starts and ends in ZEC, and pays ZEC out.
  • We’ve had to fix real bugs with real users’ money in flight, and we wrote down every one of them and why it happened.

What’s next for Zcash

  • Shielded holder rewards: holder rewards paid shielded, after Zcash’s NU7 upgrade.
  • Ready for ZSAs: we’ve already issued Sapling coin twins on the ZSA testnet, so if and when ZSAs reach mainnet, Sapling coins can become native Zcash assets.
  • A way out that doesn’t need us: users can exit their coins even if Sapling disappears.
  • Collectibles that live on Zcash.
  • And the bigger goal: bringing this activity onto Zcash itself, shielded end to end. I’ll bring protocol ideas here for review when they’re ready.

Questions for people here

  • For those who have onboarded new users: what actually gets someone from holding ZEC to using shielded ZEC? What should we change on our side to push more people there?
  • Would a public, regularly updated report of this data (ZEC paid out, how much ends up shielded) be useful to the community?

Happy to answer anything, including the hard questions. Glad to finally be able to post and contribute here.

igor

4 Likes

Thanks for writing this up, igor, especially the bugs part. Most projects don’t publish that.

On your first question, from the other side of the same problem: I build a small checker for NEAR Intents swaps and a Zcash address check, and most of what people get stuck on before “shielded” is the address itself, not the wallet. The ones I see most:

  • They’re handed a transparent address (t1…) by an exchange or a deposit screen and don’t know it isn’t private. Nothing on the screen tells them.
  • They paste a unified address (u1…) into something that only pays transparent addresses, or a TEX address (tex1…) into a wallet that only sends from a shielded balance, and the send fails or goes somewhere they didn’t expect.
  • A payout lands on their transparent address while they’re watching the shielded balance, so they think it never arrived.

So the thing that helped most was saying it in plain words before they send: “from a transparent-only wallet, this works / doesn’t” and “from a shielded wallet, this works / doesn’t”, plus the one next step. If Sapling’s withdraw screen said which kind of address the user typed and what that means for their privacy, I think more people would pick the shielded one on their own.

On the second: yes, I’d read it. The split I’d most like to see is how much of the ZEC you pay out goes to shielded addresses versus transparent ones, and how long a ZEC deposit or withdrawal takes end to end (typical and worst). Your point about every hop losing people is the right one, and those two numbers would show where.

If one of your users ever has a ZEC deposit or withdrawal that looks stuck on the intents side, I’m happy to look at it with you here and say which step it’s waiting on.

thanks @Anirudh-712 , this is really useful, and it matches what we see.

The address type is the part we underestimated. Our withdraw screen accepts t1, u1 and shielded addresses, but it doesn’t tell people what they just pasted or what it means for their privacy. Saying it in plain words before they send is a small change with a real effect, so we’re going to add it.

And thanks, those are the right two numbers for a report: shielded vs transparent, and how long deposits and withdrawals take end to end. Noted for when we put one together.

Thanks for the offer on intents too. We’ve had a few deposits that looked stuck on that side, so I’ll take you up on it next time one comes up.

On the first: in Unpair the user never picks a pool. The ZEC leg lands shielded by design and the shield step runs on its own, so there is no choice to get wrong. If I were on your side I would make the shielded withdraw the default and transparent the thing you have to pick, not the other way round.

On addresses, one thing from our side: the u1 problem is not only what the user pastes, it is which receiver the sender picks. Maya, as far as I read mayanode, pays Sapling if present, else transparent, and refuses Orchard only. We avoid the question by handing out addresses with just the receivers we want paid: transparent plus Orchard for routes that pay transparent, Orchard only for 1Click, t1 or t3 only on the payout side. Worth knowing what the big senders do with a u1 before you label it shielded.

2 Likes

thanks @zakrad, this is really useful.

on the default: agreed, and that’s where we’ve landed too. Shielded is already the preselected option on payouts (sends to a Zcash wallet, holder payouts and claims), and transparent is the one you have to choose. One place still depends on a setting, and we’re closing that gap so shielded is the default everywhere.

on u1 and receivers: good point about Maya, and it’s the reason we don’t pass a u1 straight to a router. On the transparent route we take the u1’s transparent receiver ourselves and only hand that to the router, so the label says public. on the shielded route the router pays our own order address, and our side then pays the Orchard receiver of the user’s address, so the shielded label is only shown when we’re the ones paying Orchard. We don’t use Maya at the moment, but if we add it we’d follow your approach and hand out an address with only the receivers we want paid.

Curious how Unpair handles a user who pastes a u1 with no Orchard receiver, only Sapling and transparent. Do you refuse it, or pay the Sapling part?

1 Like

We pay the transparent one and say so before the user confirms, with a hint to paste a shielded only address if they want it straight into the pool. Sapling only, bare zs1 included, we refuse and ask for a transparent or Orchard address from the same wallet. We never pay Sapling, none of our routes can and our browser wallet has no Sapling prover.

Taking the transparent receiver yourself before the router sees the u1 is the right call, we do the same in the other direction.

Glad it helps, and good to hear you’re adding it.

In case it saves you a round of copywriting, these are roughly the lines that worked for us, one per address type:

  • t1… “Transparent address. Anyone can see this payment and the balance it lands in.”
  • u1… “Unified address. It has a shielded part, so the coins can land in a private balance.”
  • zs1… “Shielded (Sapling) address. Once the coins land, the balance isn’t public.”
  • tex1… “Transparent-only address (TEX), usually an exchange. It can only be paid from transparent funds, so a wallet that sends only from a shielded balance can’t pay it.”

The one that confused people most was the last: the address looks valid, the send just fails, and nothing says why.

And sure, whenever one looks stuck, the deposit’s transaction hash is all I need to start, here or by message.

Hey @igor_zs1 — love what Sapling’s doing (trade any market straight from your ZEC wallet). I built the other side of that flow for the NEAR hackathon: Where’s My ZEC — a small keyless tool that shows where a stuck ZEC swap went and whether you’re still inside the refund window (it reads NEAR’s bridge refund deadline; no wallet, no keys, nothing to sign). Feels complementary to what you’re doing — would love your take, and happy to make it play nicely with Sapling if that’s useful.