Hi Zeeps,
Time to get real. ECC needs you to make a decision.
I resigned from ECC in 2023 to call for change. I argued that those changes included killing the direct development funding model, dissolving the trademark agreement, cross-ecosystem collaboration, building a strong UX for ZEC including a wallet with good UX and hardware support, and driving partnerships that expand the reach of ZEC.
When the Bootstrap board of directors (ECC parent org) hired me back as the CEO, I committed to doing these things, along with rebooting ECC’s culture, to help drive Zcash forward. For the world to have “unstoppable money,” we must win. And these were foundational pieces for a winning path forward.
With the support and dedication of an incredibly talented team at ECC, we executed on many of these things over the last year. In the best interest of a thriving Zcash (but not necessarily ECC’s financial interests), we worked with the community to kill the direct funding model, dissolved the trademark agreement, delivered Zashi and hardware support, and built coalitions with other communities. We opened up ECC’s culture, and we delivered. We’re now in a new era for Zcash, and it is still rapidly evolving.
Now that we’ve accomplished these foundational changes, we face a critical funding decision that will determine ECC’s future and the future of Zcash.
We have much more to do to deliver a complete vertically integrated stack for Zcash that scales, people love, and delivers multi-generational freedom through the world’s most secure and private protocol and tooling. For a more detailed breakdown of ECC’s vision and planned initiatives, check out this update: Onward in 2025 - ECCUpdate and current roadmap.
It’s time to decide if you believe in and want to continue supporting our work.
The following is our current funding position:
As you can see, our funding will run out this year. We were at two years of funding just a month ago, but the recent price drop reduced our runway by over a year. If the market remains as it is, ECC remains as it is, and we don’t receive funding, we’ll be out of money before the end of this year. From the outset, we decided to align ourselves with the interests of ZEC holders by minimizing our ZEC sales as much as possible and choosing to accelerate delivery rather than hold funds for self-preservation.
In the coming weeks, we will ask you to make decisions. It’s in your hands.
Decision 1: Do you want the lockbox to continue to receive funds beyond November 2025?
Decision 2: Do you want to open the lockbox in 2025 so ECC can apply for funding?
Decision 3: Which of the proposals will be adopted for how funds will be allocated?
Decision 4: Do you want to fund the grants we apply for?
The first two decisions must be made soon so we can plan accordingly. The third and fourth decisions are only materially relevant if you want to continue to fund our work.
Please be aware that implementing the means to distribute funds in 2025 could impact NU7 timelines. This doesn’t mean it would, but it is a risk you should consider. Changes to ECC operations could also impact NU7 timelines, as we will not be fully funded to continue as-is.
I have surfaced two proposals that we are writing up into ZIPs. Other ideas have been floated, and I welcome others to also codify them into ZIPs for polling. I would like to start polling right after ZconIV in early March.
I advocate for the Community + Coin Holder Funding Model, which aligns funding and coin holder economic incentives but allows a veto for implementing undesirable changes. I find arguments like this compelling. It seems to have good support here and from those of you who reached out to me directly. But it’s what you say in the polls that will matter.
It’s in your hands, Zeeps. So What’cha Want?
Here’s what we delivered this week:
Zashi (@Andrea)
Zashi Design (Pablo)
- Onboarding Redesign:
- Continued revisions for Seed Phrase Backup, Restore and Create Wallet flows
- App Home Screen (Empty State and Seed Phrase Backup banner)
- Adhoc stakeholder and engineering edits and improvements
- Adjustments to Advanced Settings and Tax Data Export designs
Q&A and Dev Support (@decentralistdan)
- Testing iOS & Android internal builds
- Tested FOSS Android build (F-droid) - QR scanning, & Keystone scanning
- User Support: Discord, X, & Email
- Zashi Website planning
- Zashi Release Comms
- Zashi Socials & Content Creations
Zashi iOS (@Lukas)
- Released 1.3.3 with fixes, optimizations and improvements around Keystone & Reset of Zashi
- Investigated Seed Backup options for iOS, see here
- local vs. remote storage, availability, cross-device vs. cross-platform syncs, cons & pros
- 3rd party options like 1password, etc.
- Participated in interviewing Core Team candidate
- Prepared per account user metadata data storage, waiting on encryption
- Bug troubleshooting:
- missing sapling params for the Keystone transactions
- crashes of the BGTask
- Implemented Keystone UI/UX improvements for canceling and rejecting a transaction + added a new confirmation step
- WIP: Near Intents research spike, stay tuned
Analytics Update:
Unique Installs: 6.39k
Total Downloads: 7.58k
AppStore Rating: 4.9*
Zashi Android (Milan)
- Added FOSS build environment for F-droid
- Added mechanism to remove and override non-open source libraries
- Removed non-open-source libraries for F-droid (FOSS build only)
- Working with @Yasser on GitHub releases which will allow us to distribute the .apk file directly
- Implemented Keystone UI/UX improvements for canceling and rejecting a transaction + added a new confirmation step
- WIP: F-droid publishing and build - encountering some issues
Analytics Update:
Total Install Base: 3.49k
Total Installs (incl. Open Beta): 14.4k
PlayStore Rating: 4.477*
Zcash Core (@nuttycom)
- The core team did a lot of specification work this week, including ZIP editing for NU7 and an update to ZIP 32 to replace the “Arbitrary Key Derivation” spec with “Registered Child Key Derivation” which will be used in the encryption of wallet metadata. This standard will be used in a future release of the Keystone Zashi firmware to enable the encryption of wallet metadata for a Keystone-based account, without relying on any keys that can’t be recovered from the Keystone seed.
- @str4d set up comprehensive CI infrastructure for the Zallet codebase & fixed some outstanding CI issues in the light client FFI repository.
- Transparent gap limit handling code is now functionally complete.
- Str4d migrated the Android and Swift SDKs to the latest versions of the Rust crates in preparation for the next Zashi release. As part of this, important new capabilities have been added:
- Support for PCZT pruning to reduce the bandwidth necessary for communication between the wallet and the Keystone device & to allow transactions with more inputs and outputs to be created with Keystone. Also, a bug that caused an error in creating proofs when constructing transactions via PCZT due to missing proving parameters has been fixed.
- Support for lightwalletd transaction submission and retrieval to be performed over TOR. This helps to fix a longstanding privacy risk for users of mobile wallets.
- Other features required for UI improvements (better representation for shielding transactions.)
- Kris led a community walkthrough of the librustzcash crate stack.
- Str4d finished up some long-running work on the equihash crate, which unblocks the ZF team for adding internal (testnet) miner functionality to Zebrad.
- Current in-progress work includes implementation of the Registered Child Key Derivation protocol in the Rust crates, and fixing a longstanding note commitment tree corruption bug.
Other
Product Marketing: @peacemonger completed the ZURE and ZAC surveys and initial user interviews for Zashi Vault. These efforts yielded strong insights. More on that in the coming weeks. Oh, and a community-wide survey is coming out next week. We hope to hear from you!
We’re actively interviewing for a Strategic Marketing Manager and making good progress.
Dan has been coordinating with the ZF on ZconVI, and supporting comms, including the new DEX provided by NEAR.
The Bootstrap met for our quarterly meeting and reviewed financials and plans.
@aquietinvestor, @_jon, and I began regular meetings to plan for the launch of ZSAs into the market. The primary focus is collaboration to promote ZSAs to potential issuers. We also met with Tether, thanks to an introduction from another Zeep. While a bit of a long shot, we’re still pursuing a path.
I drafted, got input on, and posted the Community + Coin Holder Funding model.
That’s all for this week.
Keeping it real.
Onward.