Bitcoin Could Soon Get Zcash-Style ‘Shielded’ Privacy Without Changing Its Rules
Researchers Clara Shikhelman, Mikhail Komarov and Aleksei Moskvin of cryptography firm alloc init published a proposal on Thursday that would let Bitcoin users send private, Zcash‑style shielded transactions without altering Bitcoin’s consensus rules.
Key Takeaways
- Shielded Bitcoin adopts Zcash’s encrypted payment design, storing notes on the Bitcoin chain.
- Verification of shielded transfers is delegated to external software, allowing a Bitcoin transaction to confirm even if the private payment fails its own checks.
- The proposal lacks a mechanism for depositing or withdrawing real BTC, leaving deposits as synthetics.
- Critics point to a required trusted setup, visible fee payments, and the absence of an in‑protocol deposit/withdraw system.
- Zcash’s shielded pool currently holds 4.9 million ZEC (≈29 % of supply) and has seen a 2,300 % YTD rally, underscoring the demand for privacy.
| Metric | Value | Why it matters |
|---|---|---|
| Researchers | Clara Shikhelman, Mikhail Komarov, Aleksei Moskvin | Credible cryptographers from alloc init |
| Company | alloc init | Cryptography research firm |
| Zcash Shielded Pool | 4.9 million ZEC (≈29 % of supply) | Demonstrates existing demand for privacy |
| Weekly Shielded Txns (last week) | 63,000 | Highest since 2022, 4th‑highest ever |
| Weekly Transfer Volume (Zcash) | $23 billion | Largest weekly total since 2021 |
| Private Transfer Size (Shielded Bitcoin) | ~700 virtual bytes | Higher than standard BTC txns (100‑200 bytes) |
What Is Shielded Bitcoin?
Shielded Bitcoin is a conceptual framework that would let users create encrypted “notes” representing BTC value. Each note would be spent by publishing a marker and a zero‑knowledge proof that the spender owns the note and has not created new funds, while keeping the amount, sender, and recipient hidden.
How It Works – Technical Overview
Unlike Zcash, where the blockchain verifies proofs internally, Shielded Bitcoin would embed the encrypted transfer data directly into a Bitcoin transaction. Verification would then be performed by external software that anyone could run. Consequently, a Bitcoin transaction could be confirmed even if the embedded shielded payment fails its own validity checks.
Current Status and Gaps
The 56‑page specification does not describe how ordinary BTC would be locked into the shielded system or released back to the user. The authors plan to address deposits and withdrawals in a separate paper using PIPEs, a technique that locks a Bitcoin signing key until specified conditions are met. Until then, the system only guarantees control over transfers inside the shielded layer and explicitly excludes deposit/withdraw mechanisms.
Community Reactions and Critiques
Mert Mumtaz, cofounder of Helius and a Zcash advocate, called the proposal a “synthetic ledger with significant tradeoffs,” citing the need for a trusted setup, visible fee payments, and the lack of an in‑protocol deposit/withdraw mechanism. He noted that the design would keep users holding synthetics rather than real BTC.
“I respect that people are working on this and taking notes from Zcash finally,” he wrote, adding that the proposal would require years of additional research and development.
Cypherpunk, a Zcash holder and miner, welcomed the research but stressed that privacy is most effective when built into the base layer. They highlighted the proposal’s advantage of not requiring Bitcoin rule changes, while also noting it as a drawback.
Comparison with Zcash and Ethereum Proposals
Zcash offers both transparent and shielded payments; its shielded pool currently holds 4.9 million ZEC, representing about 29 % of issued coins and worth roughly $7.8 billion after a recent rally. Zcash’s shielded transactions peaked at 63,000 last week, with a transfer volume of $23 billion. Ethereum is reviewing a shared private pool that would enable private transfers of ether and tokens, citing payroll, treasury management, and donations as key use cases.
Why It Matters
Privacy remains a practical concern as developers aim to use cryptocurrencies for everyday payments, payroll, and business transactions. A Bitcoin‑native shielded layer could broaden adoption by protecting user identities and transaction amounts without requiring a hard fork or consensus change. However, the lack of deposit/withdraw mechanisms and the need for a trusted setup may limit immediate usability.
Frequently Asked Questions
Who proposed Shielded Bitcoin?
Clara Shikhelman, Mikhail Komarov, and Aleksei Moskvin of alloc init.
When was the proposal published?
Thursday, the date of the paper’s release.
How does it differ from Zcash?
It stores encrypted transfers on Bitcoin and relies on external software for verification, whereas Zcash verifies proofs on its own blockchain.
What are the main criticisms?
The need for a trusted setup, visible fee payments, and the absence of an in‑protocol deposit/withdraw mechanism.
Is there a deposit/withdraw mechanism yet?
No. The authors plan to address it in a separate paper using PIPEs.
Bottom Line
Shielded Bitcoin offers a promising route to add Zcash‑style privacy to Bitcoin without a hard fork, but its current lack of deposit/withdraw functionality and reliance on a trusted setup mean it remains a theoretical concept. Traders and developers should monitor the forthcoming PIPEs paper for practical deployment details.
Crypto is highly volatile and risky. This is not financial advice — do your own research.
Reporting based on: original source.
Comments
Post a Comment