WAN’s real job: collateral for bridges, gas for L1, and stake for two security layers

Wanchain is built around one idea that has persistent token consequences: cross-chain execution is its core product, not a side feature. The chain runs its own L1 and also operates a decentralised bridge network (WanBridge) where cross-chain transactions are executed by a dedicated Bridge Node Group.

If you’re benchmarking cross-chain tokens with similar “infrastructure-first” demand drivers, our CELR tokenomics review is a useful comparison point.

WAN sits at the center of that system in three ways:

1) L1 gas + base asset. WAN is the native coin for transactions and smart contract interactions on Wanchain L1, with a small transaction burn alongside every transaction.

2) Consensus stake (Galaxy PoS). WAN secures the L1 via Wanchain’s PoS validator set, where WAN can be staked directly by validators or delegated by holders.

3) Bridge stake + collateral. WAN can also be staked to run bridge validators (Bridge Nodes, also called Storeman Nodes), delegated to them, and used as collateral to secure cross-chain transactions.

From a market microstructure angle, that matters because WAN is not “just” a payment token. It is a bonded collateral token with two separate staking demand curves (PoS and bridge), plus an explicit fee routing system that periodically converts external-fee assets into WAN and then redistributes and burns it.

Supply cap, distribution, and where float actually comes from

WAN has a stated max supply of 210,000,000.

At the time of writing, CoinGecko’s WAN page showed circulating supply around 198.8M against a 210.0M max supply, implying a relatively small gap between tradable float and fully diluted supply compared to newer, heavily-vesting assets.

The original supply split is explicitly documented in the verified token sale contract comments and constants, including the 210,000,000 total and the percentage buckets.

The important nuance is that Wanchain later made an explicit supply-integrity move. On November 5, 2019, the Wanchain Foundation burned 21,000,000 WAN to preserve the intended total supply while Galaxy PoS began issuing new WAN as rewards.

That one action reshapes how you should think about “FDV.” The cap may be 210M, but the path to that cap is partly emission-driven. Meanwhile, ongoing burns (transaction burns on L1 and the Convert n’ Burn system) continuously pull in the other direction.

Emissions and lockups: Galaxy PoS and Bridge Nodes

Wanchain’s supply behavior is dominated less by a single inflation number and more by who is forced to lock WAN, for how long, and on what cadence. Wanchain has two parallel staking systems with different timing.

Galaxy PoS (L1 validators) uses stake size and lock duration to determine staking power, with validator lock periods selectable from 7 to 90 days.

Key PoS thresholds that shape float concentration:

Validators have minimum stake requirements of 50,000 WAN (delegating validators) or 10,000 WAN (non-delegating validators).
The protocol selects 75 validator nodes per epoch, with 49 open to the public (the remainder initially reserved by the Foundation for launch security, with a plan to phase out).
There is an explicit 10.5 million WAN cap on the total stake (self + delegated) for a single validator node.

PoS emissions are defined as a lifetime reward budget of 21,000,000 WAN, distributed as 2,500,000 WAN in the first year and then reduced by 12% per year. The Foundation also ties this to mainnet history, stating Galaxy PoS went live in September 2019.

Bridge Nodes (Storeman nodes) introduce a different liquidity rhythm. Minimum stake is 10,000 WAN, but active set selection is competitive: only the top 25 nodes by total stake are selected as active validators. The staking period is described as ~30 days (from the 9th of each month to the 9th of the following month), with exit timing referencing withdrawals after the 10th of the month, per the Bridge Node guide.

That monthly cadence creates predictable moments where WAN demand can spike (stake competition to remain top-25) and where supply can re-enter circulation (unselected nodes withdrawing). It is a structural source of short-horizon volatility that “fixed max supply” narratives usually miss.

Wanchain also publishes a more formal cross-chain reward mechanism in its economic incentives documentation. In the version of the docs currently shown, it states an initial design where cross-chain rewards target 1.5x the PoS reward rate (α = 1.5), giving an example snapshot of r1 = 7.67% and r2 = 11.5%, plus a hard cap on cross-chain daily rewards equal to PoS daily rewards, shown as HardCap = 6027 WAN.

Whether those “at present” rates are stable is less important than the mechanism: reward rates are not purely market-driven. They are parameterized, capped, and therefore sensitive to governance and operator behavior.

Fees, Convert n’ Burn, and the buy-and-burn flow

Convert n’ Burn is the part of WAN tokenomics that most directly touches market structure because it creates an explicit fee-to-WAN conversion pipeline.

In Convert n’ Burn v1.0 disclosures, Wanchain describes two fee types for bridge usage: a Network Fee (to cover destination-chain gas paid by the bridge) and a Service Fee calculated as a percentage of transfer value. For most routes, the base Service Fee is disclosed as 0.2%, with typical lower and upper bounds of $0.2 and $100 (subject to exceptions and adjustment).

Then comes the routing. Wanchain discloses that collected bridge fees are converted into WAN and redistributed across five destinations:

40% to a Community Treasury, 30% to Ongoing Operations, 10% to Bridge Nodes & delegators, 10% to PoS Nodes & delegators, and 10% to a burn address.

Two microstructure details matter more than the split itself:

1) It is not continuous. Convert n’ Burn conversions are described as triggered by periodic review, “approximately once a quarter,” flagging assets that have accumulated more than USD 1000 in value for conversion.

2) The WAN buy flow is intentionally smoothed. After bridging assets to Wanchain L1, Wanchain describes converting into WAN gradually over 90 days by swapping small amounts “every few minutes” on Wanswap to minimize slippage.

That is a real design trade-off. Narrative stability improves because you avoid obvious single-block “buy events.” Price discovery also becomes more sensitive to steady, persistent flow. Liquidity shocks do not disappear though. They move up a level, into quarterly conversion decisions and the operational behavior around them.

Convert n’ Burn also explicitly ties bridge fee discounts to WAN holdings. For EVM-originating transfers, Wanchain states that if either the sending or receiving address holds at least 10,000 WAN on Wanchain L1, the Service Fee discount tiers range from 10% at 10k WAN up to 80% at 1,000,000 WAN. The same tier table is described for non-EVM-originating transfers, but keyed off the receiving address.

Critically, Wanchain discloses that WAN staked or delegated to a Bridge Node counts toward those thresholds, while WAN staked in PoS validator nodes does not.

That creates a clean incentive: if you are a heavy bridge user, there is a rational path to moving from “paying fees” to “bonding WAN into the bridge security layer” to reduce fees. In practice, it nudges float into bridge-node delegation rather than purely into PoS staking.

There is also a smaller, more direct burn sink in the user incentive layer. Wanchain’s Bridge-to-Earn system allows claiming tasks by spending XP or burning WAN coin.

Governance and control surface: who can change what

WAN’s token design is not fully “set-and-forget.” The control surface matters because the biggest price-relevant events are parameter changes and liquidity events, not abstract supply caps.

If you’re breaking that control surface into a checklist, our design components guide can help structure the review.

PoS parameters are explicitly constrained by protocol rules disclosed in docs (stake minimums, lock range, stake caps, validator count per epoch). Validator commission mechanics also have guardrails. In the XStake PoS setup guide, Wanchain notes that once a validator sets a Max Fee it is immutable, and delegation fee increases are limited to 1% per day and cannot exceed the Max Fee.

Bridge node set composition is mechanically driven by stake ranking (top 25 by total stake), with a monthly election rhythm. That means large WAN holders can translate balance sheet strength into recurring participation and reward capture. It is not inherently bad. It does create a predictable concentration vector.

Convert n’ Burn and fees are the most governance-sensitive part today. Wanchain explicitly states Service Fee bounds and exceptions “may be adjusted at any time,” and that in case of discrepancies the bridge UI prevails.

The conversion pipeline is also described as “maximally decentralised,” but with “a bit of manual intervention” still required, including quarterly reviews that determine what gets flagged for conversion.

On community governance, the docs and Foundation disclosures are candid that it is still evolving. Wanchain’s docs mention proposing and voting on Community Treasury proposals as in development. The Convert n’ Burn introduction likewise says community treasury management and the voting mechanism will be shared later, and that in the future the community will be able to vote to change how collected fees are allocated.

For traders and long-term holders, that uncertainty is not cosmetic. It directly affects modelability of the largest ongoing flow in WAN markets: the bridge fee conversion and redistribution pipeline.

Risk register (market-structure first)

WAN’s tokenomics are more engineered than most older L1s. The cost is that the system has multiple moving parts that can create sudden supply-demand imbalances. Lockups help until they do not. Burns help until they are outpaced. And fee conversion helps until governance ambiguity turns it into a source of event risk.

We cover similar flow-shaped dynamics (where timing and execution matter more than the headline supply number) in our research reports.

Dominant risk: Convert n’ Burn governance and operational discretion creates event-driven liquidity shocks.

Convert n’ Burn is designed to turn cross-chain activity into WAN buy flow and a partial burn. The market-friendly version of that story is “steady buy pressure.” The microstructure reality is messier.

First, conversions are not per-transaction. They are triggered by periodic review, described as “approximately once a quarter,” and only when assets cross a USD threshold. That concentrates decision-making and timing into discrete windows. If the market starts to anticipate those windows, you can get reflexive behavior. Pre-positioning front-runs the conversion flow. Post-flow, you get mean reversion if the bid disappears.

Second, the conversion is executed over 90 days to minimize slippage. That smoothing is good for DEX execution quality. It also turns the fee flow into an observable, slow-moving factor that can be crowded. When everyone leans on the same slow factor, price can gap when the factor pauses or the market believes it will pause.

Third, 30% of flagged fees are routed to an “Ongoing Operations” bucket held as network coins and stablecoins to cover multi-chain gas costs. This is rational. It is also a discretionary treasury-like pool. If it ever needs to raise WAN liquidity or if fee economics change, it is a potential source of non-scheduled supply to the market. That risk is amplified by the fact that fee parameters themselves can be adjusted.

Finally, governance is explicitly “in development” for treasury proposals and voting mechanics. Until those controls are mature and visible, holders are taking a form of policy risk. It is not the risk that the split exists. It is the risk that the timing, execution, and future parameter changes are hard to handicap.

  1. Trigger: A change in Convert n’ Burn execution cadence, conversion thresholds, or fee parameters.
    Mechanism: The WAN buy-and-burn flow is policy-shaped (quarterly flagging, 90-day conversion, adjustable fees), so parameter tweaks shift both realized demand (WAN buys) and realized supply (redistribution wallets that may sell).
    Who bears it: Spot holders and LPs first (wider spreads, inventory losses), then stakers if yields compress or become more volatile.
    Measurable indicators: Announced fee-table changes on bridge UI, step-changes in burned WAN and converted WAN totals, and abrupt changes in wallet inflows to the five fee destinations.
  2. Trigger: Bridge node stake concentration spikes into a tighter top-25, or large operators exit after missing selection.
    Mechanism: The bridge active set is stake-ranked (top 25), with ~30-day staking periods. That structure can create “auction-like” demand for WAN into the selection window, followed by float re-entry when unselected stake withdraws.
    Who bears it: Short-term holders and perps traders (if listed) through volatility, and bridge users through potential service quality degradation if participation drops.
    Measurable indicators: Increasing stake share held by the top few bridge nodes, higher churn in the active set, and rising delegation concentration toward a small number of operators.
  3. Trigger: A mismatch between PoS emissions and net burn rates persists in the “wrong” direction for the narrative the market is pricing.
    Mechanism: PoS issuance is governed by a declining schedule (2.5M in year one, -12% per year), while burns come from transaction burn and Convert n’ Burn’s 10% burn share. If burns fail to scale with bridge usage, the “deflation” narrative can weaken and invite supply-heavy positioning.
    Who bears it: Long-only holders and stakers, via weaker price support and lower real yield if fee flows soften.
    Measurable indicators: Rolling PoS issuance versus rolling burned WAN (Convert n’ Burn + on-chain tx burns), plus the share of circulating supply bonded in PoS and bridge staking relative to spot volumes.

If you are building around WAN incentives or designing similar systems, the hard part is not the supply cap. It is mapping the real float and the timing of liquidity events. That is where tokenomics consulting earns its keep.



This article is part of our Tokenomics Deep Dive series.