Zcash community outlined a wrapped-ZEC route into Ethereum DeFi

On October 13, 2019, CoinDesk reported that Josh Swihart, then vice president of marketing and business development at Electric Coin Company, said the Zcash community intended to develop a wrapped version of ZEC for use on Ethereum. Swihart described a six-month development horizon and an ambition to make Zcash usable in lending, decentralized autonomous organizations and other decentralized-finance applications.

The development mattered because it framed interoperability as a route to utility for an asset whose distinctive privacy features were not natively available inside Ethereum applications. It also showed how Ethereum’s emerging financial application layer was beginning to pull outside assets toward its smart-contract environment.

What was actually proposed

A wrapped asset is a representation of a coin from one blockchain on another blockchain. For wrapped ZEC, some mechanism would have needed to account for native ZEC and issue a corresponding Ethereum token. That representation could then interact with Ethereum contracts, wallets and decentralized exchanges.

The October 13 report did not establish that such a mechanism had launched, passed a security audit or settled on a custody and redemption design. It also did not demonstrate that Zcash’s shielded-address privacy would automatically transfer to the Ethereum representation. Swihart’s broader goal was eventually to make shielded Zcash functionality usable by smart contracts, but that was a research objective rather than a delivered capability.

An earlier interview published on April 16, 2019, had already shown that the idea was under consideration. In that interview, Swihart discussed a sidechain-based wrapped ZEC concept that could broaden ZEC’s use on decentralized exchanges. The October account therefore represented a more specific public development horizon, not the first appearance of the interoperability idea.

Technical work preceded the announcement

Primary technical records show that Zcash-Ethereum interoperability was more than a marketing abstraction. ConsenSys’s Project Alchemy repository described ZRelay, a Zcash simplified-payment-verification client for the Ethereum Virtual Machine, and included Solidity implementations related to Zcash’s proof-of-work verification.

Separately, researchers Antoine Rondelet and Michal Zajac published the ZETH paper on April 1, 2019. It proposed adapting Zerocash-style private transfers to Ethereum without changing Ethereum’s base layer. The accompanying implementation explicitly described itself as an inefficient, unaudited proof of concept that was not intended to hold real value on public networks.

Those records support technical feasibility research, but they should not be conflated with the exact wrapped-token product Swihart discussed. A relay, a privacy protocol and a custodial or decentralized asset bridge solve related but different problems. Each introduces distinct assumptions about reserves, validators, proof verification, contract security and redemption.

Why the distinction mattered

Ethereum’s application layer offered potential distribution for ZEC, while Zcash research offered privacy techniques that Ethereum developers were actively studying. Yet a token bridge would create additional trust and security boundaries. Users would need evidence that every represented token was backed and redeemable, and applications would need to understand whether transfers remained public or gained meaningful privacy.

No verified price, return or trading-volume claim is necessary to establish the significance of the October 13 development. The record supports an ecosystem strategy and research direction, not a causal claim about ZEC or ETH market performance.

Later context

Later evidence confirms that the direction eventually produced live representations, although that outcome was not knowable on October 13, 2019. In a November 18, 2020 recap, Electric Coin Company identified RenZEC and WZEC as Ethereum tokens backed one-for-one by ZEC. That later milestone does not retroactively turn the 2019 proposal into a completed bridge; it shows that multiple implementations subsequently pursued the interoperability thesis.