{"id":13694,"date":"2026-09-25T02:24:58","date_gmt":"2026-09-25T02:24:58","guid":{"rendered":"https:\/\/cryptonews.uk.com\/?p=13694"},"modified":"2026-09-25T02:24:58","modified_gmt":"2026-09-25T02:24:58","slug":"bitcoin-researchers-target-privacy-coins-with-zcash-style-shielded-transfers","status":"publish","type":"post","link":"https:\/\/cryptonews.uk.com\/?p=13694","title":{"rendered":"Bitcoin researchers target privacy coins with Zcash-style shielded transfers"},"content":{"rendered":"

<\/p>\n

\n

Bitcoin researchers have proposed a system for private transfers directly on the network without requiring a soft fork or changes to its consensus rules.<\/p>\n

The Sept. 24\u00a0paper from [[alloc] init] researchers Clara Shikhelman, Mikhail Komarov, and Aleksei Moskvin introduces Shielded Bitcoin, a metaprotocol designed to conceal transaction amounts, senders, recipients, and links between transfers while publishing its protocol data through Bitcoin mainnet.<\/p>\n

The design adapts techniques pioneered by Zcash, including encrypted notes, public nullifiers and zero-knowledge proofs, but does not introduce a separate blockchain. Bitcoin instead provides the publication and ordering layer from which participants reconstruct the private transaction state.<\/p>\n

That would extend Bitcoin privacy beyond existing techniques such as CoinJoin, PayJoin and Silent Payments, which can complicate transaction tracing or reduce address reuse but leave amounts and other transaction details visible.<\/p>\n

Bitcoin would carry the transactions without validating the privacy layer<\/h2>\n

The proposal avoids waiting for a Bitcoin upgrade by moving the privacy logic above the network\u2019s consensus rules.<\/p>\n

Users would hold BTC-denominated value as encrypted notes. When funds are transferred, the sender would publish an envelope containing encrypted outputs, public nullifiers marking previously held notes as spent, and a zero-knowledge proof establishing ownership and value conservation.<\/p>\n

The amount being transferred and the identities of the counterparties would remain hidden.<\/p>\n

Bitcoin miners and nodes would not validate the shielded state themselves. Instead, implementations following the Shielded Bitcoin rules would scan BTC blocks and replay accepted transfer envelopes in their recorded order, producing a common note tree and spent-note set.<\/p>\n

Bitcoin would therefore provide the timestamped transaction history and ordering needed to reconstruct the system, while the metaprotocol would handle encrypted balances and transfer verification.<\/p>\n

The current implementation profile uses OP_RETURN to publish the encrypted transfer data, though the researchers leave open the possibility of other publication methods.<\/p>\n

That architecture differs from Zcash, where the network\u2019s consensus rules enforce shielded transaction validity directly. Shielded Bitcoin would keep BTC consensus untouched while deriving a separate private state from data anchored to the chain.<\/p>\n

Some metadata would remain visible. Transaction timing, fees, input and output counts, and characteristics of the Bitcoin transaction carrying the encrypted data could still give observers clues.<\/p>\n

The paper also includes viewing capabilities that could allow users to selectively disclose transaction information without surrendering control of their funds, creating a route for auditing or compliance where required.<\/p>\n