Electric Coin Co. (ECC), the firm which created Zcash (ZEC) and develops the Zashi wallet, has unveiled its roadmap for the fourth quarter of 2025, amid a surge in the privacy-oriented token's shielded supply and price.
ECC's roadmap lists four key priorities: adding ephemeral addresses for every swap to ZEC using the multichain NEAR Intents protocol, generating a new transparent address after a user's current address receives funds, allowing Keystone hardware wallet users to resync their devices, and supporting Pay-to-Script-Hash (P2SH) multisig wallets in Keystone. ECC plans to use one such multisig wallet to secure the management of Zcash developer funds.
"This quarter, ECC’s focus is on reducing technical debt, improving privacy and usability for Zashi users, and ensuring smooth dev fund management," the firm's announcement states. "As market conditions and other factors impact ECC revenue (positively or negatively), we will re-tune our approach, refocus our efforts, and step on the gas."
These moves build on Zashi’s recent decentralized off-ramp for shielded ZEC, from Aug. 28, and the decentralized on-ramp (“Swaps”) release from Oct. 1, after which ECC temporarily disabled the Coinbase on-ramp over a new session-token requirement it viewed as privacy-unfriendly. The planned Q4 features effectively harden that flow by minimizing address reuse around swaps and simplifying hardware-signer ops.
The roadmap comes as Zcash's shielded supply and price have ballooned in recent months. The token currently trades at around $420, according to The Block's Zcash Price page, up from just $50 in mid-September. The token's market capitalization recently flipped that of competing privacy coin Monero.
The supply of shielded tokens in Zcash's Orchard privacy protocol, the most recent version of Zcash's protocol (though it maintains backwards compatibility with the earlier Sprout and Sapling versions), recently surpassed 4.1 million tokens, according to ZecHub data. The bulk of the growth in supply since mid-September has been in the Orchard protocol.
