CoinYQ Dossier

Zama used its privacy machine to sell the token that funds it

Before its public token auction, Zama had already launched the protocol on Ethereum. It used that machinery to hide bids in its January 2026 sale, then opened ZAMA claims and trading on February 2. The harder experiment began afterward: whether real demand for verification and decryption can burn enough fees to justify a network that continually mints operator rewards.

A cryptography company spent five years removing one decryption step

Rand Hindi and Pascal Paillier founded Zama in 2020 around fully homomorphic encryption. The promise sounds small but changes the trust model: calculate on encrypted data without first turning it back into readable text. Zama spent its early years turning that mathematics into TFHE-rs, Concrete and FHEVM tools, then raised a $73 million Series A in March 2024 to push the technology toward practical infrastructure.

On June 25, 2025, the company announced a $57 million Series B and a protocol meant to sit beside public chains rather than replace them. Ethereum would keep ordering transactions. Host contracts would record ciphertext handles and access rules; coprocessors would perform encrypted arithmetic; a Gateway and distributed key service would coordinate authorized decryption. The architectural choice preserved Ethereum composability but introduced a new operator network behind each hidden value.

Thirteen parties created a key none was meant to know

Between November 25 and 28, 2025, 13 organizations jointly generated the mainnet encryption key and secret shares. Zama reported that no participant learned the complete private key. The protocol went live on Ethereum on December 31, moving FHEVM from a developer testnet into a production environment.

That ceremony reveals what “private on a public chain” means here. Ethereum can expose an encrypted handle and the contract’s access decisions without exposing plaintext. Coprocessors calculate over ciphertext, while a threshold of KMS parties answers an authorized decryption request. Privacy therefore depends on cryptography, correct application permissions and the honesty/availability assumptions of the operator set—not on hiding that a transaction happened.

The first large demonstration was Zama’s own sale

From January 21 to 24, Zama sold ZAMA through a sealed-bid Dutch auction implemented on its mainnet protocol. Bids stayed encrypted during the sale. Zama later reported $118 million committed and called the auction its first production application with real value; that number describes submitted commitments, not cash earned as protocol fees.

Claims opened at noon UTC on February 2 and exchange trading one hour later. Genesis created 11 billion tokens, with 20% circulating at TGE. The sale made the technical claim tangible before the token became freely traded: FHE protected price discovery, and the token distributed by that auction would then pay the operators who make future confidential applications work.

Burning usage and minting security pull in opposite directions

ZAMA fees are quoted in dollars and converted through an oracle, insulating application costs from the token’s unit price. The protocol charges for checking encrypted-input proofs, decrypting ciphertext and bridging encrypted values; applications or relayers may sponsor the payment. Every collected token is burned.

Security spending runs the other way. Operator rewards are newly minted at an initial 5% annual rate, split between KMS and coprocessor roles and weighted by the square root of stake. By block 25,909,938, Ethereum total supply had risen to about 11.286 billion. That observed increase is the economic test in miniature: fee use contracts supply while security rewards expand it, and governance may change the reward rate.

Delegators choose operators; operators choose protocol rules

A ZAMA holder can delegate to an operator pool, but only elected operators and their delegators earn rewards. The holder receives a pool share and accepts its commission and unstaking rules. Protocol voting is different: elected operators have equal votes regardless of stake. The Aragon DAO governs Ethereum and already links to the Gateway through LayerZero. BSC, HyperEVM and Solana currently use dedicated local multisigs; broader DAO linkage is planned. These are fee-payment and delegation functions; the litepaper does not establish a claim on Zama company profits, and the initial issuance rate is not a promised delegator yield.

The Ethereum token cannot be upgraded, yet immutability does not remove administration. Its DAO address holds the default admin role, two staking contracts can mint, and a pauser wrapper can stop minting; all were active in the September review and minting was unpaused. Operators can also approve upgrades to protocol proxies, change fees and rewards, or block addresses under documented thresholds. ZAMA therefore secures a service whose future is decided by a small operating federation, even as anyone can buy or delegate the token.

A live protocol still has an adoption problem to solve

By May 2026, Zama described the full Ethereum stack, confidential wrappers, portfolio, staking and bridges as live and integrable, while labeling its new SDK beta. ZAMA could travel to BSC, Solana, HyperEVM/HyperCore and the Gateway, but token travel is not the same as FHE execution on every destination. Current documentation still requires a chain-by-chain deployment check.

The original research wager has reached production; its commercial feedback loop is only beginning. If confidential applications create repeated verification and decryption demand, burns connect ZAMA to real use. If activity stays concentrated in launches and incentives, minted security rewards dominate. The next chapter is therefore written less by another cryptographic benchmark than by the ordinary applications willing to pay to keep one field secret.

How the project changed

  1. 2020
    Zama begins as an FHE research company

    Rand Hindi and Pascal Paillier found the company years before a protocol token exists.

  2. 2024-03-07
    A $73 million round funds practical FHE

    The Series A backs the plan to make encrypted computation easier and faster for blockchain and AI.

  3. 2025-06-25
    The confidentiality protocol is unveiled

    Zama pairs its Series B with an operator network that adds FHE to existing public chains.

  4. 2025-11-28
    Thirteen parties complete the mainnet key ceremony

    The distributed generation ends without one participant holding the full secret key, according to Zama.

  5. 2025-12-31
    Ethereum mainnet goes live

    The production confidentiality layer precedes both the auction and transferable token launch.

  6. 2026-01-21 to 2026-01-24
    Zama sells ZAMA with encrypted bids

    Its own FHE protocol runs the sealed-bid auction that becomes the first real-value production application.

  7. 2026-02-02
    Claims and exchange trading begin

    Claims open at 12:00 UTC and trading at 13:00 UTC, turning the protocol fee asset into a transferable market token.

  8. 2026-05-07
    Wrappers, portfolio and bridges reach users

    Zama reports the Ethereum stack and applications live while its simplified SDK remains beta.

Evidence and primary sources

Last evidence review: 2026-09-05

What is Zama?

Zama is an open-source cryptography company founded in 2020 and the builder of a confidentiality layer for existing public chains. Its production protocol has operated on Ethereum mainnet since December 31, 2025. It is not a new general-purpose L1: host-chain contracts keep encrypted handles and access rules, while coprocessors, a Gateway rollup and a threshold key-management network perform and authorize work.

ZAMA is the protocol’s public ERC-20 fee and staking asset on Ethereum at 0xA12C…f4f3. LayerZero adapters expose representations on BNB Smart Chain, HyperEVM, the Gateway and Solana. Those token bridges do not prove that confidential-contract execution is live on every destination. Ethereum mainnet and Sepolia are the documented live builder environments; the May 2026 SDK release was still labeled beta.

What problem does Zama solve?

Public smart contracts make balances and state visible. Zama’s answer is fully homomorphic encryption: contracts can request computation over ciphertext without first exposing the underlying value. The host chain records permissions and symbolic results, while specialized off-chain operators do the expensive cryptography.

Encryption does not decide who deserves access. Each application grants use and decryption permissions through an access-control list, and delegated decryption can authorize a service provider, custodian or regulator. The protocol therefore supplies confidential computation; an application still chooses its disclosure and compliance policy.

How does Zama work?

A confidential contract emits an operation instead of evaluating FHE arithmetic inside Ethereum. Coprocessors validate encrypted inputs and calculate ciphertext results. The dedicated Arbitrum Gateway coordinates attestations and decryption requests, and 13 KMS parties hold shares of the key so no single node should possess it. The 2025 key ceremony generated mainnet material jointly across those 13 parties.

Fees are denominated in dollars but settled in ZAMA after a Gateway oracle converts the amount. The protocol charges for proof verification, decryption and ciphertext bridging; a user, application or relayer can pay, so an end user need not personally hold ZAMA. All protocol fees are burned. Staking rewards are newly minted at an initial 5% annual rate and can change through operator governance. At Ethereum block 25,909,938, totalSupply was 11,285,903,453.995201608326824533 ZAMA, already above the 11 billion genesis supply.

Delegators choose an elected KMS or coprocessor pool. Only elected pools and their delegators earn protocol rewards; operators can charge up to 20% commission, and unstaking has a configurable delay initially described as seven days. Governance votes belong to operators with equal weight, regardless of stake. The primary Aragon DAO controls Ethereum and already connects to Gateway through LayerZero: a GovernanceOApp receiver passes governance messages to an AdminModule trusted by the Gateway multisig. BSC, HyperEVM and Solana currently use dedicated multisigs; broader linkage to the DAO remains planned. The token contract itself is non-upgradeable, but its DAO admin can manage roles. Two staking contracts currently hold MINTER_ROLE, a PauserSetWrapper holds MINTING_PAUSER_ROLE, and minting was not paused in the reviewed block.

Key facts

  • Rand Hindi and Pascal Paillier founded Zama in 2020; the company’s FHE libraries and research came years before ZAMA.
  • Zama announced the Confidential Blockchain Protocol on June 25, 2025; 13 parties completed its mainnet distributed-key ceremony on November 28, and the protocol went live on December 31.
  • The January 21–24, 2026 ZAMA sale used an encrypted sealed-bid Dutch auction on the production protocol. Zama reported $118 million committed; this is a company-reported bid total, not protocol revenue.
  • Claims opened at 12:00 UTC and exchange trading at 13:00 UTC on February 2, 2026. The Ethereum contract is 0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3.
  • Genesis supply was 11 billion ZAMA. Twenty percent circulated at TGE: 12% public sale, 6% campaigns and 2% liquidity. Treasury 20%, Growth 10%, Team 20%, VCs 20% and Angels 10% follow two- or four-year schedules; Team, VC and Angel allocations have one-year cliffs.
  • ZAMA follows burn-and-mint economics. Fees are burned and operator rewards are minted at an initially 5% annual rate; the observed September 5 supply was about 11.286 billion, so 11 billion is not a permanent cap.
  • Staking is live on Ethereum for public ZAMA. Any holder may delegate, but rewards accrue only through elected operators; operator commission is capped at 20%.
  • Protocol votes are cast by operators with equal weight, not by every token holder according to balance. The Aragon DAO governs Ethereum and already links to the Gateway through LayerZero. BSC, HyperEVM and Solana currently use dedicated local multisigs; broader DAO linkage is planned.
  • The immutable Ethereum token code separates admin, minter and minting-pauser roles. Live calls found the DAO admin, two staking minters and a pauser wrapper active; minting was unpaused.
  • Current token bridges reach BSC, Solana, HyperEVM/HyperCore and the Gateway. This cross-chain token availability is separate from FHE host-chain deployment.

Official links

Categories

Related coins

Frequently asked questions

Did Zama launch for the first time in February 2026?

No. The company dates to 2020, the protocol was announced in June 2025 and Ethereum mainnet went live on December 31, 2025. February 2 was the transferable ZAMA claim and exchange-trading launch.

Does every FHE calculation require the user to hold ZAMA?

No. Fees are paid in ZAMA, but the application or a relayer can pay them. The charged operations are input-proof verification, decryption and ciphertext bridging; the litepaper says FHE computation itself is not separately charged.

Can every ZAMA holder vote on protocol upgrades?

The current governance design gives equal votes to elected operators. Token holders can delegate to operator pools and may earn rewards through elected pools, but balance alone does not give a direct protocol vote.

Is the supply capped at 11 billion?

No. Eleven billion was the genesis supply. Protocol fees burn ZAMA and staking contracts mint rewards at a governance-adjustable rate initially set to 5% annually. The observed supply on September 5 was about 11.286 billion.

Does a bridged ZAMA token mean Zama FHE is live on that chain?

Not necessarily. ZAMA uses LayerZero representations on several chains. That proves token transport, not confidential-contract support. Current documentation should be checked for each host chain before treating bridge availability as protocol deployment.

External trackers

Choose a tracking site for Zama: