IGNIS
WHITEPAPER

Overview

Ignis is a deflationary token deployed on the Monad blockchain, built around two fully permissionless on-chain mechanics that anyone can trigger at any time. There is no team multisig controlling the burn engine, no admin function to pause it, and no upgradeable proxy.

The core thesis is simple: the act of burning IGN increases scarcity, and scarcity increases value for remaining holders. Every igniteBurn call permanently removes liquidity from the pool and destroys tokens. Every forgeStability call creates buy pressure against the pool. Both are open to the public.

Ignis is built on Monad for its high throughput and low fees, which make frequent permissionless calls economically viable. Liquidity is provided via PancakeSwap V3 and permanently locked — it cannot be withdrawn by any party.

The protocol operates in three distinct phases tied to how much supply has been burned. During the Early and Mid Game phases, WMON proceeds from each burn are deployed into additional liquidity pools across multiple IGN trading pairs on the Monad ecosystem. Fee revenue generated by price discrepancies between these pools compounds over time, broadening the protocol's economic base. Once 50% of supply is burned — the Late Game — the expansion phase ends and all proceeds shift entirely into IGN buybacks and burns, accelerating deflationary pressure until the system reaches its terminal state at 90% burned.

Token Summary

Architecture

Ignis is composed of three smart contracts that work together as an immutable system.

Core Mechanics

4.1 igniteBurn — The Deflationary Engine

igniteBurn() is the primary deflationary function. It is permissionless — any wallet on any chain can call it once the cooldown has elapsed.

What happens when igniteBurn() is called

1. 01
   Phase check — Reads how many IGN tokens have been sent to address(0). Calculates emberRate = burnedSupply / 1,000,000 IGN. If emberRate ≥ 90, the function permanently reverts with "burns complete".
2. 02
   Cooldown check — Requires block.timestamp ≥ nextBurnTime. Reverts with "burn not ready" if called too early.
3. 03
   Cooldown update — Sets nextBurnTime forward based on the current burn phase.
4. 04
   LP removal — Calls VAULT.claimBurn(), which instructs PancakeSwap to remove exactly 0.5% of remaining liquidity (liquidity / 200). Simultaneously sweeps all accumulated swap fees in the same transaction.
5. 05
   WMON routing — The WMON received is routed based on the current emberRate phase (see Section 5).
6. 06
   IGN burn — Any IGN held by IgnisForge at the end of the call is transferred to address(0) and permanently destroyed.

Each call is strictly rate-limited. The 0.5% removal compounds over time — early calls remove large absolute amounts, later calls remove smaller absolute amounts, but the percentage stays constant.

4.2 forgeStability — The Volatility Mechanism

forgeStability() is a secondary permissionless function with a 1-hour cooldown.

What happens when forgeStability() is called

1. 01
   Cooldown check — Requires block.timestamp ≥ nextChaosTime. Reverts with "chaos not ready" if called too early.
2. 02
   Fee claim — Calls VAULT.claimFees(), pulling any accumulated swap fee revenue from the LP position into IgnisForge.
3. 03
   Balance check — Requires the contract holds at least 1 WMON. If not, reverts with "insufficient MON". Fee revenue from the pool is the primary source.
4. 04
   IGN pre-burn — Any IGN currently held by IgnisForge is immediately burned to address(0).
5. 05
   3-round swap loop — Executes 3 consecutive rounds: buy IGN with the full WMON balance, sell all IGN back for WMON, repeat. Each round uses the contract's full balance, compounding the effect. The 1% pool fee is extracted from the balance each time.

Burn Phase Routing

The WMON received from LP removal in each igniteBurn call is routed differently depending on how much of the total supply has been burned.

The Expansion-to-Burn Lifecycle

The Early and Mid Game WMON routing is not passive team revenue — it funds an active multi-pool liquidity expansion strategy. Each new trading pair (IGN paired against other Monad ecosystem tokens) increases the total volume routed through IGN, generating more swap fee revenue across the board. Price discrepancies between pools attract arbitrage flows, which in turn deepen each pool's fee accrual. By the time the Late Game begins, the protocol has a mature, multi-pair liquidity presence that amplifies the impact of every buyback-and-burn call: orders flow through a liquid market, slippage is minimized, and each IGN purchased is immediately destroyed — maximizing deflationary pressure per WMON spent.

Cooldown Schedule

igniteBurn has a dynamic cooldown that increases as more supply is burned, slowing the rate of burns as the token becomes rarer. The base cooldown is 4 hours. For every 5% of supply burned, an additional 2 hours is added.

forgeStability has a flat 1-hour cooldown regardless of burn phase.

Liquidity Design

Permanent Lock

The LP NFT is transferred into IgnisVault via lockNFT() during deployment. Once locked, there is no function — on any contract — that can withdraw it. The vault has no unlockNFT function. Liquidity is locked permanently by design.

Single-Sided Position

At launch, all 95M IGN is deposited into a single-sided PancakeSwap V3 position. No MON is required at launch — the position covers from the launch tick outward to MAX_TICK. As buyers purchase IGN, MON accumulates in the LP position and swap fees begin accruing.

The 0.5% Removal Rate

Each igniteBurn call removes liquidity / 200 from the position — exactly 0.5% of remaining liquidity, not total original liquidity.

Liquidity asymptotically approaches zero but never reaches it. The removal rate slows naturally as liquidity decreases, and the cooldown increases simultaneously — both mechanisms cooperate to slow the pace of burns as the token matures.

Swap Fees

The 1% fee tier means every swap in the IGN/MON pool generates fee revenue. This revenue accumulates inside the LP position and is claimed by claimFees() (inside forgeStability) or swept alongside the liquidity removal in claimBurn() (inside igniteBurn). All fee revenue flows into IgnisForge as WMON.

Multi-Pool Expansion Strategy

During the Early and Mid Game phases, WMON received by the owner is deployed into additional liquidity pools pairing IGN against other Monad ecosystem tokens. This creates a network of pools where price discrepancies naturally attract arbitrage activity — each arbitrage trade generates swap fees across every pool in the route, compounding total fee revenue beyond what a single pair can produce.

As trading volume grows across these pairs, the primary IGN/MON pool becomes a deeper reference market. When the Late Game begins and WMON is redirected to buybacks rather than new pools, the existing multi-pair presence ensures that buyback orders flow through a mature, liquid market — minimizing slippage and maximizing the deflationary impact of each igniteBurn call.

Token Distribution

The 5% deployer allocation is strictly designated: 2% is reserved to seed new liquidity pools during the expansion phase (once these are exhausted, additional expansion tokens will be purchased from the open market), 1.5% funds ongoing infrastructure maintenance, and 1.5% is allocated for marketing and community incentives.

Launch Parameters

Contract Addresses & Deployment

Ignis Contracts

Monad Infrastructure

Deployment Sequence

1. 01
   Deploy IgnisForge — internally deploys IgnisToken and IgnisVault, mints 100M IGN to deployer, renounces IGN ownership
2. 02
   Create the IGN/MON pool via PancakeSwap V3 Position Manager at the launch price
3. 03
   Approve 95M IGN to the Position Manager
4. 04
   Mint the single-sided LP position (95M IGN, 0 MON)
5. 05
   Approve the LP NFT to IgnisVault, call lockNFT() — liquidity is permanently locked

Security Model

What is Immutable

• ✓
  Total supply is fixed at 100M IGN — no mint function exists after ownership is renounced
• ✓
  LP liquidity can never be withdrawn — IgnisVault has no unlock function
• ✓
  igniteBurn and forgeStability routing logic cannot be changed — no admin overrides
• ✓
  Pool fee, tick range, and swap callback logic are hardcoded constants

What the Owner Controls

The owner address receives WMON payouts during Early and Mid game phases of igniteBurn. These proceeds are deployed into additional IGN liquidity pools across Monad ecosystem trading pairs — growing fee revenue that compounds the protocol's economic base before the Late Game burn engine takes over. Ownership can be transferred via transferOwnership() with no timelock or delay. A compromised owner key only affects payout destination — it cannot access locked liquidity, pause burns, or modify any mechanic.

Tokenomics Summary

Roadmap

Disclaimer

This whitepaper is for informational purposes only and does not constitute financial, investment, or legal advice. IGNIS is a purely experimental, deflationary protocol deployed on the Monad blockchain. Participation in decentralized finance (DeFi) and the acquisition of cryptographic tokens involve significant risk, including the potential loss of all invested capital. The Ignis smart contract system operates autonomously and is immutable; it is not managed, controlled, or influenced by any person or entity. Users assume full responsibility for their interactions with the protocol and should conduct their own thorough due diligence before participating. By interacting with the Ignis smart contracts, you acknowledge and accept these inherent risks.