Immutable’s token economy is anchored in one place: a company-set fee and a foundation-run distribution machine

Immutable’s tokenomics are less about “a decentralized gaming token” and more about a deliberate power split: Immutable the company controls key operating parameters (especially the protocol fee), while an issuer-aligned foundation runs distribution programs and staking. That split buys speed and coordination. It also concentrates the ability to change outcomes in a small set of hands.

Structurally, IMX now spans a merged stack. Immutable’s documentation states that the native token of Immutable Chain is IMX, issued by the IMX Ecosystem Foundation, and that on Immutable Chain it is used for gas and can be staked, while on Ethereum it exists as an ERC-20.

Immutable also states that Immutable X (the original StarkEx-based rollup) was merged into Immutable Chain in early 2026, with its interfaces deprecated and scheduled for removal per its Immutable X deprecation notice.

The token incentives moved earlier. Immutable announced that IMX staking on Immutable zkEVM would begin on June 19, 2025, and that staking on Immutable X would end the same day (at the conclusion of the epoch) in its staking migration update.

That history matters because it reveals the real governance surface. The protocol can be merged, deprecated, and re-homed. Tokenholders are not steering that ship in any binding way, at least not in the public docs.

Supply, allocation, and who starts with the chips

The most important hard constraint is supply. Immutable’s whitepaper update states there will be 2,000,000,000 IMX tokens.

The issuer structure is explicit. The whitepaper describes IMX as distributed via the token issuer, Digital Worlds Ltd. NFTS (the “Foundation”), with Immutable as the exclusive service provider developing the protocol and token, managed by the Foundation.

That already tells you where governance power accumulates. A large portion of supply is earmarked for “ecosystem development,” and the Foundation has a facilitation role in governance. Tokenholder voting exists in the design, but the issuer and the operator sit at the center of execution.

The “who has the chips” conclusion is blunt. Even if you grant that “ecosystem development” is community-aligned, it is still a massive discretionary pool. The issuer side decides cadence, program design, eligibility, and partner selection, unless and until a binding governance system constrains it.

Utility and fiscal flows: the 2% fee, plus an IMX conversion loop that funds staking

Immutable’s orderbook documentation states that Immutable sets a fixed percentage fee on all orders, and that for both Immutable X and Immutable zkEVM chains there is a 2% protocol fee set in its orderbook fee documentation.

At the token layer, the whitepaper defines a specific capture mechanism. It states that 20% of Immutable’s protocol fee must be paid in IMX, either directly or by automatically swapping the purchase currency (for example ETH) for IMX on the open market.

Two details matter here, and they cut against casual “fee capture” narratives.

First, the protocol fee is structurally upstream of tokenholder control. Immutable’s docs describe it as set by Immutable. That makes it an admin-like parameter, even if the chain eventually decentralizes validation.

Second, the project explicitly warns against treating IMX like equity. The whitepaper states there is no entitlement, allocation, or rights to revenue purely from owning IMX. This separation between utility and claims is a recurring pattern worth comparing against Aave tokenomics.

In practice, IMX’s “value routing” is incentive-native, not claim-native. The token’s economically meaningful path is: protocol activity generates fees, a specified fraction is turned into IMX demand, and that IMX is routed into reward programs and staking.

Staking and incentives: a participation-gated yield that the issuer can reshape

Staking is funded by the fee capture loop. Immutable’s explainer says staking rewards are generated from 20% of the protocol fee, redistributed to qualified stakers after each 14-day staking cycle.

On the older Immutable X implementation, Immutable’s support documentation described eligibility mechanics tied to on-protocol activity. To qualify during a 14-day cycle, users had to stake IMX and trade at least one NFT on the Immutable X orderbook.

The staking home moved. Immutable announced that staking on Immutable X would end on June 19, 2025, with staking available on Immutable zkEVM from that same date, and that the new model still requires an NFT trade within the cycle to earn rewards.

Today, Immutable’s chain docs frame staking as something “provided by the IMX Ecosystem Foundation,” and they point users to the Foundation’s community site for participation.

The most governance-relevant observation is that staking is not a neutral, unstoppable contract primitive in the public documentation. It is an incentive program whose terms have changed over time, and which is explicitly tied to ecosystem participation rules and an issuer-managed staking pool. The whitepaper even flags that staking reward terms may be subject to change via governance or a similar process.

The Foundation also runs direct incentive rails beyond staking, including liquidity and trading-rewards style programs with eligibility constraints.

Seen as token economy design, Immutable is choosing a familiar path: bootstrap adoption using a large ecosystem allocation, and route a portion of fees into stakers. Seen as governance power distribution, it is also choosing issuer and operator discretion over hard-coded credibly neutral policy.

Governance and parameter control: token voting exists on paper, but execution power sits with the Foundation and Immutable

The whitepaper describes “decentralized governance” as tokenholder voting on token-related proposals. The proposal scope is broad, including allocating token reserves, voting on developer grants, activating daily rewards, and changes in token supply.

But the same section embeds the power reality.

Proposal creation is gated. The whitepaper states that submitting a proposal requires owning a token threshold that would be determined later.

The Foundation has agenda influence. It “has the right to propose items” and plays a facilitation role in curating proposals to be voted on.

Execution is not framed as automatic. The whitepaper says successful votes will be executed as soon as feasible, given “commercial and technological implementation limitations.”

Even where voting power is defined, it is standard token-weighted governance. The whitepaper states governance is performed on L1, with wallet balances sourced across L1 and L2, and that voting power increases with token holdings. For a baseline comparison on token-weighted voting mechanics, see Cosmos Hub.

Now put that next to the operational knobs. Immutable’s docs state the protocol fee is set by Immutable, and that it is 2% on both Immutable X and Immutable zkEVM, with fees described as changeable over time.

That’s the governance trade-off in one sentence. Immutable is optimizing for operational flexibility. Tokenholders get a governance story, and maybe real influence over incentive allocation. They do not appear to have hard constraints over core economics like fee rates, nor over major platform transitions like deprecating Immutable X and merging the chain stack. For a contrasting case study on L2 governance positioning and parameter control, compare Optimism tokenomics.

Risk analysis: where this token model strains under power concentration

Dominant risk: governance centralization over fee policy and incentives.

IMX is positioned as a utility, staking, and governance token. The catch is that the value loop it relies on is ultimately a policy choice controlled by the operator and the issuer-side entities.

The protocol fee is the upstream valve. Immutable’s docs say Immutable sets it, and the IMX buy-and-distribute loop is downstream, relying on a rule that 20% of that protocol fee is paid in IMX or swapped into IMX, and then routed to staking rewards.

This means IMX holders are exposed to governance-by-document-update. If the protocol fee changes, if the conversion share changes, if reward eligibility tightens, or if incentives pivot from staking to grants to liquidity programs, tokenholder economics can swing without any guaranteed on-chain constraint. The whitepaper explicitly frames governance execution as bounded by commercial and technical feasibility, and gives the Foundation a curation role.

Even the infrastructure layer reinforces the same pattern. Immutable’s zkEVM architecture docs state it initially launched with only Immutable as a single sequencer/validator, explicitly to respond quickly and protect chain integrity, with a long-term goal to open the chain gradually in its zkEVM architecture overview.

If you want the politically-aware framing, it is this. The system is not “decentralized governance that sometimes feels centralized.” It is centralized control with some tokenholder participation lanes, mainly around incentive allocation, that may widen over time. Your confidence level should match that.

Top 3 risks

  1. Trigger: Immutable changes protocol fee terms or fee recipients, or adjusts staking reward rules.
    Mechanism: Immutable’s docs state the protocol fee is set by Immutable, while IMX rewards depend on a defined conversion/allocation loop and Foundation-run staking and reward programs.
    Who bears it: IMX stakers and long-term holders first, then marketplaces and games whose unit economics assumed stable fee and reward policy.
    Measurable indicators: updates to fee schedule language, changes to fee configuration documentation, staking program rule updates, and epoch-level reward distribution changes.
  2. Trigger: a sustained drop in NFT and game asset trading volume routed through Immutable’s orderbook and marketplaces.
    Mechanism: staking rewards are funded by a share of protocol fees, so lower volume reduces fee generation and shrinks the staking rewards pool.
    Who bears it: stakers (lower rewards), and liquidity providers or incentive hunters who depend on program payouts to justify capital deployment.
    Measurable indicators: staking dashboard reward rates per cycle, protocol fees collected over time, and on-chain marketplace/orderbook settlement volumes.
  3. Trigger: sequencer/validator outage, compromise, or prolonged censorship while the chain remains effectively centralized.
    Mechanism: Immutable’s zkEVM documentation states the chain initially launched with only Immutable as a single sequencer/validator, concentrating liveness and ordering in one operator while decentralization is phased in.
    Who bears it: traders and games relying on predictable settlement, users with time-sensitive actions, and protocols integrating on top of Immutable Chain.
    Measurable indicators: sequencer downtime incidents, delayed transaction inclusion, status page incidents, and any published roadmap updates to sequencer decentralization.

If you are advising a team building on Immutable, or holding IMX as a bet on ecosystem throughput, the work is not “find the yield.” It is map the governance perimeter. Document which parameters you are assuming are stable, who can change them, and what process constrains that change. If you want a repeatable approach, our methodology guide lays out the best-practice checks.

For teams that need hands-on help with those assumptions (and how they translate into program design), see our tokenomics services.

If you want a quick refresher on common governance, supply, and incentive terms used in reviews like this, start with our tokenomics FAQ.



This article is part of our Tokenomics Deep Dive series.