Crypto · updated 1h ago · 2 min read
Researchers Publish Shielded Bitcoin Draft With Zcash-Style Privacy Without Changing Bitcoin Rules
Alloc Init researchers propose Shielded Bitcoin to add Zcash-style privacy without Bitcoin rule changes. The approach uses encrypted notes and zero-knowledge proofs to hide amounts, senders, recipients.
Whether the main emphasis is compliance-ready promise or integration gaps.
8 of 10 outlets skipped it: regulatory/auditing via selective viewing capabilities.
12outlets compared
Same story, two versions
tap a side to read it in full
CryptoSlate
“The key gap [[alloc] init] still needs a secure peg to move BTC into and out of the shielded system.”Read the original ↗
OneSafe sells the future as compliance-friendly, while CryptoSlate and CoinDesk stress the missing peg and integration risks.
A Zcash-style blueprint
Researchers at [[alloc] init] published a 56-page draft titled “Shielded Bitcoin: Private Transfers on the Bitcoin L1” on September 24, 2026, proposing a metaprotocol that keeps Bitcoin’s consensus rules untouched. Clara Shikhelman, Mikhail Komarov and Aleksei Moskvin wrote that the scheme aims for sender, recipient, transfer amount and the link to earlier payments to stay hidden while avoiding a soft fork. The draft describes encrypted notes, public nullifiers and zero-knowledge proofs as its core building blocks, and it says every transfer carries such a proof.
The paper states that there is no implementation yet, with “no implementation, no users and no pool holding any actual funds,” and it frames the work as “a paper, not a product.” The proposal also specifies Groth16 as its proof system, while the draft notes that Groth16 requires a trusted setup ceremony.
How it would work
The proposal pins Bitcoin as “a neutral publication and ordering layer,” while separate software called indexers would verify the privacy logic by scanning Bitcoin blocks and replaying accepted transfer envelopes. The draft says a shielded transfer would publish encrypted data on Bitcoin while leaving the checks to separate software that “any participant either runs themselves or trusts someone else to run.” The system uses nullifiers to mark notes as spent without revealing which note was used, and it relies on zero-knowledge proofs to establish that the sender is entitled and that input sums match output sums.
The draft also quantifies the fee impact, with one description putting a shielded transfer at 625 virtual bytes for a transfer with two inputs and two outputs. The draft’s architecture also leaves a critical gap, because it does not explain how ordinary BTC would enter or be released, reserving those mechanisms for a separate paper using PIPEs.
Critics, costs, and next steps
Mert Mumtaz, cofounder of Helius and a Zcash proponent, described the proposal as “a synthetic ledger with significant tradeoffs,” and he pointed to “a trusted setup” and “no fee anonymization.” Mumtaz also wrote that there was “no in-protocol mechanism for getting actual BTC in or out (which means you are holding synthetics),” while the paper itself says the specification does not explain deposit and withdrawal flows. Cypherpunk welcomed the research but said it did not perceive it as competition for the existing network, writing “Privacy works best when built into the base layer.”
The proposal’s own authors acknowledge that transfer timing and fee payments remain visible, and it also flags that privacy depends on crowds, with a brand new metaprotocol starting at zero in the view of developer Vadim Zavodil. As the draft remains a blueprint with no launch date, the next steps center on completing the peg-in and peg-out boundary and addressing the trusted setup and fee visibility concerns raised alongside the higher transaction size.