galaxy.comarticle‘Shielded Bitcoin
Galaxy Research newsletter piece covering "Shielded Bitcoin," a paper by [[alloc] init] researchers Clara Shikhelman, Mikhail Komarov, and Aleksei Moskvin proposing a Zcash-style shielded pool (encrypted notes, public nullifiers, zero-knowledge proofs) run as a Bitcoin L1 metaprotocol via OP_RETURN envelopes, with peg-in/peg-out deliberately left to a future "PIPEs v2" paper. The article's security-relevant angle flags that novel ZK circuits need battle-testing — citing Zcash's own Orchard Pool soundness bug that survived professional audits for four years before being fixed in the Ironwood upgrade — and that bridge/peg mechanisms (the likely weak point) have historically been the most exploited component in crypto, naming Ronin, Wormhole, Nomad, and KelpDAO. It also notes a growing AI-driven deanonymization threat to transparent blockchains, citing ETH Zurich/Anthropic research showing LLM agents can re-identify pseudonymous users from profile data alone.
What it is
Shielded Bitcoin, published by [[alloc] init] researchers (Clara Shikhelman, Mikhail Komarov, Aleksei Moskvin) as of this writing (the piece reports it was published "Thursday" before the Oct. 9 article date). The design's key technical dependency, not in the existing summary: it relies on Bitcoin Core v30's loosened OP_RETURN relay policy — the exact change Bitcoin maximalists fought against last year. Without that relay-policy shift, the envelopes this protocol depends on wouldn't propagate normally through the network.
How it works
Value is held as encrypted notes; transfers are OP_RETURN data envelopes carrying encrypted notes for recipients plus a proof that the sender owns the inputs and didn't inflate supply. Indexers watch Bitcoin, replay every envelope in block order, and discard invalid ones. Unlike the closest prior proposal, Shielded CSV, all data lives onchain — so a wallet can recover funds from its seed alone, with no off-chain data dependency.
Preconditions / Affected
The design presupposes Bitcoin Core v30's relay policy for OP_RETURN (larger/looser data relay) to function as intended on mainnet. Peg-in/peg-out — the mechanism that actually locks and releases real BTC — is explicitly out of scope and deferred to a future "PIPEs v2" paper; the authors do not claim entry/exit will be trustless or censorship-resistant.
Caveats
The piece frames this directly as a competitive shot at the Zcash "private complement to Bitcoin" thesis, noted in the context of ZEC's run (~$1,600, ~$26B market cap, +90% in 30 days, +2,500% over the past year at time of writing) and recent moves like Grayscale's ZCSH ETF (>$250M net inflows since Aug. 25) and Citrea's acquisition of the private wallet Crest the day before this paper's release. None of that market context is a technical claim about the protocol itself, but it explains why the paper is drawing attention now and why maximalist critics are inclined to seize on its unresolved peg design as a point against the "privacy needs Bitcoin" narrative.
Organisations named here
- Nomad
- Orchard Pool
- PIPEs
- Ronin
- Wormhole
Technologies named here
- Bitcoin L1
- Shielded Bitcoin
- Bitcoin Core
- Indexers
- Flock Safety platform
- Zcash
- ZODL
- Zcash Orchard pool
- Shielded CSV
- Crest
- Grayscale Zcash ETF
- Citrea
- NEAR
- Flock Safety license-plate cameras
- Bitcoin
- KelpDAO
- Ironwood
Techniques named here
- Shielded pool design
- OP_RETURN data envelopes
- Onchain address clustering
- AI-assisted deanonymization
- AI-enabled surveillance pattern analysis
Related in Blockchain
blog.thorchain.orgwriteupTHORChain Exploit Report #2 — GG20 root-cause disclosure
protos.comarticleBlack Thursday revisited: MakerDAO keeper exploited for $500K
.jpg)
aikido.devwriteupGraphalgo campaign spreads to Terraform providers and Go Modules
sundaytimes.lkarticle