Horizen now: ZEN is no longer a security-budget coin

Horizen’s most important tokenomics fact in 2026 is blunt: ZEN stopped being the native asset that pays for its own L1 consensus. It migrated from the legacy Horizen mainchain and the EON EVM chain into an ERC-20 on Base, and “all coin transfers are now managed on Base, via ERC-20 smart contract calls,” per the migration overview.

That single move flips the economic model. Under proof-of-work, ZEN’s issuance directly underwrote mining and a large incentivized node network. After the migration, the highest-leverage “security” line item becomes operational: sequencers, RPC, indexers, bridges, proof infrastructure, plus governance and treasury controls that decide whether those services stay funded. That is a different kind of security budget. It is less automatic. It is more political.

ZEN is still marketed as the governance and utility token of the Horizen ecosystem, with a fixed maximum supply of 21 million and no ICO or pre-mined supply.

History and structural breaks that matter for tokenomics

Horizen 2.0’s own research whitepaper (v1.0) documents a key strategic pivot: due to “regulatory concerns,” the project made “a strategic decision to remove private transaction capability from Horizen’s network,” as noted in the 2.0 whitepaper.

On issuance, ZEN followed a Bitcoin-like halving rhythm on the legacy chain until late 2024. Horizen’s community communications describe the second halving at block 1,680,000 on December 12, 2024, reducing the block reward to 3.125 ZEN.

The real break came next. The migration docs state the move was “successfully completed on July 23, 2025,” migrating balances from both old chains to Base, and discontinuing both old chains.

This is where tokenomics stops being about block-by-block issuance curves and starts being about how the remaining supply is allocated, vested, and spent, and whether fee capture is real enough to replace the old issuance-funded security model. If you’re pressure-testing a model like this, it helps to anchor your analysis in token economy components rather than just supply curves.

Supply, remaining issuance, and allocations (the part that will move markets)

On Base, the official ZEN ERC-20 contract is documented as having a maximum capped supply of 21 million ZEN, consistent with the legacy cap, in the smart contract docs.

CoinGecko currently lists 21,000,000 as total and max supply, and 17,796,210 as circulating supply.

The tokenomics question, then, is not whether supply is capped. It is how the remaining not-yet-distributed supply is released, and what it is released for. The tokenomics addendum frames this as reallocating the “remaining 5M unminted $ZEN” after the Base decision, with 25% minted at migration and the remaining 75% linearly vesting over 48 months, per the tokenomics addendum.

Those allocations are the closest thing Horizen has to a modern “budget.” They are also your forward sell-pressure map.

One more supply nuance matters operationally. The migration architecture includes vault contracts that minted and distributed balances, with the ZEND backup vault handling manual claims. The smart contract documentation states that after each successful claim, the vault’s remaining balance corresponds to the “unclaimed total value at any given time.”

Unclaimed supply is not burned. It is dormant. That creates a slow-moving overhang that can re-enter circulation if user claim activity re-accelerates during future market cycles.

Utility, fees, burns/mints, and fiscal flows

On the legacy chain, ZEN utility was simple and coherent. You paid ZEN fees to transact, and ZEN issuance funded miners, nodes, and treasury. The Horizen Academy’s mining explainer describes a post-2020 state where the block reward was 6.25 ZEN and the miner portion was 3.75 ZEN because 10% each went to Secure Nodes and Super Nodes and 20% went to the treasury.

EON (the pre-migration EVM environment) also had a clear fee policy. The documentation states that in Horizen EVM, the token used for gas was ZEN, and after EIP-1559-style pricing, the “base fee is not burned like in Ethereum,” but instead goes “in a shared pool to be redistributed among the forgers.”

After Base migration, the mechanics change again. All transfers are now executed on Base through ERC-20 smart contract calls.

That means fee capture at the token layer is no longer “native by default.” Base gas is not paid in ZEN. If Horizen wants ZEN to have ongoing fee-driven value accrual, it has to be implemented at the application layer, or on a Horizen-operated rollup/appchain where ZEN is a required fee asset, or via explicit buyback logic.

For a comparison point on how markets react to different governance-token value stories, see our YFI review.

Public primary docs accessible from the migration and governance stack do not, today, specify the exact buyback rate, routing, or burn address policy behind the “network fees to buy & burn” statement. From a modeling standpoint, that is a real gap. A buy-and-burn program is either a deterministic mechanism or it is marketing. Without parameters, it cannot be treated as a dependable security-budget replacement.

Security budget and validator incentives: what Horizen used to buy, and what it buys now

Horizen’s legacy tokenomics were unusually explicit about paying for “security” as infrastructure, not only as consensus. On the proof-of-work mainchain, issuance was split across miners and two incentivized node tiers, plus a treasury stream.

That model has a clean “Security Budget Maximalist” property. It forces ongoing payment for resilience. It is expensive. It is also mechanically hard to underfund, because issuance happens every block.

It also came with the standard long-run problem: each halving cuts the security budget unless fee revenue rises. The December 12, 2024 halving cut the total block reward to 3.125 ZEN.

ZenIP 42407 (pre-Base pivot) shows how the team originally tried to address that: move from PoW to a delegated PoS-style design with Collators and Delegators, allocate 40% of future emissions to the Collator reward structure, and smooth the halving into a continuously declining emission curve to preserve the 21 million cap.

Then Base happened. The Base migration rationale explicitly argues that by migrating to operate as an L3 appchain on Base, the ecosystem “no longer requires a dedicated allocation to blockforging security,” and it reallocates the remaining 5M unminted ZEN to incentives, sustainability, and infrastructure buckets.

This is a very specific trade. Horizen swaps an issuance-funded, protocol-enforced security budget for Base/Ethereum economic security plus a treasury-funded operating budget. If you like lower inflation, you will like the direction. If you care about long-term security robustness, you should treat it as an open question until two things are measurable:

1) Does the post-migration Horizen stack generate recurring fee revenue that is actually captured for operations?

2) If not, is the remaining supply plus treasury management enough to maintain infra without governance capture, service degradation, or chronic sell pressure?

The official ERC-20 contract design also reinforces this shift. The smart contract docs say the ZenToken contract mints the remaining supply “with the rules determined by ZenIP 42409” once vault minting is completed.

So the token’s “security” is now largely upstream (Base and Ethereum), while ZEN’s remaining issuance is downstream (ecosystem and infrastructure spending). That is less a security budget and more a runway.

Governance and parameter control (who can change what)

Horizen’s governance docs describe ZEN as the governance token, with a dual-track process: technical proposals follow a rough-consensus “run the new software” model, while non-technical proposals are enacted via tokenholder vote directives to the Foundation under the governance constitution.

The same constitution states that DAO-approved proposals are reviewed by a Special Council for adherence to mission, constitution, and applicable law. It also sets submission requirements: holding at least 25,000 ZEN to submit a non-technical ZenIP and 100,000 ZEN to submit a technical ZenIP.

This creates an explicit governance gate. It can reduce spam. It also concentrates agenda-setting in larger holders, which matters more now that the largest remaining “economic lever” is allocation of the unminted supply and treasury spending rather than protocol issuance to miners.

One more control surface is purely technical. The migration smart contract docs state that the LinearTokenVesting contract’s admin can modify the beneficiary or vesting parameters, with the note that this “will be subject to offchain DAO voting.”

“Subject to offchain DAO voting” is a social constraint, not a cryptographic one. If you are modeling governance risk, you treat that as discretionary authority with a political backstop.

Finally, under the legacy model, the treasury stream was structurally linked to block subsidy. The Transparency Report describes that the DAO’s portion of the block subsidy was 20% of the total block subsidy, routed to multisig wallets, and it specifies a policy split of that DAO portion: 25% retained in the DAO treasury and 75% allocated to an administrative budget for the Foundation, with a temporary higher allocation to repay pre-launch costs.

Post-migration, those legacy block-subsidy flows are structurally less relevant because the old chains are discontinued.

Risk analysis: tokenomics under stress

Horizen’s current token design is best understood as an ecosystem treasury and governance token sitting on Base, with a finite remaining issuance buffer (the unminted supply) explicitly earmarked for incentives, sustainability, and infrastructure.

That can work. It can also fail quietly, because the protocol is no longer forced to pay for security every block. When the spending decision is human, underfunding is always an option.

Top 3 risks

  1. Security/operations funding gap (dominant), Trigger: the Horizen stack on Base fails to create meaningful, captureable fee revenue, while the DAO/Foundation draw down the remaining unminted supply for ops and incentives. Mechanism: security and reliability become a treasury runway problem instead of an issuance-guaranteed budget; when runway shortens, infra spend is cut, centralization increases (fewer providers), or sell pressure rises from treasury liquidations. Who bears it: users (downtime, degraded UX), builders (infra fragility), and long-term holders (persistent distribution-driven sell pressure). Measurable indicators: DAO/Foundation net outflows and remaining allocation balances, cadence of distribution from vesting, spending share labeled “infrastructure,” and whether any onchain fee capture or buy-and-burn parameters are published and then observed in practice (without primary parameters it should not be modeled as dependable). If you want a tighter measurement playbook, see our research notes for how we frame observable token KPIs.

  2. Governance capture and agenda control, Trigger: low participation governance combined with high proposal submission thresholds and Special Council review becomes a de facto veto regime. Mechanism: resource allocation skews toward insiders or politically durable initiatives, while accountability weakens because “offchain voting” norms are not enforceable by contracts. Who bears it: minority tokenholders and ecosystem builders who rely on neutral grant and infra allocation. Measurable indicators: voter turnout on Snapshot, concentration of voting power, frequency of uncompetitive elections, and whether vesting/admin parameters are changed by contract admins (even if socially approved).

  3. Migration tail risk and “sleeping supply” reactivation, Trigger: renewed user activity around claiming, or any exploit/bug in claim tooling, vault admin processes, or signature workflows. Mechanism: unclaimed balances sit in vaults and can re-enter circulation over time; operational failures can strand users or create reputational shocks. Who bears it: legacy holders (direct loss or inability to access funds), and all holders (confidence and liquidity hit). Measurable indicators: remaining unclaimed balances implied by vault contract balances, reported claim failure rates, and the rate of new claims over time.

Dominant risk: the security budget didn’t disappear, it moved

Horizen’s pre-Base tokenomics paid for security in a way that was hard to misunderstand. Miners got paid. Node operators got paid. The treasury got paid. Even after the 2020 halving, the Horizen Academy article still explains that the miner only receives 3.75 ZEN out of a 6.25 ZEN block reward because the rest is programmatically routed to nodes and treasury.

That is a classic “security budget maximalist” architecture. It is inflationary. It is also mechanically credible. Issuance happens. Security spend happens with it.

Once ZEN becomes an ERC-20 on Base, that linkage is severed by design. The migration docs are explicit that both old chains are discontinued and transfers are now ERC-20 calls on Base.

So what is the security budget now?

First, it is upstream. You inherit Base and Ethereum’s security properties, including their governance and operational risks. ZEN holders do not control that budget with ZEN emissions.

Second, it is internalized as operating expense. The Base-era tokenomics proposal allocates a defined chunk of the remaining unminted supply to “Infrastructure” and a much larger “ZEN Sustainability Initiative,” with the explicit rationale that these funds can support sequencers, RPC, indexers, oracles, bridging support, and other essential services.

That sounds sensible. It is also a fundamentally weaker security commitment than per-block issuance, for the same reason that any discretionary budget is weaker than an automatic one. Discretion can be delayed. It can be reallocated. It can be politicized. And when markets turn, it can be financed via spot selling into thin liquidity.

Horizen’s own governance conversations acknowledge the cultural loss here. Community members state directly that an L3 on Base “won’t have nodes that require staking,” and that the incentives category is meant to fund “productive staking opportunities” at the application level instead.

As a security-budget lens, app-level staking is not a substitute for consensus security. It can create token demand and sticky TVL. It does not guarantee liveness, censorship resistance, or reliable block production for a chain. Those are supplied elsewhere.

The final issue is value capture. If the system does not capture fees in ZEN, then the only durable sources of ZEN-denominated security/ops funding are: (a) remaining unminted supply distributions, and (b) secondary-market purchases by treasury actors. The “fees to buy & burn” line is directionally encouraging, but without hard parameters it cannot be treated as a model input.

That puts Horizen in a narrow corridor. Either it builds a real fee engine with explicit capture, or it runs on runway. Runway tokenomics can fund growth for years. They do not, by themselves, create a permanent security budget. When the runway ends, networks either (1) have genuine fee replacement, (2) reintroduce issuance, or (3) degrade.

If you are working through this kind of transition yourself, this is exactly where disciplined tokenomics consulting earns its keep: you need a budgeted security/ops model with observable KPIs, and governance constraints that turn “we plan to” into “it happens automatically.”



This article is part of our Tokenomics Deep Dive series.