Shielded Bitcoin: a new privacy proposal with entry and exit still unresolved

On 24 September 2026, Clara Shikhelman, Mikhail Komarov and Alexey Moskvin of [[alloc] init] published a paper on Shielded Bitcoin. The proposal describes shielded transfers recorded on Bitcoin without changing its consensus rules. This is a research design; publication alone does not establish that an active service has been tested in widespread use. Research paper (Opens in a new tab)

What the proposal aims to hide

Value is represented in encrypted records called notes. A zero-knowledge proof is intended to allow validity checks without disclosing the amount or the connection between the parties. Public identifiers, called nullifiers, prevent reuse of the same record. Separate software reconstructs the system's state from data recorded on Bitcoin; including the data in a block does not mean Bitcoin nodes validate the system's rules. Research paper (Opens in a new tab)

For background on the distinction between storing data and interpreting it, start with the blockchain guide.

Even a shielded transfer leaves traces

The authors' explanation notes that publication timing, fees and transfer characteristics remain visible. An identified wallet repeatedly paying publication fees may create a link between actions. The described proof profile also uses Groth16 and an initial setup ceremony, whose trust assumptions form part of the security model. The authors' explanation (Opens in a new tab)

From an editorial perspective, it is therefore better to ask which information is hidden, from whom and under what conditions. The word privacy alone does not answer all those questions.

The part still requiring its own specification

The authors point to a future document detailing how BTC enters and leaves the system through PIPEs. This is a significant limitation when assessing the proposal: understanding internal transfers is not enough to assess the entire path of the money. Questions about the system's boundaries need to be examined against that specification when it becomes available. The authors' explanation (Opens in a new tab)

What to look for next

We will follow the entry and exit specification, independent technical review, and documentation of implementation and testing. These are questions for further coverage, not conditions already shown to have been met. Readers assessing a new solution should also establish how access is recovered and who holds the keys; the guide to wallets and custody explains the concepts.

Publication allows public discussion of the idea and its limitations. At this stage, an accurate headline concerns a proposal, and should not imply that every Bitcoin user has now gained a new privacy capability.