Choose your own adventure. ECC Update

Hi Zeeps,

What does it mean to be truly in control of your outcomes: to be free to choose, act, and belong on your own terms?

Self-Determination Theory (SDT) argues that humans flourish when three needs are met:

Autonomy: I choose.
Competence: I can.
Relatedness: I’m not alone.

I felt this pull as a kid flipping through Choose Your Own Adventure books. They promised choice but only within narrow, pre-written paths. I loved the optionality and the unknown. But I yearned for more options and more freedom to shape the story myself.

Soon after, I discovered something similar in video games like Kings Quest, Space Quest and, yes, Leisure Suit Larry (don’t tell my mom). There was much more to solve and explore. It felt more open and exciting, but there were severe limits to freedom.

Today’s open-world games don’t just offer options, they offer agency. They let you ignore the main quest entirely if you want. Fish. Wander. Play your way. It’s a natural evolution as it mirrors what SDT tells us: we thrive when we’re trusted to move freely in the world.

But with money? We’ve been stuck in King’s Quest. US-regulated stablecoins, KYC-heavy CEXs, and surveillance-tethered tools offer only the illusion of freedom with a handful of pre-approved paths, all monitored, all conditional. You can trade, as long as someone else approves. You can hold, until someone else freezes it.

With Zcash, we’re creating a multi-player open world engine. It’s the evolution of the game. A strong user-experience with self-custody and privacy at scale provides autonomy. The constantly evolving open source protocol that empowers everyone honors competence. And this fosters relatedness between decentralized builders, the community, and economic actors.

We’re designing and building all this outside the legacy system, not to burn down the rails of the past, but to provide a better option that more closely mirrors the nature by which we are as human beings. Zcash isn’t here to offer a few narrow pre-determined choices. In our collective game, you are the creator.

Happy journeys.

Here’s what ECC added to the map this week:

Zashi

Zashi Design

  • Adjusting Send/Receive icons on all designs in Zashi Blueprint file
  • Adjusting marketing graphics (App Store and Play Store)
  • Continued work on Cross-chain Payments designs (research into SwapKit and Near)
  • Initial Zashi landing page exploration designs
  • Learning about new products and features from Config 2025

Q&A and Dev Support

  • Release testing iOS 2.0.2
  • User Support Issues (DIscord/email)
  • Community Management
  • Socials Management
  • Supporting product research efforts

Zashi iOS

Zashi 2.0:

  • Worked mostly on 2.0.2 version with a massive list of fixes and updates
  • Released Zashi 2.0.2 :rocket:
  • Updated Tor SDK and received another batch of comments - iteration is WIP
  • Research Spike: Near 1 Click API, SwapKit, Maya, WalletConnect

Analytics Update:
Unique Installs: 7.71k
Total Downloads: 9.28k
AppStore Rating: 4.9*

Zashi Android

  • Investigating user reported issues
  • UI tweaks and improvements for Zashi 2.0.2 in progress
  • Working on the Tor tx submission implementation and resolving issues
  • Started looking into Near 1ClickAPI documentation

Analytics Update:
Total Install Base: 3.77k
Total Installs (incl. Open Beta): 18.3k
PlayStore Rating: 4.509*

Zcash Core

  • The results of polling on funding are in. Our conclusion is that they support inserting an NU6.1 in the timeline. We are clear on what needs to be done spec- and implementation-wise, in collaboration with ZF.
  • librustzcash and SDKs: Tor reliability improvements, backports of librustzcash crate stack for zcashd.
  • Zallet: Added OpenRPC support, fixed seed fingerprint hex byte order, working on z_sendmany.
  • Continued reworking of ZeWIF code.
  • Research and auditing: Experiments with use of Lean for expressing security properties of circuits and proof systems, reviewed the Namada airdrop protocol.

That’s all for this week.

Immersed in the game,

Onward.

15 Likes

I’ve noticed that the numbers for zashi iOS are slowly growing, but on the android side (the most popular OS) the numbers are frozen. Are they using Zingo?

1 Like

Could be. Also onboarded someone via F-Droid this week - don’t have any of those numbers.

4 Likes

is this where the idea to build a one-time disbursement lockbox thing is covered?
isnt a one-time patch silly given that some of us already are disappointed in how there is so much energy getting sunk into one off polling debates cohort creations coin votes, all of these initiatives that take away from building Zcash and marketing the project…
doing a dev fund debate on a yearly basis is already too much and now is the idea to update the lockbox distributor on a yearly basis too?
are we really supposed to believe that the NU6 then NU7 distributors are going to be the end state? or is it actually just a cold truth that this project is likely to be reinventing the lockbox distributor on a perpetual basis?? and yes i can see a debate for constant upgrades we dont necessarily go the path like bitcoin (ossified)

Bumping this for the community sake…

As far as i could see, nobody ever voted in favor of a One-Year patch job LockBox distribution implementation…

Can anyone prove this wrong?

Nope.

What was voted for was the Community and Coinholder Funding Model. Quoting its specification section:

Zcash Community Grants

A funding stream will be established for Zcash Community Grants […] will start on expiry of the existing FS_FPF_ZCG funding stream, and last for a further 1,260,000 blocks (approximately 3 years), ending at Zcash’s 3rd halving.

Coinholder-Controlled Fund

A pool of multisig-controlled funds, seeded from the existing contents of the ZIP 1015 Deferred Dev Fund Lockbox and supplemented with a funding stream […] for the same time period as the Zcash Community Grants stream, forms a new Coinholder-Controlled Fund. The mechanisms for the creation and management of this fund are described by the Deferred Dev Fund Lockbox Disbursement proposal. This proposal sets […] the stream_end_height parameter to Mainnet block height 4406400, equal to that of the Zcash Community Grants stream so that both streams end at Zcash’s 3rd halving.

That clearly covers the remaining three years following the current 1-year lockbox period before the next halving, not a single year.

The Deferred Dev Fund Lockbox Disbursement ZIP referenced above is where the lockbox disbursement mechanism is being worked out. We (the various engineers who do Zcash protocol design) have been working out the details of that mechanism, such that it only needs to deployed once and then it can be used for any in-protocol dev fund disbursement going forward (again, not just for a single year).

The full lockbox disbursement mechanism we are designing will require a transaction format change, and so that will end up in the same v6 format that will be deployed in NU7 alongside ZSAs. But because Question 2 of the votes also said to prioritise the dev fund work ahead of NU7, it means that we can’t completely block the dev fund work on the v6 tx format existing. That, combined with this line from the Requirements section of the C&C Model:

  • The funds in the Deferred Dev Fund Lockbox will be usable immediately on activation of this ZIP.

is what motivates NU 6.1 with the “one-time disbursement” in the Deferred Dev Fund Lockbox Disbursement ZIP: it’s a simple consensus rule change that can be deployed in both zcashd and Zebra relatively quickly. That enables any initial grants that coinholders vote on to start being actioned as soon as NU6.1 activates, while in parallel the full lockbox disbursement mechanism can be deployed as part of NU7.

5 Likes

Thanks strad,
so if i am reading this correct…

we’ve now signed up for a new 3 year devfund, where the teams quickly build a ~simple one-time lockbox distributor into the upcoming NU

then in the following NU there is a more advanced lockbox distributor getting built and shipped

then after that (speculatively) there would be a new devfund debate and subsequent debates to further enhance the lockbox distributor (?)