A new proposal called Shielded Bitcoin is exploring whether Bitcoin can support private transfers without changing its consensus rules. Researchers Clara Shikhelman, Misha Komarov and Aleksei Moskvin published the design on September 24, describing a metaprotocol that could hide transaction amounts and the relationship between senders and recipients while using Bitcoin as the settlement layer. The proposal does not introduce a new blockchain or cryptocurrency and does not require a Bitcoin soft fork or hard fork.
How Shielded Bitcoin Would Work
The basic idea resembles the shielded pools used by Zcash. A user would move BTC into the proposed shielded system and receive an encrypted note representing the funds. That note could then be transferred privately, with zero-knowledge proofs allowing participants to demonstrate that a transaction follows the system’s rules without revealing the sender, recipient or amount publicly. The design uses Bitcoin PIPEs to handle the movement of funds into and out of the shielded environment without requiring a federation or trusted bridge operator.
The proposal takes an unusual approach to Bitcoin’s limitations. Rather than asking miners and Bitcoin nodes to understand a new privacy protocol, Shielded Bitcoin puts the additional verification logic outside Bitcoin’s consensus layer. A Bitcoin transaction can therefore carry information associated with the shielded protocol, while a separate indexer interprets that information and determines whether the associated shielded transaction is valid. Invalid shielded data could still appear in a Bitcoin block, but the Shielded Bitcoin software would ignore it rather than treating it as a valid state transition.
This means the security model is different from a conventional Bitcoin protocol upgrade. Bitcoin itself would continue validating the underlying transaction according to its existing rules, while the shielded system would use cryptographic proofs and an indexer to maintain its own state. The researchers say the system uses nullifiers to prevent the same shielded note from being spent twice, while zero-knowledge proofs demonstrate that new notes correspond to legitimate funds without exposing the private transaction details.
At the center of the design is Bitcoin PIPEs, a mechanism developed by Komarov and collaborators. PIPEs uses witness encryption to place a Bitcoin signing key behind a cryptographic condition. If the required condition is satisfied, the key can be recovered and used to produce an ordinary Bitcoin signature. Bitcoin nodes therefore do not need to directly verify the more complicated condition themselves. Bitcoin Optech previously described the approach as a way to enforce certain spending conditions without requiring consensus changes.
The proposal is consequently different from putting BTC on a conventional privacy sidechain or sending coins through a custodial mixer. The researchers describe Shielded Bitcoin as requiring no operators, bridges or federations to hold users’ bitcoin. The intended model keeps BTC tied to Bitcoin’s base layer while the additional privacy rules are handled through cryptography and software running alongside a Bitcoin node.
The Trade-Offs Behind Private Bitcoin
Privacy would not come without costs. Komarov has said a shielded transaction could be roughly four times the size of an ordinary Bitcoin transaction, with the encrypted note alone adding substantial data. That could translate into higher fees for users when Bitcoin block space is expensive. The proposal therefore introduces a technical path to greater privacy while also creating a new question around the amount of data Bitcoin users and infrastructure operators would need to process.
There are also significant engineering questions still to answer. The Shielded Bitcoin proposal is not a feature currently enforced by Bitcoin Core, and the cryptographic construction remains an active research project. Komarov’s earlier PIPEs work has involved substantial computational and storage requirements, with the team working to reduce those requirements as the design moves toward something more practical.
Another important distinction is that Bitcoin miners would not determine whether shielded transactions are valid under the proposed system. The shielded protocol’s indexers would perform that role. This could allow experimentation without changing Bitcoin’s consensus rules, but it also means users would need software capable of interpreting and verifying the additional protocol data rather than relying solely on ordinary Bitcoin validation.
The proposal also attempts to preserve self-custody. Users would not need to hand their BTC to a company operating a privacy pool, according to the design. Funds could enter and leave through the PIPEs-based mechanism, while the cryptographic construction is intended to prevent an intermediary from becoming the entity that controls the underlying bitcoin.
The broader significance is that Shielded Bitcoin adds another example of developers trying to expand Bitcoin’s functionality without modifying consensus. PIPEs has previously been explored for covenant-like spending conditions and other applications, and the new proposal applies the same general approach to private transfers. Bitcoin’s conservative base layer therefore remains unchanged while researchers experiment with additional functionality around it.
For Bitcoin users, the proposal could eventually offer a new way to transact without exposing the same level of financial information currently visible on the public ledger. Businesses, institutions and individuals could potentially transfer BTC without publicly revealing the amount and direct transaction relationship. But those benefits remain theoretical until the cryptography, implementation, storage requirements, security assumptions and practical user experience are tested further.
Shielded Bitcoin is therefore better viewed as an early-stage privacy proposal than an imminent Bitcoin upgrade. Its core proposition is straightforward: keep Bitcoin’s consensus rules intact while using zero-knowledge proofs, encrypted notes, witness encryption and PIPEs to build a private transaction layer around them. Whether that approach can become secure, efficient and widely usable remains an open research question, but the September 24 publication gives developers another concrete design to examine in the ongoing debate over Bitcoin privacy.
About The Author
