Skip to content
Crypto.world

The Ledger

Paper Introduces Shielded Bitcoin Without Changes to Bitcoin Consensus

A Cryptology ePrint Archive preprint describes a protocol for private Bitcoin transfers that uses encrypted notes, public nullifiers and zero-knowledge proofs without changing Bitcoin consensus. The design publishes protocol data on Bitcoin while reconstructing its shielded state off-chain through deterministic replay.

Paper Introduces Shielded Bitcoin Without Changes to Bitcoin Consensus

A paper in the Cryptology ePrint Archive introduces Shielded Bitcoin, a protocol for private transfers directly on Bitcoin’s layer 1 (L1) that requires no changes to Bitcoin consensus. The preprint, “Shielded Bitcoin: Private Transfers on the Bitcoin L1,” was received by the archive on Nov. 3, 2026, and approved on Nov. 5. Its authors are Clara Shikhelman, Mikhail Komarov and Aleksei Moskvin.

The protocol holds value in encrypted notes. When notes are spent, public nullifiers mark the spends, and zero-knowledge proofs establish that the transfers are valid. The paper describes a system in which transfer details are concealed while the validity of changes to the encrypted state can still be checked publicly. “A shielded transfer does not publicly reveal its amount, sender, receiver, and place in the transfer graph, while keeping the validity of every encrypted state transition publicly verifiable,” the authors write.

Transfers use Bitcoin for publication

The design borrows from the architecture of Zcash and earlier shielded-note systems. Unlike Zcash, Shielded Bitcoin does not introduce a dedicated consensus chain. Instead, all protocol data is published on Bitcoin, and transfer validity is enforced through PIPEs v2. The preprint describes this as a metaprotocol transfer system: its protocol data is on Bitcoin, while the shielded state needed to follow transfers is maintained off-chain.

The paper specifies the transfer model and note structure, including note leaves derived from ciphertext. It also sets out nullifier rules, transaction binding and publication assumptions. Together, these elements describe how the protocol represents notes, marks spends and ties transfers to the published data. The paper’s abstract presents validity as publicly verifiable even though the amount, sender, receiver and position in the transfer graph are not publicly revealed.

Deterministic replay reconstructs shielded state

Shielded state consists of a note tree, a nullifier set and a history of block-level roots. The paper says this state is maintained entirely off-chain. It is reconstructed by replaying accepted transfers in Bitcoin order: any two correct implementations replaying the same Bitcoin history derive identical protocol state without coordination.

The preprint identifies replay semantics as part of the protocol it defines. In this design, replaying the accepted transfers provides the means to reconstruct the shielded state from Bitcoin history; the state itself is not maintained on-chain. The paper describes the resulting agreement between correct implementations as deterministic, rather than requiring them to coordinate with each other.

At the metaprotocol transfer level, the system is non-custodial. Spending authority remains with user-controlled wallet keys encrypted in a ciphertext. The paper says neither indexers nor the replay layer receive authority to spend users’ notes.

Peg-ins and peg-outs are outside the paper

Peg-ins and peg-outs are the mechanisms by which value enters and exits the shielded transfer system. The authors say those mechanisms belong to the broader system and fall outside the scope of this paper. The preprint instead defines the private-transfer model, how its data is published on Bitcoin, and how accepted transfers are replayed to reconstruct off-chain state.

Sources

  1. Original source · Preprint Cryptology ePrint Archive eprint.iacr.org

Related stories

Explore

More articles