Shielded Bitcoin: private payments on Bitcoin without a soft fork?
A new research proposal borrows Zcash's design to hide amounts and counterparties on Bitcoin as it is today. What it promises, what it costs, and what is still missing. Presented at three conferences this autumn.
Every Bitcoin payment is public: anyone can see the amounts and follow coins from address to address. On 24 September 2026 the New York research lab [alloc] init published Shielded Bitcoin, a proposal for private transfers directly on Bitcoin, with no soft fork. Its founder, Misha Komarov, presents it at three conferences this autumn.
The idea in plain words
The design borrows from Zcash, a separate cryptocurrency known for private payments:
- Your bitcoin inside the system is held as an encrypted note. Only you can read it.
- When you spend it, the transaction publishes a zero-knowledge proof: a short piece of math that shows the payment follows the rules without revealing who paid whom or how much.
- All the data is written on Bitcoin. Bitcoin nodes do not check the private rules; separate software reads the data in block order and rebuilds the private balances. Any two correct programs get the same result.
The white paper says a shielded transfer hides the amount, sender, receiver and its place in the payment graph. Bitcoin itself does not change, and there is no separate blockchain, token or company in the middle.
What it costs
According to Komarov, a shielded transfer takes about 700 vbytes, roughly four times a typical Bitcoin payment, so fees are about four times higher. Komarov called this "not catastrophic".
What is still missing
- Getting in and out. The September paper covers transfers inside the system. How bitcoin moves into the pool and back out is left for a second paper.
- Experimental cryptography. That entry and exit relies on the team's PIPEs research and a technique called witness encryption. Komarov calls it "still pretty experimental". The lab said in September that it had cut the encrypted files the scheme needs to about 8 terabytes.
This is a research proposal, not a wallet you can use today. Do not send money to anything that claims to be "Shielded Bitcoin" until the designers publish working, reviewed software.
Why it matters
Adding privacy to Bitcoin's own rules would need a soft fork, and those are slow and hard to agree on, as the BIP-110 episode showed. Shielded Bitcoin tries to avoid that. Critics and supporters are now testing whether the assumptions hold. Komarov has urged Bitcoin users to give feedback now, saying that in about a year it would be too late to shape the design.
Where to hear it
| Local time / MSK | Event | Session |
|---|---|---|
| 13 Oct, 11:45 Atlanta / 18:45 | TABConf 8 | "Shielded Bitcoin: Private Transfers on the Bitcoin L1" |
| 5 Nov, 13:15 Amsterdam / 15:15 | Bitcoin Amsterdam | "The Insider's Look on Shielded Bitcoin" + Q&A |
| 8 Nov, 16:30 Seoul / 10:30 | Bitcoin Korea Conference | "Bringing Privacy to Bitcoin L1 via PIPEs" |
Sources
- [alloc] init: Shielded Bitcoin, Private Transfers on the Bitcoin L1 (white paper, PDF) allocinit.xyz
- bitcoin++ Insider: Shielded Bitcoin & PIPEs, 12 questions and answers insider.btcpp.dev
- Unchained: Bitcoin could get Zcash-style private transactions without a soft fork, Misha Komarov says unchainedcrypto.com
- Bitcoin.com News: Shielded Bitcoin proposal aims to bring privacy to Bitcoin L1 news.bitcoin.com
- TABConf 8 live schedule schedule.tabconf.com
- Bitcoin Amsterdam agenda bitcoin.amsterdam
- Bitcoin Korea Conference schedule, day 2 bitcoinkoreaconference.com
Times are Lugano (CEST, UTC+2) and Moscow (UTC+3). Not investment advice.
Read next
Who controls bitcoin mining? This autumn's conferences ask it in four cities
From pool protocols in Atlanta to home miners in Seoul and Bangkok and the AI energy race in Amsterdam: a plain guide to the mining debate, with every session time in local and Moscow time.
TABConf 8 in Atlanta: election timestamps, quantum addresses and a Red Team panel
The technical Bitcoin conference starts on 12 October. Its schedule is built in the open on GitHub. Eight sessions worth watching, with times in Atlanta and Moscow.