A trio of cryptographers has published a 56-page proposal for encrypting bitcoin payments using a design borrowed from Zcash, arguing that Bitcoin’s privacy problem can be addressed without a hard fork, a soft fork, or any change to the network’s consensus rules. The paper, called “Shielded Bitcoin,” was released Thursday by Clara Shikhelman, Mikhail Komarov and Aleksei Moskvin of the cryptography firm [alloc] init, and it lands at a moment when interest in privacy-preserving crypto is unusually high.
The timing is not incidental. Zcash’s shielded pools held 4.9 million ZEC as of Friday, up 14% since July 30 and equal to roughly 29% of all issued ZEC — a stash worth about $7.8 billion after the token’s rally. Shielded transfer volume hit around 63,000 transactions last week, the busiest since 2022 and the fourth-highest ever recorded, while total weekly transfer volume topped $23 billion, the largest since 2021. ZEC itself has gained more than 2,300% over the past year, crossing $1,000 in early September and touching $1,600 on Wednesday.
How the design works
Bitcoin’s blockchain is, by design, a public ledger: every transaction, address and amount is visible to anyone who cares to look. Zcash was built to fix that from the ground up, offering both transparent transactions and “shielded” ones that encrypt the sender, receiver and amount using zero-knowledge proofs — cryptographic techniques that let a network confirm a transaction is valid without revealing its contents.
Shielded Bitcoin tries to import that idea into Bitcoin without asking Bitcoin’s own software to change. Under the proposal, encrypted transfer data would still be published on the Bitcoin blockchain itself, but the actual verification of those private payments — checking that the notes and proofs are valid — would be handled by separate, external software rather than by Bitcoin’s consensus nodes. In practice, a private transfer would look to the base Bitcoin network like an ordinary, if somewhat larger, transaction; the heavy cryptographic lifting happens off to the side.
That size difference is one of the proposal’s clearest trade-offs. The researchers estimate a private transfer would run to roughly 700 virtual bytes, against 100 to 200 virtual bytes for a typical bitcoin transaction today. At an equivalent fee rate, that implies miner fees for a shielded transfer running about four times higher than for a standard one — a real cost users would weigh against the privacy gained.
What it means, and what’s missing
The idea of bolting privacy onto Bitcoin is not new. Zerocoin, proposed in 2013, was an earlier attempt to add anonymity to Bitcoin transactions. The related Zerocash research never made it into Bitcoin but instead became the technical foundation for Zcash’s launch as its own independent cryptocurrency in 2016. Shielded Bitcoin’s authors are explicitly working the other side of that fork in the road: rather than spinning up a new chain, they want to bring Zcash-grade privacy back to Bitcoin itself, using the same case-for-consensus-neutrality that has made soft forks so contentious in Bitcoin’s history.
Avoiding any change to consensus rules is also the proposal’s biggest limitation, according to critics including Helius cofounder Mert Mumtaz and the Zcash-holding firm Cypherpunk. As it stands, Shielded Bitcoin has no in-protocol mechanism for actually moving real BTC into or out of the shielded system — deposits and withdrawals would depend on a technique called PIPEs that the authors say will be detailed in a future paper, not this one. The design also requires a trusted cryptographic setup, a step where participants must trust that certain secret parameters were destroyed after being generated, and it does nothing to hide transaction fees or timing, both of which can still leak information about who is transacting with whom. The authors acknowledge each of these gaps and list further verification tooling as future work rather than something ready today.
None of that makes the proposal irrelevant. It arrives alongside a parallel push at Ethereum, where developers are separately reviewing a proposal for a shared private transfer pool, suggesting privacy engineering is becoming a live design question across multiple major chains at once — even as regulators sharpen their focus elsewhere, as seen in the stalled US crypto legislation now sitting with regulators and in the Federal Reserve’s new capital and redemption rules for stablecoin issuers. For Bitcoin specifically, the proposal is a reminder that the network’s famously conservative approach to changing its own rules has not stopped researchers from hunting for privacy fixes that work around, rather than through, that rulebook.
What comes next
No launch date has been set, and the gap between a 56-page specification and working software that people actually use remains wide. Readers should watch for the promised follow-up paper on PIPEs, which would need to solve the deposit-and-withdrawal problem before Shielded Bitcoin could handle real funds; for independent audits of the trusted setup process; and for any signal that Bitcoin Core developers or major wallet providers take an interest in building the external verification tooling the design depends on. It is also worth tracking whether the current surge in Zcash’s shielded-pool activity proves durable or fades once the current wave of attention passes, since much of the enthusiasm behind this proposal is tied to that broader revival of interest in on-chain privacy.
Source: CoinDesk
This content is for informational purposes only and does not constitute financial or investment advice.
Create a free account to comment and earn rewards.
Create account Log in