Deployment & Addresses

Contract addresses, deployment order, constructor arguments, and post-deploy verification for the Inferno protocol.

1. Sepolia Contract Addresses

All contracts are deployed and verified on the Sepolia testnet. Click any address to view it on Etherscan.

2. Mainnet Addresses

Mainnet deployment pending. Addresses will be published here after launch.

3. Deployment Order (10-Step CFLM)

The Inferno protocol follows a strict 10-step Community Fair Launch Model (CFLM) deployment sequence. Each step must complete before the next begins.

1
Deploy InfernoToken
poolFeeReceiver = deployer — 1,000,000,000 IFR (1B) minted to deployer wallet.
2
Deploy LiquidityReserve
6-month lock period, 50M IFR per quarter release schedule.
3
Deploy Vesting
12-month cliff, 36-month linear vesting, 150M IFR total allocation.
4
Deploy BurnReserve & BuybackVault
BurnReserve for permanent token burns. BuybackVault with 60-day activation delay.
5
(BurnReserve already deployed in Step 4)
Both contracts deployed together in the previous step for atomic consistency.
6
Deploy Governance
48-hour timelock for all governance proposals. Guardian set to deployer initially.
7
Deploy PartnerVault
Mainnet params: rewardBps=1500 (15%), annualEmissionCap=4M IFR, admin=Governance, guardian=deployer.
8
Set feeExempt for all contracts + deployer
Exempt all protocol contracts including PartnerVault and deployer from transfer fees. CRITICAL: PartnerVault must be feeExempt BEFORE any IFR transfer to it — otherwise ~3.5% of the 40M transfer is lost to fees (1.4M IFR on Sepolia).
9
Distribute tokens
200M → LiquidityReserve • 150M → Vesting • 150M → Treasury • 60M → Community & Grants • 40M → PartnerVault (fee-free after Step 8) • 400M remains with deployer for LP pairing.
10
Remove deployer feeExempt
Deployer fee exemption is revoked. All transfers now subject to the standard fee structure.

4. Post-Deploy Steps

After the 10-step deployment, the following operations complete the protocol setup.

LP Pairing

npx hardhat run scripts/create-lp.js --network sepolia

Creates the IFR/WETH liquidity pair on Uniswap V2, adds initial liquidity from the 400M IFR allocation.

Ownership Transfer

token.transferOwnership(governance.address)

Transfers InfernoToken ownership to the Governance contract. After this, the deployer has no direct control over the token.

IFRLock Deploy

npx hardhat run scripts/deploy-lock.js --network sepolia

IFRLock is a core protocol component deployed as part of the standard sequence. Its feeExempt status must be set via Governance proposal after ownership transfer to the Timelock. Without fee exemption, unlock() will fail because transfer fees cause the contract to hold fewer tokens than recorded.

5. Constructor Arguments

These are the exact constructor parameters used for the Sepolia deployment. All token amounts use 9 decimals.

Contract Constructor Parameters
InfernoToken deployer (poolFeeReceiver)
LiquidityReserve token, 15552000 (180 days), 50000000000000000 (50M × 1e9), 7776000 (90 days), deployer (guardian)
Vesting token, deployer (beneficiary), 31536000 (365 days), 126144000 (4 × 365 days), 150000000000000000 (150M × 1e9), deployer (guardian)
BurnReserve token, deployer (guardian)
BuybackVault token, burnReserve, deployer (treasury), deployer (router placeholder), deployer (guardian), 5184000 (60 days)
Governance 172800 (48 hours), deployer (guardian)
IFRLock token, deployer (guardian)

Note: On mainnet, the deployer placeholder addresses (treasury, router, beneficiary) will be replaced with the actual multisig and protocol addresses.

6. Etherscan Verification

All contracts should be verified on Etherscan after deployment. Use the Hardhat verify plugin with the exact constructor arguments used during deployment.

npx hardhat verify --network sepolia CONTRACT_ADDRESS CONSTRUCTOR_ARGS...

Example for InfernoToken:

npx hardhat verify --network sepolia \
  0x3Bd71947F288d1dd8B21129B1bE4FF16EDd5d1F4 \
  0x5Ecc668eab04C5bee81b5c7242e1077c946dE406

Example for Governance:

npx hardhat verify --network sepolia \
  0x6050b22E4EAF3f414d1155fBaF30B868E0107017 \
  172800 \
  0x5Ecc668eab04C5bee81b5c7242e1077c946dE406

Tip: If verification fails with "Already Verified", the contract source is already published. You can check by visiting the contract address on Etherscan.

7. Post-Deploy Checklist

Current status of all deployment and post-deployment tasks for the Sepolia testnet.

Task Status
Deploy 9 repo contracts + create LP Pair Done
Etherscan verification (9/9 repo contracts) Done
LP pairing (Uniswap V2) Done
BuybackVault router set Done
Ownership transferred to Governance Done
Governance Proposal #0 executed Done
IFRLock deployed + Proposal #1 created Done
Governance Proposal #1 executed (setFeeExempt IFRLock) Done
PartnerVault v2 deployed + verified (0x5F12...490A39) Done
Governance Proposal #2 cancelled (old PartnerVault) Done
Governance Proposal #3 (setFeeExempt new PartnerVault) Done — Executed 26.02.2026
1.4M IFR Top-up to PartnerVault v2 Done — PartnerVault now 40M IFR
Set treasury/community addresses Pending
Proposal #3 — Executed 26.02.2026
setFeeExempt(PartnerVault v2, true) executed via Governance Timelock.
1.4M IFR Top-up completed — PartnerVault now holds 40,000,000 IFR (4%).
TX: 0x3f28690a...57de6e8