ZEC's 291% Rally Rests on a White Paper Its Own Endorser Hasn't Read

The single largest print on the ZEC tape this cycle was a $10.68 million short liquidation. By the time that order cleared, price had already run from $1,200 — Eli Ben-Sasson's September 25 target — to $1,545.89. That is a 29% overshoot of his own call, on a chart with no new protocol revenue, no new issuance schedule, and no new usage metric to point at. What happened next is the part I keep returning to. Whales began messaging Ben-Sasson directly, asking what was driving the move. His public answer was that he did not know. He asked his own followers for theories. Founders talk their books constantly. It is the cheapest marketing channel in the industry. Watching one admit the order flow had detached from anything he could name is rarer, and far more informative, than any price target he could have handed out. The real signal was never $5,000. It was the silence underneath it. Zcash has run as a proof-of-work network since 2016. For most of that life it carried two liabilities: a shielded pool that never grew past a fraction of supply, and a "privacy coin" label that keeps it on the wrong side of exchange listing committees. Over the past 90 days ZEC is up 291%, and it now sits at roughly ninth by market cap. A single Zcash spot fund absorbed $98.2 million in one week — the largest inflow among the 14 crypto products tracked in that data set. Ledger's desktop application added a shielded-balance view. Those are the only two items in the entire story that touch usage or capital rather than sentiment. The technical headline is a proposal. On September 24, a research group called Alloc Init — authors Misha Komarov, Aleksei Moskvin, and Clara Shikhelma — published a white paper titled Shielded Bitcoin. The claim is aggressive: shielded transfers on Bitcoin L1, amounts and addresses hidden, implemented without a soft fork, without BitVM, and without any change to Bitcoin consensus. The stated machinery is familiar to anyone who has read Zerocash: zero-knowledge proofs, nullifiers to prevent double-spends, encrypted notes carrying value, and — the load-bearing part — witness encryption, a primitive that lets a party encrypt a message whose decryption key is not yet known. Ben-Sasson endorsed it. He is a co-author of the Zerocash paper, a co-founder of StarkWare, and one of the founding scientists of Zcash. Real name, real track record. He posted his support the same day the paper dropped. He also stated, plainly, that he had not yet read it. There is a structural reason to flag the alignment. Ben-Sasson sits on both sides of this: Zcash founding scientist and StarkWare co-founder. STARK technology is exactly the class of proof a Bitcoin-L1 privacy layer would need to lean on. An endorsement of ZK tooling landing on Bitcoin is, whether intended or not, an endorsement of technical territory StarkWare occupies. I am not accusing him of anything. I am noting that the same person's incentive and his stated belief point in the same direction, and a reader should weight them accordingly. Start with the claim, because the claim is where the trouble is. "No soft fork, no BitVM, no consensus change" reads like a list of advantages. It is actually a description of the trust model. If Shielded Bitcoin does not touch consensus, then miners and full nodes do not validate shielded transfers. Ordering, availability, and final settlement of double-spend disputes have to live somewhere outside the consensus layer. That makes this far closer to a client-side-validated protocol layered on top of Bitcoin, plus a public commitment, than to native confidential transactions. The anonymity set is whatever subset of users voluntarily installs the tool. In 2018 I spent 120 hours manually auditing early MakerDAO CDP contracts in Solidity v0.4.24, tracing variable dependencies until I found an integer overflow in the price-oracle feed path that could have drained collateral during a flash crash. The lesson I keep from that winter applies here: the security of a system lives in the layer that adjudicates state, not in the layer that advertises the feature. A privacy guarantee no validator enforces is a privacy guarantee with a soft edge. The dependency is where I would push hardest. Witness encryption — encrypting to a recipient whose key is unknown, decryptable only once some puzzle resolves — is a beautiful theoretical object with essentially no efficient practical instantiation. Wiring it in as a base dependency, not an optional enhancement, is a feasibility red flag, not a design detail. Add to that: no testnet, no code, no audit. The authors have no public delivery history I could locate. The proposal itself has not been read by the person endorsing it. That means there is currently no peer-review signal at all, only directional agreement from a respected name. The proposal has no repository activity worth tracking yet. Until there is a testnet, a commit log, or a third-party audit, the correct classification is concept, not protocol. I have a rule for this: if I cannot read the code, I cannot price the risk, and if I cannot price the risk, the position size is zero or the trade is purely momentum. Shielded Bitcoin sits on the momentum side of that line right now. Two more items the write-ups skipped. "PIPEs" appears as a building-block tool with no definition attached; you cannot evaluate a primitive that is not defined, so it stays in the unknown column. And nullifiers only mean something if the set they nullify against is large. A nullifier over a thin anonymity set is a privacy illusion — it proves you spent something without revealing which, while the set itself narrows the candidate to a handful of wallets. On Bitcoin, that set is bounded by how many people opt in. Zcash has lived this exact failure mode for years: optional privacy produces a thin shielded pool, and the transparent pool stays the default. Shielded Bitcoin removes even the chain-level force Zcash retains. The fund data deserves a second look. $98.2 million in a single week, top of a 14-product list, is real. But a weekly flow is a snapshot, not a trend. The relevant question is not whether one week printed big; it is whether the flow repeats, and whether the composition is sticky. Redemption pressure travels the same rails as inflow. I would want four consecutive weeks before treating that number as structural rather than event-driven. Here is the number that should anchor everything. ZEC is up 291% in 90 days, market cap rank ninth, with a $10.68 million single-liquidation print. Every piece of "user" evidence in the story is financial-side — fund flows, leverage, liquidation — and none of it is on-chain. No shielded-pool ratio. No shielded-transaction count. No holder distribution. The value capture for a proof-of-work privacy asset is a monetary premium plus a privacy premium; there is no cash flow to discount, so there is no fundamental anchor — only narrative and regulation. When the founder of the asset cannot explain the move and the only hard number is a fund inflow that lasted one week, you are not analyzing a protocol. You are analyzing a reflexive bid. One dimension the story never touches is regulation, and for a privacy asset that is a first-order variable, not a footnote. Privacy coins have spent two years under channel pressure: EU AML rules tightening around anonymous assets, historical delistings in Japan and Korea, exchange-level monitoring of ZEC pairs. That the flow arrived through a regulated spot-fund wrapper makes the compliance story look settled. It does the opposite. A product holding a privacy asset inside a securities structure is exposed on two sides — to the privacy restrictions and to the fund-registration regime. The inflow is a liability as much as an asset, because the same channel that delivered $98.2 million in can transmit redemption pressure out at the same speed. Now the part that gets buried. Ben-Sasson's stated original goal was to bring privacy to Bitcoin. Read that again inside the context of what he just endorsed. If Shielded Bitcoin works, Bitcoin holders get privacy without leaving Bitcoin — no migration cost, no new chain, no exchange listing risk, no "privacy coin" label. Zcash's entire differentiated claim, that it is the place you go for shielded value, gets compressed. The market read the endorsement as bullish ZEC. The engineering read is competitive substitute. Those two readings cannot both be right, and the second one falls out of the actual dependency graph. This is not a Zcash-only problem. The entire independent privacy-chain category is being eaten from the edges. Silent Payments on Bitcoin, BTC L2 confidential-transfer work, and now a direct L1 shielded proposal all attack the same premise: that you must leave Bitcoin to get privacy. Zcash retains one advantage — a mature, audited, multi-year shielded implementation. That is a real moat. But a moat does not grow when the castle gets cheaper to bypass. The timing reinforces the suspicion. Proposal published September 24. Endorsement tweeted September 24. Same day, synchronized, on a chart that was already vertical. I do not say this to allege coordination; I say it because late-cycle rallies routinely dress a technical event in narrative clothing and let price borrow its credibility. The media cycle did the rest. The headline kept "his ZEC year-end target is still in play" and quietly dropped the load-bearing disclaimer — that this was his personal bet and not investment advice. That is not a small edit. It converts a discretionary position statement into an implied institutional signal, and most readers never see the original. Strip the narrative and you have three drivers. A one-week fund inflow, sustainable only if it repeats. A short squeeze, which is definitionally one-time. A founder price target, which is self-decaying — the first call landing at $1,200 buys authority that the $5,000 call spends. Of the three, only the first is trackable, and the story itself concedes the point in its final line: whether demand holds through December likely decides whether ZEC approaches the target. That sentence is the most honest analysis in the whole piece. Everything above it is noise dressed as signal. Remove every price target from your framework and treat it as a sentiment indicator, never an anchor. Track exactly three things: weekly net inflow to the Zcash spot fund, because it is the only quantifiable support and two consecutive red weeks flip the tape; the shielded-pool ratio, because it is the first genuine usage metric that would confirm or kill the privacy thesis; and derivatives open interest plus funding, because a $10.68 million forced close means leverage is now the primary amplifier and it works in both directions with equal violence. Trust the audit, verify the stack, ignore the hype. Code does not reach consensus by being praised. The market rewards those who read the source code — and right now there is no code to read.