Fluid’s token design is treasury-centric, not fee-share native

Fluid is built to merge a money market and an AMM through a shared “Liquidity Layer,” so collateral and even debt can become trading liquidity via Smart Collateral and Smart Debt positions. This is not a “token-first” system. The token is the control plane. The economic link between protocol usage and token value is routed through a DAO treasury, then optionally expressed via incentives and buybacks.

On the governance side, the original design intent is explicit: INST (now rebranded to FLUID) governs Fluid, including rate curves, fees, Liquidity Layer configurations, protocol allowances, vault configuration, and rewards. That scope matters more than any single “utility” bullet. If you model FLUID, you are modeling the credibility of parameter-setting and treasury policy over time. Compared with fee-share tokenomics, this design keeps value capture as an explicit governance choice rather than a native distribution rule.

Two public statements anchor the economic architecture:

1) Governance is expected to own the knobs. Fluid’s launch governance proposal states that the protocol is administered by tokenholders and that all revenue will be directed toward the DAO treasury, framing revenue to treasury as the default routing.

2) The token was rebranded without supply or address changes. The December 3, 2024 proposal frames the rebrand as a 1:1 conversion from INST to FLUID with the same Ethereum token address and the same 100M total supply, as set out in the rebrand plan.

Supply and distribution: fixed mint, time-released access

Fluid’s token supply is structurally simple and hard-capped. 100,000,000 tokens were minted at genesis, then made “accessible over the course of 4 years,” as described in the genesis mint documentation. Post-rebrand, the same 100M total supply and token address are asserted to remain unchanged.

The key consequence: there is no “emissions lever” in the sense of an uncapped mint. The only long-run distribution lever is how quickly already-minted tokens move from locked or treasury-controlled states into circulating hands, and whether the DAO later pulls tokens back via buybacks.

Allocations at genesis (as published for INST, and carried forward structurally through the FLUID rebrand) were:

Two distribution mechanics from the original launch are worth remembering because they shaped early ownership and governance legitimacy.

First, 11,000,000 tokens were set aside for user claims at launch (10,000,000 on Ethereum Mainnet positions and 1,000,000 on Polygon Aave positions), with explicit formulas intended to avoid whale-dominated outcomes, including diminishing increments and “double counting” for Instadapp users managing positions via the product.

Second, a short, bounded liquidity mining window existed at genesis: 3,000,000 tokens over three months, plus UNI v3 staking rewards (250,000 + 750,000 across two ranges).

In practice, the part you can treat as “hard” in a model is the fixed supply itself. Most other token behavior is governance-selected.

Utility in-product: FLUID is the permissioning and parameter token

The cleanest way to talk about FLUID utility is to avoid vague “governance token” language and instead enumerate the actual control surface Fluid governance has claimed responsibility for. If you want a structured lens for that surface, map it to standard token economy components.

The original Fluid introduction states tokenholders are responsible for: rate curves, fees, and token configurations in the Liquidity Layer, plus protocol allowances to interact with that layer, vault configuration, and the determination of rewards in the lending and vault systems.

In practice, governance proposals show this is not theoretical. Fluid vault and market proposals specify dense parameter sets, including utilization-based rate curves, collateral factors, liquidation thresholds, penalties, withdrawal gaps, borrow fees, and liquidity expansion controls.

As a mechanism designer, I read this as “governance is the risk engine.” The token gives you influence over the live risk surface of a cross-coupled money-market-plus-AMM system. That creates real value for aligned holders. It also means the token’s legitimacy depends on process quality, not marketing.

One notable example of an explicit design decision: a March 14, 2024 proposal removed automated limit adjustments (via a LiquidityConfig contract) and moved to static limits in the 20% to 25% range for expansion settings. That is a deliberate shift away from algorithmic adaptation and toward simpler, more governable parameters. It reduces code-path complexity. It increases reliance on governance diligence.

Fiscal flows: revenue to treasury, then incentives and buybacks as policy

Fluid’s hard statement is that revenue routes to the DAO treasury. The soft part is what the treasury then does with it. The project’s own rebrand plan leans heavily on that “second step.”

The December 3, 2024 proposal introduces three treasury-mediated tokenomics primitives:

1) Growth incentives funded from token supply. The proposal budgets up to 0.25% of total supply per month for “Stable Lending” incentives and up to 0.25% of total supply per month for DEX incentives. If fully utilized, that is 0.5% of supply per month, which is 6% of supply per year. This is not “inflation.” It is distribution velocity from a fixed pool. Economically, it behaves like emissions against circulating float.

2) Liquidity provisioning using treasury-held tokens. The proposal states governance will allocate 5% of total supply to establish FLUID liquidity on DEX pools, with an explicit note that 2.5% was already utilized and the remainder could return to the DAO if not used.

3) Buybacks that are intended to be algorithmic, but whose end-state is not yet a credible commitment. The same proposal states a buyback program would activate after Fluid reaches $10 million in annualized revenue, following an x * y = k model keyed to FLUID’s FDV, with up to 100% of earnings allocated to buybacks depending on valuation.

Two details are mechanism-critical.

First, the proposal states bought-back tokens would be kept in the treasury, and governance would decide whether to burn, distribute to holders, or use them as incentives. That is policy optionality. It weakens forward modelability because “buybacks” can become “temporary inventory accumulation.” It also gives governance a second chance to re-inject supply later.

Second, the buyback discussion shows the model was still under debate in 2025, with alternative models discussed and missing parameters called out, including how annualized revenue is defined and how the tapering function is pinned down.

There is also an operational reality check: in a September 17, 2025 update, the team states buybacks would kick off on October 1, 2025, and that for the first month 100% of mainnet revenue would be allocated to buybacks because automated buyback infrastructure was not yet complete (see the September 2025 update).

On “what generates revenue,” Fluid’s own public revenue dashboard reports revenue aggregated across Fluid and Instadapp Lite, including “Annualized Revenue (30d)” and a breakdown of trailing revenue windows. This is a useful transparency artifact, but it is not the same thing as an immutable fee schedule.

Finally, DEX-side fiscal routing can be product-specific. A 2025 proposal for “Fluid DEX Lite” states that additional swap fees flow directly to the DAO treasury and that 100% of fees generated by DEX Lite would go to the DAO as an extra revenue source. It also describes extremely low pool fees in the ecosystem, citing 0.0005% on USDC-USDT as a context for sandwich-attack-driven volume.

Governance and parameter control: strong tooling, weak constraints

Fluid’s governance stack is conventional but powerful. Instadapp governance documentation describes a two-track system: Snapshot for off-chain signaling and Atlas for on-chain voting.

From the original INST launch, the governance parameters were published as:

1% of supply to submit a proposal, 4% quorum, a ~3 day voting period, and a ~2 day timelock delay.

Then the system explicitly tightened execution latency. A February 7, 2024 proposal updated timelock configuration with ~1 day voting delay, ~2 day voting period, and ~1 day execution queue, and it passed.

That trade is clear. Shorter governance cycles improve operational responsiveness, which matters when you are tuning a live risk engine. It also reduces review windows. In a system where governance can set “each & every component,” shortening the cycle raises the premium on strong proposal hygiene and independent simulation.

The other constraint gap is subtle. Fluid’s published buyback direction repeatedly signals algorithmic intent, including x*y=k and TWAP-based approaches. But the same documents leave open the fate of bought-back tokens, and the operational update shows interim discretionary allocation of revenue.

As a mechanism designer, I treat this as the central governance question for FLUID: can the DAO credibly commit to a predictable value-accrual rule, or will value-accrual stay as a “good weather” discretionary lever that competes with growth spend?

For deeper dives on these design tradeoffs, we publish related crypto research.

Mechanism stress points that matter for tokenholders

Fluid’s tokenomics are exposed to the protocol’s microstructure choices because the token’s value capture is treasury-mediated. When the product design creates externalities, governance tends to patch them with incentives. That can work. It is also expensive.

A concrete example is the DEX v1 rebalancing behavior. In May 2025, the team described that during sharp volatility, the v1 design’s rebalancing can incur losses to LPs, with realized losses outweighing fee income in the ETH-USDC pool under the market path observed. The proposed mitigation included vesting 500,000 FLUID (0.5% of supply) over a year for affected users, plus ongoing monthly rewards until DEX v2 is live.

This is not “bad.” It is a rational internalization of a design externality. The tokenomics point is that compensation came from the token supply and incentive budget, not from an automatic fee rebate. That keeps the system flexible. It also keeps the token’s supply trajectory governance-dependent.

Fluid’s roadmap continues to expand the governance-controlled surface. A blog post states DEX v1 launched on October 29, 2024, and DEX v2 aims to support dynamic fees and multiple DEX types deployed by governance on top of a singleton architecture. That increases expressive power. It also increases the number of parameters that can break under adversarial conditions if not carefully constrained.

On the “governance versus team” boundary, Fluid DEX Lite is a revealing case. The proposal states a $5M USDC/USDT credit line would be provided, that the team multisig would be the sole operator, and that all pool parameters (fee, range, etc.) will be managed by the team based on market conditions. Even if that is operationally pragmatic, it is discretionary control. Tokenholders should treat it as such when pricing governance risk.

Risk register

The system has real technical ambition and unusually transparent governance parameter posts. It also has a token economy that leans heavily on policy choices rather than immutable flows. That combination can work. It demands discipline.

Top 3 risks

  1. Dominant risk: Treasury policy remains under-specified, making FLUID value accrual a governance-contingent narrative rather than a deterministic rule.

    Trigger: Buyback “automation” remains delayed, or the DAO revises buyback activation criteria, buyback percentages, or the handling of bought-back tokens during market stress.

    Mechanism: Fluid routes revenue to a DAO treasury, then relies on governance to decide whether and how that revenue becomes buybacks, growth incentives, liquidity provisioning, or simply retained funds. The rebrand plan explicitly states bought-back tokens are held in treasury and governance decides whether to burn, distribute, or re-incentivize. That optionality makes ex ante valuation fragile because the same “buyback” can be either (a) a permanent reduction in effective float through burn, (b) a temporary inventory build, or (c) a deferred emissions pool.

    This is a credible-commitment problem. If the DAO wants FLUID to price like a revenue-anchored asset, it needs a rule that is (1) precisely defined, (2) hard to manipulate, and (3) hard to reverse. Without those, “algorithmic buybacks” are more slogan than mechanism.

    The update that allocates 100% of mainnet revenue for one month because the automated infrastructure was not ready is the clearest signal of this risk. The intent is good. The governance pattern is discretionary. Discretion tends to expand in emergencies. That is exactly when tokenholders most want constraint.

    Who bears it: Long-term holders bear valuation instability. Active users bear incentive instability. Delegators bear the cost of monitoring. If bought-back tokens are later redeployed as incentives, future holders effectively subsidize past buybacks through renewed distribution.

    Measurable indicators: (i) A published, parameter-complete buyback spec (FDV or FDV/annualized-revenue thresholds, TWAP definition, tapering function), (ii) on-chain execution that matches the spec over time, (iii) the treasury’s treatment of repurchased tokens as permitted by the rebrand plan, and (iv) revenue trend relative to the proposed $10M annualized activation condition.

  2. DEX design externalities force token-funded patch cycles.

    Trigger: Volatile price regimes that push v1 pools out of their effective ranges, causing rebalancing losses that exceed fee income, leading to LP exits.

    Mechanism: If LP performance degrades, governance can respond by widening ranges, changing fee settings, or compensating LPs with FLUID incentives. The May 2025 ETH-USDC post explicitly proposes vesting 500,000 FLUID (0.5% supply) for affected LPs. That converts a product-mechanism issue into token supply velocity.

    Who bears it: LPs bear direct losses. Tokenholders bear the incentive dilution or treasury opportunity cost. Traders bear worse execution if liquidity thins.

    Measurable indicators: (i) Recurring incentive programs tied to DEX performance, (ii) pool-level fee revenue versus LP PnL disclosures, and (iii) governance proposals that repeatedly adjust range and fee parameters across the same pairs.

  3. Governance centralization and shortened review windows increase tail risk.

    Trigger: Concentrated delegation, fast governance cycles, or operational reliance on team-managed parameters for key subsystems.

    Mechanism: The timelock configuration was updated to tighter timings (1 day delay, 2 day voting, 1 day queue), explicitly to improve reaction times. Separately, DEX Lite proposes team-managed pool parameters and team multisig operational control. Faster control loops and semi-centralized operation can be appropriate for product iteration, but they weaken the security margin that governance timelocks are supposed to provide.

    Who bears it: Users bear the risk of rushed parameter changes. Tokenholders bear reputational and economic damage if governance missteps. Integrators bear risk if assumptions change faster than they can adapt.

    Measurable indicators: (i) Distribution of voting power on Atlas and Snapshot, (ii) frequency of “fast fix” proposals, (iii) number of systems where the team is the explicit operator, and (iv) timelock and queue durations relative to proposal criticality.

If you want a deterministic token economy, Fluid is not there yet. The project is converging toward algorithmic policy, but it is still negotiating the parameters in public and executing interim discretionary steps. That is a valid development path. It should lower confidence in parameter stability until the rules are fully pinned down on-chain.

If you’re doing tokenomics consulting or tokenomics design work on top of Fluid, the practical task is not inventing new emission schedules. It is specifying constrained treasury policy, including buyback math, oracle definitions, and the lifecycle of bought-back inventory, so the token economy can be modeled and audited like any other critical protocol module-and that is exactly what our tokenomics design services focus on.



This article is part of our Tokenomics Deep Dive series.