← Inferno

Protocol Plan

Complete architecture of the IFR Protocol — how every wallet, contract, and mechanism works together. Written for transparency: every decision, every trade-off, every scenario documented.

1. What is IFR?

Inferno (IFR) is a deflationary ERC-20 token on Ethereum Mainnet. Every standard transfer between non-exempt addresses automatically burns 2.5% of the amount — permanently. An additional 1% goes to the protocol fee pool. There is no mint() function. Supply can only decrease, never increase.

Transfer Fee Breakdown — sending 10,000 IFR
9,650 IFR → Recipient (96.5%)
200 IFR burned (2.0% sender)
50 IFR burned (0.5% recipient)
100 IFR → BuybackController (1.0% pool fee)
Total burned per transfer: 250 IFR (2.5%)

The Lock Mechanism

IFR serves as a universal access token. Users lock IFR in the IFRLock contract to gain premium access to any product that integrates the lock check, without a recurring subscription. Access remains active while the product-required IFR stays locked and that integration remains available. No renewal. While tokens are locked, the holder gets access. Unlocking is always possible — no penalty, no forced lock period.

2. All Wallets & Contracts

Every IFR token can be traced on-chain. Here is where every token lives, who controls it, and what it is for.

🚀 LP Reserve Safe (3-of-5)
0x5D93E7919a71d725054e31017eCA86B026F86C04

Holds 400.6M IFR (40%) reserved for Uniswap V2 liquidity. Gnosis Safe 3-of-5 multisig (same 5 signers as Treasury and Community Safes). Transferred from Deployer EOA on 18.03.2026. Tokens will be paired on Uniswap via phased LP releases (see Section 4).

400.6M IFR Gnosis Safe 3-of-5
🏛 Treasury Safe
0x5ad6193eD6E1e31ed10977E73e3B609AcBfEcE3b

Protocol treasury controlled by Gnosis Safe multisig (3-of-5 active). Originally held 150M IFR — 144.75M initial funding plus a 5.25M top-up transferred to BootstrapVaultV3 (Plan B). Current balance: 0 IFR. No deployed mechanism automatically refills this Safe.

0 IFR 3-of-5 Multisig
👥 Community Safe
0xaC5687547B2B21d80F8fd345B51e608d476667C7

Community operations wallet. Originally 60M IFR (57.9M received after 2.1M burned on transfer — Community EOA was not fee-exempt at migration time). 50M contributed to Bootstrap Plan B. ~7.9M permanent reserve for bug bounties, grants, ecosystem incentives, DAO seed funding.

~7.9M IFR 3-of-5 Multisig
🔥 Bootstrap Vault V3 LIVE
0xf72565C4cDB9575c9D3aEE6B9AE3fDBd7F56e141

Holds ~200M IFR for the Bootstrap Event. When contributors send ETH, this contract holds it. After the event closes (June 5, 2026), anyone calls finalise() to create the Uniswap V2 LP. Fully trustless — no admin can touch the funds. If not finalized, contributors reclaim ETH after 30-day grace period. IFR in this vault cannot be withdrawn by anyone.

200M IFR Permissionless
💧 Liquidity Reserve
0xdc0309804803b3A105154f6073061E3185018f64

The initial lock on 200M IFR (20%) ended 01.09.2026. All 200M IFR remains in the smart contract. Governance may withdraw at most 50M IFR per 90-day period under the current cap; no withdrawal or LP deployment has executed.

200M IFR Held · 50M / 90-day cap · 0 withdrawn
⏳ Team Vesting Contract (the vault)
0x2694Bc84e8D5251E9E4Ecd4B2Ae3f866d6106271

Smart contract holding 150M IFR (15%). 12-month cliff (zero tokens released before March 2027), then linear release over 36 months until March 2030. Tokens are locked in this contract — not accessible until the cliff ends.

Beneficiary (who receives tokens after cliff):
0x04FABC52c51d1F8ced6974E7C25a34249b1E6239 — held by the Core Developer as trustee on behalf of the entire team. The 150M IFR represents the collective team allocation. Usage decisions (reinvestment, compensation, or other purposes) are made collectively. All claims publicly announced via official governance channels. Currently: 0 IFR (cliff not reached).

Planned (Option B, after March 2027): New multisig vesting contract with Gnosis Safe as beneficiary — placing the team allocation under shared 3-of-5 control. Migration executed transparently.

150M IFR Cliff: Mar 2027
🏗 PartnerVault (Builder Ecosystem)
0xc6eb7714bCb035ebc2D4d9ba7B3762ef7B9d4F7D

40M IFR (4%) for partner rewards, not active yet. Pilot partners will be paid only for verified checkout redemptions, valued in EUR, within a fixed per-partner budget, vesting 6–12 months. No refill.

40M IFR On-chain cap: 4M/year on lock rewards; milestones capped per partner allocation
♻️ 🔥 BuybackVault + BurnReserve
0x670D...F812 | 0xaA14...6fCF

BuybackVault is a separate ETH-to-IFR buyback contract whose configured execution splits bought IFR between BurnReserve and Treasury. BuybackController separately accepts ETH and implements the 50/50 burn/LP path described below. Neither contract refills PartnerVault. BurnReserve destroys received IFR only when burn() is called.

0 IFR (fills after LP) Governance
⚖ Governance (Timelock)
0xc43d48E7FDA576C5022d0670B652A622E8caD041

Protocol proposals go through this contract with a mandatory 48-hour Timelock. Untimelocked exceptions: owner-only guardian rotation through setGuardian and transferring the deployed Governance contract’s ownership through owner-only setOwner (tracked as CWA-25). Governance owns InfernoToken.

48h Timelock 7 proposals

3. The Bootstrap Event

The Bootstrap Event is how IFR gets its initial Uniswap liquidity. Instead of the team funding the LP themselves (Plan A — centralized financial risk), the community contributes ETH and receives IFR pro-rata. 100% of ETH goes into the Uniswap liquidity pool. No team ETH is taken.

Bootstrap Timeline
07.03.2026
Contract Deployed
11.03.2026
Vault Funded
05.06.2026
FINALIZED
08.06.2026
Trading live
finalise()
LP Created

How It Works

  1. Bootstrap ENDED 05.06.2026 23:51 UTC ✅ — Contributors contributed 0.01–2 ETH during the 90-day window. Claims open via claim().
  2. finalise() executed 05.06.2026 23:51 UTC — Block 25254575 — LP Token: 0xbE495E9c0d8cc2DCf95570cf95B63c4844dF31A0
  3. finalise() created the Uniswap V2 IFR/ETH pool with all raised ETH + 100M IFR and reserved 100M IFR for contributor claims
  4. Mainnet Team.Finance locker was disabled; LP tokens remain in BootstrapVaultV3, which exposes no LP withdrawal function
  5. Contributors claim their IFR proportional to their ETH contribution

What If Bootstrap Fails?

If zero ETH is contributed by June 5, the IFR in the vault remains locked permanently (no admin withdrawal function). The team would use the 400M LP Reserve Safe IFR + team ETH to create an initial liquidity pool directly via Governance. See Contingency Plan below.

✅ Scenario A — Success
  • ETH contributed by community
  • finalise() creates LP automatically
  • LP retained in BootstrapVaultV3 with no LP withdrawal function
  • Contributors claim IFR pro-rata
  • IFR tradeable on Uniswap
⚠ Scenario B — Fallback
  • Zero ETH contributed
  • 200M IFR stays locked in vault
  • Team creates LP with LP Reserve Safe IFR
  • Governance Proposal + 48h Timelock
  • IFR tradeable via direct pairing

4. Liquidity Phases

The 400M IFR LP Reserve allocation is not all added to Uniswap at once. Flooding the pool immediately would depress the price and create poor trading conditions. Instead, it is released in 3 phases as trading volume grows.

Executed Bootstrap — 100M
LiqRes cap — 50M
LP Reserve Safe — 400.6M
Phase 1 — Automatic
Executed 05.06.2026. 100M IFR + 0.030 ETH → Uniswap V2 LP. Team.Finance disabled; LP retained in withdrawal-less BootstrapVaultV3.
Phase 2 — Governance
Not scheduled. The initial LiqRes lock ended 01.09.2026, but the current cap is 50M IFR per 90 days. A 100M phase would require at least two periods or a separately proposed cap change, plus Governance proposal, 48h timelock and a distinct LP action.
Separate LP Reserve Safe
400.6M IFR is held separately by the 3-of-5 LP Reserve Safe. No fixed future tranche schedule is approved; any use requires an explicit Safe/governance decision and proportional counter-asset planning.
Iron rule: ETH in the liquidity pool is never withdrawn by the team. The initial liquidity's LP tokens are held by BootstrapVaultV3, which has no withdrawal function — permanently locked. LP tokens created later by the BuybackController go to TreasurySafe (governed, not locked).

5. The Buyback Mechanism

The deployed BuybackController implements an ETH-to-IFR market buyback plus an attempted liquidity addition. It has no PartnerVault refill, operating-pool, SOS-reserve or 12-day voting path. The controller is deployed and governance-owned, but the execution path is dormant while its native-ETH threshold is not met.

Fee Flow
FeeRouterV1 native-ETH fee or direct ETH
→
BuybackController
→
50% ETH buys IFR → BurnReserve
50% ETH + held IFR → LP receiver

BuybackController (Phase 3 — Deployed)

BuybackController was deployed on 14.04.2026, before the LP launch, and governance-wired through Proposals #13 and #14. Execution is permissionless only when the controller is unpaused, its native-ETH balance reaches minTriggerAmount, and the cooldown has elapsed. It is not an unconditional timed automation.

1. Trigger check
Requires an unpaused controller, elapsed cooldown and enough native ETH.
2. Burn half
50% of ETH buys IFR on Uniswap and sends the output to BurnReserve.
3. LP half
The remaining ETH attempts to pair with IFR already held by the controller; LP tokens go to lpReceiver.
4. Fallback
If no IFR is available or adding liquidity fails, the remaining ETH also buys IFR for BurnReserve.
BuybackController ETH allocation before fallback
50% Buy IFR → BurnReserve
50% Attempt LP

6. Governance

Governance proposals use the mandatory 48-hour timelock, giving the community time to review. The untimelocked exceptions: TreasurySafe 3-of-5 can call setGuardian and, on the deployed Governance contract, setOwner (tracked as CWA-25) without the timelock. The Guardian (TreasurySafe since 03.10.2026) can cancel proposals during the timelock window. The Governance Owner is TreasurySafe 3-of-5 (since 20.03.2026).

Multisig Signers

# ID Address Status
1G.M.0x6b36...ed67Active
2M.G.0x17F8...72d4Active
3A.M.0x0c48...ED74Active
4Y.K.0xA086...b275Active
5A.P.0x32cF...0fE9Active

7. Contingency Plan

If the Bootstrap receives zero ETH by June 5, the protocol has a clear fallback. No IFR is lost — the 400M LP Reserve Safe allocation remains available as emergency liquidity.

0 ETH contributed
→
Governance Proposal
→
48h Timelock
→
Direct LP Creation

8. Token Distribution

1B IFR
● 40% DEX Liquidity (400M)
● 20% Liquidity Reserve (200M)
● 15% Team Vesting (150M)
● 15% Treasury (150M)
● 6% Community & Grants (60M)
● 4% Partner Ecosystem (40M)
Unlock Timeline
March 2026Bootstrap opened — 200M IFR in vault✅ Done
June 2026Bootstrap finalized — LP created via finalise()✅ Done
Sep 2026Initial LiquidityReserve lock ended — 200M IFR still held, 50M current staged capacityNo withdrawal
March 2027Team Vesting cliff ends — linear release beginsLocked
March 2030Team Vesting fully vestedLocked

9. Known Issues & Open Points

Full transparency means documenting what is not yet perfect.

DONE feeExempt — listed protocol contracts
The vaults, reserves and fee contracts that need fee-free transfers are fee-exempt on-chain via governance proposals; CommitmentVault V2 joined via proposal #17 (executed 4 October 2026). Not every contract is exempt: Governance, BuilderRegistry and the DEX router are not. Verified list (block 26,065,893 plus #17): Fee Design.
DONE Bootstrap Event
Ran 07.03.–05.06.2026 with 200M IFR. Ended 05.06.2026; finalise() executed (block 25254575), LP live on Uniswap V2. See Bootstrap.
DONE Governance → Multisig Transfer
Governance owner transferred to TreasurySafe 3-of-5 on 20.03.2026. TX
DONE Multisig Threshold 3-of-5
3-of-5 active with 5 signers (G.M., M.G., A.M., Y.K., A.P.). Completed 15.03.2026.
PHASE 3 CommitmentVault
V1 (legacy) offered four unlock conditions; its PRICE_ONLY and TIME_AND_PRICE tranches can never unlock (CV-01), while TIME_OR_PRICE tranches still unlock by their time condition. V1 receives no new locks. CommitmentVault V2 (deployed 2 October 2026, fee-exempt since proposal #17) accepts time-only locks and receives all new locks; existing V1 tranches stay listed and unlock through V1. See CommitmentVault.
RETIRED LendingVault
V1 retired by owner decision (3 October 2026): borrowing stays disabled (ifrPriceWei = 0, no activation planned or authorized) and lenders are withdrawing their offers; those IFR are not lost. No V2 is planned until a reviewed price source exists. See LendingVault.
PHASE 3 BuybackController
Deployed 14.04.2026 before LP launch. Since proposal #21 (executed 5 October 2026) it is the InfernoToken pool fee receiver. It can split native ETH between IFR buyback-to-BurnReserve and an LP attempt; it has no PartnerVault refill or overflow-routing mechanism.
PHASE 4 DAO Governance
RatVoting + ForumVoting + IFRSpamProtection. Full on-chain governance. After ecosystem is established.