Bitcoin

Zcash

<h2 id="header-0">Bitcoin News</h2>
Cryptography researchers at Alloc Init have published a paper describing Shielded Bitcoin, a protocol designed to hide the amount, sender, and recipient of a transfer while keeping the transaction on Bitcoin's (BTC) base layer.&nbsp;
The <a target="_blank" rel="noopener noreferrer nofollow" href="https://www.allocinit.xyz/uploads/shielded-bitcoin.pdf">paper</a>, dated Sept. 24, is authored by Clara Shikhelman, Mikhail Komarov and Aleksei Moskvin.
<img src="https://academy-public.coinmarketcap.com/optimized-uploads/36b8753aaebd499cb1bc98c7be2d49e7.png">
The design does not require any change to Bitcoin's consensus rules. Instead, value is represented as encrypted notes, and spending a note publishes a public marker called a nullifier rather than revealing the note itself. A<a target="_blank" rel="noopener noreferrer nofollow" href="https://coinmarketcap.com/academy/glossary/zero-knowledge-proof"> zero-knowledge proof</a> attached to each transfer verifies that the sender owns the funds and that no value was created or destroyed, without disclosing who is involved or how much is being sent.
<h2 id="header-1">No Separate Blockchain Required</h2>
Shielded Bitcoin borrows its core structure from Zcash (<a target="_blank" rel="noopener noreferrer nofollow" href="https://coinmarketcap.com/currencies/zcash/">ZEC</a>), which uses a similar system of encrypted notes and nullifiers. The paper describes one key departure from that model: Zcash runs its own blockchain to track shielded balances, while Shielded Bitcoin has no chain of its own. Transfer data is published directly to Bitcoin, and software called an indexer rebuilds the private balance records by replaying every accepted transfer in the order <a target="_blank" rel="noopener noreferrer nofollow" href="https://coinmarketcap.com/currencies/bitcoin/">Bitcoin </a>recorded them.
Because that replay process is deterministic, any two indexers processing the same Bitcoin history are expected to arrive at an identical set of records without needing to communicate with each other. The paper states that spending authority stays with the user's own wallet keys throughout this process, and that neither the software reading the blockchain nor the replay layer itself is able to move a user's funds.
Related Article: <a target="_blank" rel="noopener noreferrer nofollow" href="https://coinmarketcap.com/academy/article/bitcoin-price-holds-84k-bond-sell-off">Bitcoin Price Holds $84K Despite Bond Sell-Off, Eyes $97K</a>&nbsp;
The paper positions Shielded Bitcoin against several existing approaches to Bitcoin privacy. Existing tools such as CoinJoin and Silent Payments make it harder to trace ownership through pattern analysis, but transaction amounts remain visible on the public ledger under those methods. A separate proposal called Shielded CSV pursues a similar goal to the new paper but requires users to store their own transaction history locally, meaning that history could become unrecoverable if a user loses that data. Shielded Bitcoin's authors argue their design avoids this by publishing everything needed to rebuild the private state directly on Bitcoin itself.
<h2 id="header-2">Publication Costs and Open Questions</h2>
The paper discloses specific technical trade-offs rather than presenting the design as finished. Each transfer's cryptographic proof gets published inside a Bitcoin transaction using a data field called OP_RETURN, and proof size varies depending on which underlying proof system is used, ranging from roughly 160 to 192 bytes according to figures cited in the paper. The authors note this publication method adds a fee cost to every private transfer, on top of Bitcoin's standard network fees.
Several design choices remain unresolved. The paper states that a method allowing a user's wallet to verify its own transaction history without downloading and replaying the entire Bitcoin blockchain has not yet been solved and is listed as future work. The authors also have not settled on a standard number of inputs and outputs for a typical transfer, noting that the choice affects how easily individual transfers can be distinguished from one another by outside observers.
The paper also outlines an optional feature allowing institutions to verify, using a separate zero-knowledge proof, that funds they receive originated from an approved source and passed only through certified recipients, without revealing the underlying transfer history to anyone outside that verification. The authors describe this compliance layer as strictly opt-in, stating that notes without this additional verification remain valid under the base Shielded Bitcoin protocol.
The paper describes peg-in and peg-out, the mechanisms by which funds would enter and exit the shielded system, as outside its scope, and says that functionality is intended to be built using a separate protocol called Bitcoin PIPEs v2, which the same research group has also published.

Researchers Unveil Zcash-Style Privacy Plan for Bitcoin

Table of Contents

Other articles published on Sep 27, 2026

Bitwise Sets NEAR Price Target at $155 for 2030

Saylor Calls for Bitcoin Rights at DC Policy Summit

Bitcoin ETFs Erase 2026 Losses as Treasury Buybacks Fuel Rally

Join our free newsletter for daily crypto updates!