← Inferno

Tokenomics Deep Dive

Complete breakdown of IFR fee mechanics, deflation model, token allocation, fair launch design, and fee-exempt addresses.

1B Initial Supply
3.5% Default Fee
2.5% Burn per Transfer
9 Decimals

1. Fee-on-Transfer Mechanics

Every standard ERC-20 transfer of IFR triggers an automatic fee mechanism built directly into the token's _update function. This is not an external router or wrapper — the fee logic lives inside the token contract itself, making it impossible to bypass on any DEX or wallet transfer.

Fees are only applied on normal transfers between non-exempt addresses. Minting (from address(0)) and burning (to address(0)) are excluded. If either the sender or the recipient is marked as feeExempt, the entire fee is waived.

Fee Breakdown

Fee Type Rate Basis Points Destination
Sender Burn 2.0% 200 bps address(0) — permanently burned
Recipient Burn 0.5% 50 bps address(0) — permanently burned
Pool Fee 1.0% 100 bps poolFeeReceiver — protocol wallet
Total 3.5% 350 bps —
Max Cap (governance limit) 5.0% 500 bps Sum of all three cannot exceed this

Calculation Example

Sending 10,000 IFR

Transfer Amount 10,000 IFR
Sender Burn (2.0%) - 200 IFR
Recipient Burn (0.5%) - 50 IFR
Pool Fee (1.0%) - 100 IFR
Net Received by Recipient 9,650 IFR
Total Burned (supply reduction) 250 IFR
Pool Fee Receiver gets 100 IFR

Contract Logic

The fee mechanism is implemented by overriding OpenZeppelin's _update internal function. All fee calculations use basis points (1 bps = 0.01%) for precision with integer arithmetic.

function _update(address from, address to, uint256 value) internal override {
    // Only apply fees on normal transfers (not mint/burn)
    // and when neither party is exempt
    if (from != address(0) && to != address(0)
        && !feeExempt[from] && !feeExempt[to])
    {
        uint256 burnSender    = (value * senderBurnBps)    / 10_000;
        uint256 burnRecipient = (value * recipientBurnBps) / 10_000;
        uint256 poolFee       = (value * poolFeeBps)       / 10_000;
        uint256 totalBurn     = burnSender + burnRecipient;
        uint256 netAmount     = value - totalBurn - poolFee;

        // Net amount to recipient
        super._update(from, to, netAmount);
        // Pool fee to receiver
        super._update(from, poolFeeReceiver, poolFee);
        // Burn — tokens go to address(0), totalSupply decreases
        super._update(from, address(0), totalBurn);
    } else {
        super._update(from, to, value);
    }
}

Important: If either the sender or the recipient is feeExempt, the entire transfer proceeds without any fees. Both parties must be non-exempt for fees to apply.

2. Deflation Model

Inferno is a purely deflationary token. There is no minting function beyond the initial supply creation in the constructor. Every taxed transfer permanently removes tokens from circulation by sending them to address(0), which decreases totalSupply.

Key Properties

Connecting to Ethereum Mainnet…
Current Supply
—
Total Burned
—
Burn Rate
—

Projected Supply Scenarios

The following table illustrates how supply decreases based on cumulative transfer volume. These are simplified examples assuming uniform transfer sizes and no fee-exempt transfers.

Scenario Transfer Volume Approx. Burned Remaining Supply % Deflation
1,000 transfers of 10,000 IFR 10,000,000 IFR 250,000 IFR 999,750,000 IFR 0.025%
10,000 transfers of 10,000 IFR 100,000,000 IFR 2,500,000 IFR 997,500,000 IFR 0.25%
100,000 transfers of 10,000 IFR 1,000,000,000 IFR 25,000,000 IFR 975,000,000 IFR 2.5%
1M transfers of 10,000 IFR 10,000,000,000 IFR 250,000,000 IFR 750,000,000 IFR 25%

Key Insight: The deflation rate is entirely driven by transfer volume, not by the passage of time. High trading activity on DEXes accelerates token burns. During low-activity periods, the supply remains stable. This creates a natural correlation between usage and scarcity.

Fee Governance

The owner (Governance contract with 48-hour timelock) can adjust the three fee rates via setFeeRates(). The hard cap of 500 bps (5%) is enforced on-chain — the sum of all three rates can never exceed this limit, even through governance action.

function setFeeRates(
    uint256 _senderBurnBps,
    uint256 _recipientBurnBps,
    uint256 _poolFeeBps
) external onlyOwner {
    require(_senderBurnBps + _recipientBurnBps + _poolFeeBps <= 500, "fees>5%");
    senderBurnBps    = _senderBurnBps;
    recipientBurnBps = _recipientBurnBps;
    poolFeeBps       = _poolFeeBps;
}

3. Token Allocation

The total initial supply of 1,000,000,000 IFR is distributed across six categories at deployment. All allocations are executed in the deploy script — there is no ongoing emission or inflation mechanism.

Category Percentage Amount (IFR) Unlock Schedule
DEX Liquidity 40% 400,000,000 Held by LP Reserve Safe (3-of-5 Gnosis Safe) for governance-controlled LP expansion. Bootstrap LP was created separately by BootstrapVaultV3.finalise() with 100M IFR + 0.030 ETH on 05.06.2026.
Liquidity Reserve 20% 200,000,000 Initial timelock ended 01.09.2026. All 200M IFR remains held; current cap is 50M IFR per 90 days and 0 IFR has been withdrawn. NOT used for Bootstrap.
Team Vesting 15% 150,000,000 12-month cliff, 36-month linear vesting. 0 tokens available before March 2027.
Treasury 15% 150,000,000 Gnosis Safe multisig. Funded Bootstrap with 144.75M IFR plus a 5.25M IFR top-up. No automatic refill path is deployed.
Community & Grants 6% 60,000,000 Community Safe (57.9M received — 1.5M burned + 0.6M pool fee). 50M → Bootstrap. ~7.9M operational reserve.
Builder Ecosystem 4% 40,000,000 PartnerVault contract. Partner rewards not active; planned for verified checkout redemptions only.

Allocation Visualization

DEX Liquidity
40%
400M IFR
Liquidity Reserve
20%
200M IFR
Team Vesting
15%
150M IFR
Treasury
15%
150M IFR
Community & Grants
6%
60M IFR
Builder Ecosystem
4%
40M IFR

Unlock Schedule Details

DEX Liquidity (40% — 400M IFR)

Liquidity Reserve (20% — 200M IFR)

Team Vesting (15% — 150M IFR)

Treasury (15% — 150M IFR)

Community & Grants (6% — 60M IFR)

Builder Ecosystem (4% — 40M IFR)

🔒 Builder Vault — Why are the 40M safe?

The 40M IFR in the Builder Vault are not freely available. They can only be released through real usage:

  • A user locks IFR for a Builder product
  • The Vault automatically pays a % as reward
  • Rewards vest linearly over 6–12 months
  • No admin can withdraw the 40M directly
  • All parameters are controlled by Governance (48h timelock)

Bottom line: If nobody locks IFR, all 40M remain permanently locked in the contract.

Note: BuybackVault and BurnReserve are not genesis allocations. The 1% IFR transfer-pool fee accrued in FeeRouterV1 until Proposal #21 (05.10.2026) and goes to BuybackController since; it is not automatically forwarded to either contract. Bootstrap was funded via Plan B from Treasury + Community Safe — not a standalone genesis bucket.

Bootstrap Event (Plan B — COMPLETED ✅ 05.06.2026)

LP Allocation — Phased Release

Phase Amount Trigger Mechanism
Phase 1 ✅ 100M IFR DONE — finalise() 05.06.2026 23:51 UTC LP created: 100M IFR + 0.030 ETH → Uniswap V2 LP. 100M IFR reserved for contributor claims. LP Token: 0xbE495E9c…. Team.Finance was disabled; LP remains in BootstrapVaultV3, which exposes no LP withdrawal function.
Phase 2 100M IFR Not scheduled; initial reserve lock ended 01.09.2026 The current 50M-per-90-day cap cannot supply 100M in one period. Any reserve withdrawal needs a Governance proposal + 48h timelock; any cap change and LP action require separate explicit decisions.
Phase 3 100M IFR Governance decision (flexible timing) 3-of-5 Multisig + 48h Timelock. Amount and timing based on market conditions.

Iron rule: ETH always stays in the LP — never withdrawn by the team.

BuybackVault (protocol contract — not a genesis allocation)

BurnReserve (protocol contract — not a genesis allocation)

4. Fair Launch Model (CFLM)

Inferno uses a Community Fair Launch Model (CFLM), which guarantees that no individual or group receives preferential access to tokens before public trading begins.

Core Principles

Principle Implementation
No presale Zero tokens sold before Uniswap listing
No private rounds No seed, private, or strategic investor allocations
No VC allocations No venture capital or institutional pre-purchase agreements
Transparent distribution All token transfers executed via the public deploy script on-chain
Deployer exemption disclosed The Deployer EOA remains feeExempt = true after executed Proposal #7 (18.03.2026); no revocation proposal is recorded through #16
Team tokens vested 15% allocation locked for 48 months (12-month cliff + 36-month linear)
Liquidity locked Reserve tokens locked for a minimum of 6 months

How It Works

  1. The deploy script mints the entire 1B IFR supply to the deployer
  2. The deployer distributes tokens to all allocation contracts (Vesting, LiquidityReserve, Treasury, Community wallet)
  3. 40% is paired with ETH on Uniswap V2, creating the initial liquidity pool
  4. Executed Proposal #7 set the Deployer EOA feeExempt = true; the active exemption is publicly disclosed and remains governance-revocable
  5. Ownership of InfernoToken (and all admin functions) is transferred to the Governance contract with its 48-hour timelock
  6. From this point, no single entity has privileged access to the token

Verification: Every step of the CFLM deployment is fully verifiable on-chain. All contract source code is verified on Etherscan, and the deploy script is open source in the project repository.

5. Fee Exempt Addresses

Certain protocol contracts are marked as feeExempt to ensure that internal protocol operations (vesting releases, reserve unlocks, buyback executions, burns) are not taxed. Without these exemptions, protocol mechanisms would lose tokens to fees on every internal transfer, breaking the intended allocation math.

Exempt Contracts

Vesting
Team token releases must deliver the exact vested amount without fee deductions
LiquidityReserve
Reserve unlocks should transfer the full quarterly allocation to the target
Treasury
Treasury disbursements to fund development and operations must not be taxed
BuybackVault
Buyback operations purchase IFR from the market — fees would reduce effectiveness
BurnReserve
Tokens held for scheduled burns should not lose value to transfer fees
IFRLock
Users locking and unlocking tokens should not be penalized by fees on lock/unlock operations
CommitmentVault
Voluntary lock deposits and withdrawals must transfer full amounts — feeExempt since 06.04.2026
LendingVault
Lending deposits, repayments, and liquidations must be exact — feeExempt since 06.04.2026
BuybackController deployed / wired
Fee-exempt since 16.04.2026 and configured as FeeRouterV1's native-ETH fee collector since 18.04.2026. Permissionless execution still depends on controller balance, cooldown and pause state.
LP Token (IFR/WETH) ✅ active
Uniswap V2 LP Token (0xbE495E9c0d8cc2DCf95570cf95B63c4844dF31A0) — Proposal #15 executed 08.06.2026, feeExempt = true.
Deployer EOA active disclosed exception
0x6b36687b0cd4386fb14cf565B67D7862110Fed67 — Proposal #7 executed 18.03.2026. The exemption is visible in feeExempt(address) and can be revoked only through Governance.

Exemption Rules

// Setting fee exemption (onlyOwner = Governance contract)
function setFeeExempt(address account, bool exempt) external onlyOwner {
    feeExempt[account] = exempt;
    emit FeeExemptUpdated(account, exempt);
}

// Fee check in _update:
// Both sender AND recipient must be non-exempt for fees to apply
if (from != address(0) && to != address(0)
    && !feeExempt[from] && !feeExempt[to])
{
    // ... apply fees
}

Security Note: The fee exemption mapping is controlled exclusively by the Governance contract (owner). No single EOA can grant or revoke exemptions. Any change requires a proposal, a 48-hour waiting period, and execution — giving the community time to review and react.

6. PartnerVault & Partner Rewards

The Builder Ecosystem Pool (4%, 40M IFR) sits in the PartnerVault contract on Ethereum Mainnet. Partner rewards are not active: no partner is registered and no reward has been paid (verified on-chain: totalAllocated, totalRewarded and totalClaimed are 0). The pool is never refilled.

Decided Model: Verified Checkout Redemptions

From the first pilot partner on, rewards follow one rule: IFR only for a real, seller-confirmed checkout redemption at a registered pilot partner. A lock alone never earns a reward.

Property Value
Pool Size40,000,000 IFR (4% of supply), no refill
TriggerVerified checkout redemption at a registered pilot partner
ValuationEUR per redemption, paid in IFR at the published 7-day TWAP at settlement; no fixed rate
Per-Partner BudgetHard cap (the partner's PartnerVault allocation), set per pilot by Governance
SettlementPer period by Governance proposal (recordMilestone, 48h timelock)
Vesting180–365 days linear per partner, optional cliff (contract bounds)
PauseTreasury Safe (PartnerVault guardian)
Claimclaim() by the partner beneficiary after vesting

Contract parameters that the model does not use: PartnerVault also contains a lock-triggered path, recordLockReward, paying lockAmount × rewardBps / 10000 (rewardBps = 1500, contract bounds 500–2500) under a 4,000,000 IFR annual cap (bounds 1M–10M). The project does not use this path, because a lock can be opened and closed again to farm rewards. Policy: PARTNER_REWARDS_MODEL_B.md.

7. Bootstrap Pricing (Phase 0)

In the initial bootstrap phase, all pricing is token-denominated. There is no USD pricing, no oracle, and no TWAP — this is a deliberate design decision for a zero-capital launch.

How It Works

Phase Pricing Model Requirements
Phase 0 (Current) Product-defined IFR amount (for access while the threshold remains locked and the integration remains available) No oracle, no USD, fully on-chain
Phase 2+ (Future) USD-based via TWAP + ETH/USD oracle ≥ 250K USD liquidity, price floor at 40% of launch price

Why Token-Denominated?

Transition to Phase 2: USD-based pricing will only be activated once sufficient DEX liquidity exists (≥ 250K USD). Until then, token-denominated pricing ensures the protocol functions without external dependencies.

8. Protocol Fee & FeeRouter

The FeeRouterV1 contract handles protocol-level fees on IFR swaps. These are separate from the token's built-in transfer fees (2.5% burn + 1% pool fee).

Where the 1% IFR pool fee goes: from Proposal #6 until Proposal #21 the token's poolFeeReceiver was FeeRouterV1. FeeRouterV1 forwards only native-ETH swap fees and has no IFR withdrawal function; the IFR it held was recovered to the Treasury Safe on 7 October 2026 by a governed batch (CWA-02). Since Proposal #21 (executed 5 October 2026, block 26,124,660) pool fees go to BuybackController, where the IFR stays recoverable by Governance via withdrawIFR (the deployed controller is dormant, JUL-08, so nothing is used automatically). FeeRouterV1 holds 0 IFR since that recovery.

Permanently lost IFR: only CV-01 — 26,418,467.99 IFR in CommitmentVault V1 price-conditioned tranches that can never unlock (not burned; still counted in totalSupply), 2.651% of totalSupply at block 26,151,369 (9 October 2026). The 734,545.07 IFR held by FeeRouterV1 are not lost: they were recovered to the Treasury Safe on 7 October 2026 by a governed batch (CWA-02, Proposals #22 and #23, block 26,143,797) and are unallocated Treasury IFR. FeeRouterV1 holds 0 IFR. Details: Transparency.

Fee Structure

ParameterValueNotes
protocolFeeBps5 bps (0.05%)Default, governance-adjustable
FEE_CAP_BPS25 bps (0.25%)Hard cap, contract-enforced
Fee targetfeeCollector = BuybackControllerSet via Proposal #14 (18.04.2026)

Discount Vouchers (IFR Points)

Users earn points through verified actions in the IFR ecosystem. Points can be redeemed for a signed EIP-712 discount voucher, applied against the FeeRouter protocol fee at swap time. A voucher waives that fee up to the current on-chain protocol fee (currently 5 bps, 0.05%); it never reduces the IFR token transfer fee or burn.

ActionPoints
Wallet Connect (SIWE)10
Complete Wallet Setup Guide20
Add IFR Token (Decimals verified)20
Complete Lock Guide30
Builder Onboarding50

Voucher status: the points-to-voucher issuer is not live. Under the deployed FeeRouterV1, discountBps must be less than or equal to the current 5-bps protocol fee. A larger discount fails validation and reverts instead of clamping the fee to zero.

Important: IFR Points are not a token. They have no transfer value and no monetary promise. They only reduce the protocol fee on a single swap.

Contract Address (Mainnet)

0x4807B77B2E25cD055DA42B09BA4d0aF9e580C60a — Etherscan