Invest3 publishers3 min readPublished
Alloc Init's 56-page private Bitcoin spec leaves deposits and withdrawals for a second paper
Alloc Init published a 56-page design for Zcash-style private Bitcoin transfers that needs no change to Bitcoin's consensus rules. Deposits and withdrawals await a second paper, so who holds the pooled BTC is still an open question.
The Investor · Invest desk

What happened
- Transfers are posted to Bitcoin as data the chain records without checking, while separate indexer software verifies the zero-knowledge proofs and rebuilds the shielded state.
- Each transfer is published in an OP_RETURN output that comes to 625 vbytes when it has two inputs and two outputs, according to the paper.
- The current version uses the Groth16 proof system, whose security depends on a trusted setup ceremony having been run honestly.
- An appendix sketches an optional Trust Authority that certifies approved deposits so institutions can check a note's origins, while notes without that evidence stay valid.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- exposure Exchanges and custodians that handle entry and exit would see both public ends of a shielded coin's path, so source-of-funds checks can attach there even while the transfers in between stay hidden.
- constraint Node operators and miners can cut off ordinary relay of shielded transfers by reverting one Bitcoin Core default, with no soft fork or consensus vote required.
- decision Each regulated fund or exchange receiving shielded BTC would have to decide whether it accepts uncertified notes, a choice the protocol leaves to the venue.
The paper is precise about how little it hides. "Like Zcash and Monero, Shielded Bitcoin preserves the privacy of who paid whom and how much, not that a shielded transfer happened," it states [9]. Timing, fees and the number of inputs and outputs stay public [10]. At the boundary the promise is smaller again. According to Bankless, the authors explicitly do not claim that entering or leaving the system will be private or free from transaction linkage [8]. A coin's path has a public first step, a private middle and a public last step, and the 56 pages cover the middle [2].
The bitcoin itself sits outside the published half. Deposit 1 BTC and it leaves your spendable balance while a note worth 1 BTC appears inside the system, in Bankless's description [18]. That note is a claim on coins held under a peg that has not been specified. The peg paper will build on PIPEs v2, earlier Alloc Init research in which a valid proof recovers an encrypted Bitcoin signing key, according to the firm's website [7]. If that key controls the deposited coins, the pool is only as sound as the proof system behind it [6]. Pierre-Luc Dallaire-Demers, founder of Pauli Group, called the construction interesting but "not quantum resistant at all" [16].
The compliance appendix already puts the regulatory check at the deposit, the point where a public coin becomes a note [11]. Zcash, whose design this one borrows, now sits inside regulated wrappers: Grayscale's Zcash ETF began trading on NYSE Arca on August 25, and 21Shares listed Europe's first Zcash product on Euronext Paris and Amsterdam on September 22 [12]. None of the three reports includes a response from a regulator or an exchange to Shielded Bitcoin.
The peg paper can go a few ways. It could claim entry and exit that cannot be linked, and the boundary would then stop being a checkpoint. It could deliver withdrawals that work but leave deposits traceable, with certified deposits as the lane regulated venues use. Or the design could work while the pool stays thin. "A brand new metaprotocol starts at zero, so your first private transfer hides in a crowd of one," developer Vadim Zavodil wrote [14]. The authors concede that large deposits do not automatically create a large anonymity set, and that observers may narrow links between transfers if a few actors create most notes [15].
I think the second outcome is the likeliest, because the authors wrote the compliance lane before the exit. An unlinkable exit in the next paper would prove that wrong. Building a metaprotocol spares Alloc Init a soft-fork campaign, and chief operating officer Scott Odell described the aim as making Bitcoin "private, without changing Bitcoin" [20]. The counter-case is that the transfer layer is what the Zerocash authors wanted on Bitcoin from the start. StarkWare chief executive Eli Ben-Sasson, a Zerocash co-author, said that paper's original intent was to bring privacy to Bitcoin, though he said he had not yet read this one [17]. Zavodil's other complaint, that Zcash had already implemented much of the privacy stack, points to the peg as the new work [21].
What to watch
- The separate peg-in and peg-out paper built on PIPEs v2, and whether it claims entry and exit that cannot be linked.
- Whether Bitcoin Core node operators and miners keep or reverse the larger v30 OP_RETURN default that shielded transfers need for relay.
- Whether any exchange, custodian or Zcash fund issuer says it would accept Trust Authority-certified notes.