AIANALYSISPODCAST
Zama raised $150M at a $1B valuation betting that encrypting Ethereum and Solana transactions is the missing default for institutional money on shared ledgers.
Before 1995, the internet had every wire the modern web needed except one default: the one that encrypted a credit-card number before it crossed a network. Without that default, mass e-commerce was a science experiment. HTTPS turned it into a marketplace. Zama just closed a $150M raise including a $115M Series B at a $1B valuation led by Pantera. The cryptography startup bets public blockchains are stuck in the same pre-encryption moment. A public blockchain is a shared ledger anyone can read with a block explorer: every balance, every trade, every counterparty in the open.
The Paris-based company, founded by CEO Rand Hindi, is putting a four-year number on how it ends: 95% of Ethereum and Solana financial transactions, encrypted through Zama, by 2030. The live proof is a confidential USDC vault curated by Steakhouse on Morpho, where Morpho is a DeFi lending protocol and Steakhouse the vault manager. The vault is already taking deposits. The institutional stake is Apex Group's $100B T-Rex tokenization commitment running through Zama's privacy layer, independently reported as a Wall Street-targeted launch.
"Bigger than Zcash at 5% shielded," Hindi said on Podcast Alpha, conceding the size of the target and the puniness of prior attempts at the same problem. The mechanism is what separates Zama. The vault uses fully homomorphic encryption (FHE), a cryptographic scheme that lets a blockchain run computations on encrypted balances without ever decrypting them, so a block explorer can still validate the math while the numbers stay opaque. The open ledger stays open for verification; the contents are encrypted by default. That is the 1995-HTTPS shift in engineering terms, and it is the change that lets an institution use a shared public chain for a compliance workflow without giving up verifiability. In Hindi's framing, institutions no longer have to choose between a private consortium chain, a 1990s-style intranet, and a shared public chain they cannot use at all.
The bet collapses if Hindi has misidentified the binding constraint. Confidentiality is one of three reasons large asset managers have stayed off public chains. Custody and regulatory clarity are the other two, and a separate school of thought (Fireblocks, Anchorage, the compliance-first chains) argues the real problem is who holds the keys, not who can see the ledger. If that camp is right, Zama's HTTPS layer ships on time and the institutions still do not arrive. The Series B buys Zama the four-year runway to find out, and the Morpho vault is the first empirical test of whether a real allocator will park real USDC behind the encryption default rather than a permissioned wrapper. The network-effects bet is winner-take-all: if the encrypted default becomes the default, it becomes the default, and every prior privacy chain gets relegated.
The falsifiable watch is narrow. Apex Group's $100B commitment is a stated tokenization pipeline, not currently encrypted on-chain volume. The T-Rex launch is what decides whether the pipeline actually runs through Zama. The 95% target is a four-year horizon, and the next twelve months will sort the thesis from the pitch: every new institutional deployment either routes through Zama or routes around it. If Apex ships a meaningful share of its $100B book through the T-Rex privacy layer in 2027, the HTTPS analogy earns its weight. If a custody-first chain absorbs the same book first, the analogy stays an analogy, and the 95% number stays a target Hindi set for himself.