Debate Sparks Over Shielded Bitcoin Proposal Borrowing Zcash’s Encryption Model

Three cryptographers want to give Bitcoin shielded transactions — without touching Bitcoin’s core code. The paper, authored by Clara Shikhelman, Mikhail Komarov, and Aleksei Moskvin, borrows heavily from Zcash’s encryption model and has already set off a sharp debate across developer communities.

The proposal is called Shielded Bitcoin. At its core, the idea is pretty simple: store Bitcoin values inside encrypted records called notes. When a user spends one of those notes, the transaction broadcasts a usage marker plus a zero-knowledge proof confirming the sender controls the funds and isn’t printing new coins out of thin air. Crucially, the amounts move without revealing who sent what to whom. Sender identities stay hidden. Recipient identities stay hidden. The numbers themselves stay hidden. That’s the pitch, anyway — and it’s a meaningful one. Bitcoin’s current transaction records are fully public, meaning anyone with a blockchain explorer can trace fund flows with enough patience. For payroll, business payments, or just basic personal financial privacy, that’s a real problem. Zcash solved it years ago by letting users pick between transparent and shielded transactions, and the shielded option has quietly gained serious traction.

Zcash’s Shielded Pools Hit 4.9 Million ZEC

The timing of the Shielded Bitcoin paper isn’t random. Zcash’s own shielded pools now hold about 4.9 million ZEC — roughly 29% of all coins ever issued. The network recently clocked its busiest week ever for private transactions, logging 63,000 shielded transactions in a single week. ZEC’s price responded. It surpassed $1,600, a move that works out to more than 2,300% up from the prior year. Privacy coins aren’t a niche curiosity anymore. The market is paying attention.

But here’s where the Shielded Bitcoin proposal gets technically messy. Zcash handles its zero-knowledge proofs directly on its own blockchain. The Shielded Bitcoin approach does something different — it publishes transaction data on the Bitcoin network but ships the actual verification work off to external software. That split means a Bitcoin transaction could technically confirm even if the privacy checks fail. It’s an unusual design choice, and not everyone’s comfortable with it.

Mert Mumtaz of Helius didn’t pull punches. He called the proposal a “synthetic ledger with significant tradeoffs.” The core complaint is that there’s no clear mechanism for getting regular Bitcoin into the shielded system or getting it back out. Without a clean deposit and withdrawal process, critics say users might end up holding synthetic representations of Bitcoin rather than the real thing — which matters a lot for trust and adoption.

PIPEs, Trusted Setups, and the Fee Problem

The proposal leans on a technique called PIPEs, basically a method to lock a Bitcoin signing key until specific conditions are met. The authors at [alloc] init say the full mechanics of how PIPEs would handle deposits and withdrawals are coming in a follow-up paper. Not yet published. No timeline given either.

That gap is a problem for some. Cypherpunk, a company with close ties to the Zcash ecosystem, broadly agrees that more privacy is worth pursuing — but says skipping changes at Bitcoin’s base layer comes with real costs. When privacy lives in an external layer rather than the protocol itself, the system’s security guarantees are weaker. That’s a legitimate concern, and it’s not a new one. Bitcoin’s history is full of second-layer proposals that looked elegant on paper and got complicated in practice.

More context: Researchers Propose Shielded Bitcoin for Enhanced Privacy Without Protocol Changes

There’s also the trusted setup issue. Zero-knowledge proof systems often require an initial cryptographic ceremony where participants generate secret parameters and then destroy them. If anyone in that setup keeps their secrets, they could potentially forge proofs. The Shielded Bitcoin paper hasn’t fully addressed how it handles this, and critics have flagged it as a point of vulnerability.

Fee visibility is another sticking point. Even if amounts and identities are hidden, the timing of transfers and the fees paid remain visible. That’s not nothing. Sophisticated chain analysis can sometimes infer quite a bit from timing patterns alone, even without seeing the amounts involved.

And then there’s size. Private transfers under the proposed system are estimated at around 700 virtual bytes each. Standard Bitcoin transactions run much smaller. Bigger transactions mean higher fees. Higher fees mean adoption pressure, especially for smaller payments where the cost-to-value ratio gets awkward fast.

The authors are aware of these gaps. They’ve said explicitly that a secure cryptographic setup and efficient verification for lightweight wallets are both on the to-do list. The paper frames itself as a starting point, not a finished product. That’s fair — academic cryptography often works this way, with a proof-of-concept that invites community scrutiny before the hard engineering begins.

Related: New York Lab Unveils Shielded Bitcoin for Enhanced Privacy Using Zero-Knowledge Proofs

Still, the proposal has gotten real attention. The idea of layering Zcash-style privacy onto Bitcoin without a hard fork is genuinely appealing to a segment of the community that wants better privacy but isn’t holding their breath for a protocol-level change. Whether the tradeoffs are acceptable is a different question, and that debate is very much ongoing.

No launch date has been set.

Hub: Bitcoin price, news, and analysis