Ethereum Mainnet access layer

Lock IFR. Unlock access. Verified on-chain.

Inferno Protocol turns IFR into reusable access infrastructure: holders lock once for product access, builders verify lock status on-chain, and standard non-exempt transfers reduce supply.

Build with IFR View verified contracts
MetaMask Rainbow Trust Wallet Coinbase OKX WalletConnect
Network Ethereum Mainnet
Token No mint path
Transfer 2.5% standard burn
Market Uniswap V2 live

One protocol, four doors

Use IFR where access and contribution need proof.

The Web3 page should stay light: one clear action surface for holders, one entry point for builders, and proof for developers who want to verify the system.

Lock once. Use across the ecosystem.

Holders can connect, check IFR balance, use the simple IFRLock access lock, manage CommitmentVault tranches, and withdraw retired LendingVault V1 offers without hunting through the full documentation tree.

Buy IFR Use IFR Benefits Track pool
  • Check wallet, IFR balance, and lock state.
  • Buy IFR on the live Uniswap V2 pool.
  • Use IFRLock for simple access or CommitmentVault for tranches; LendingVault V1 is retired (withdraw only).

Token flow

A smaller, clearer path than the old live tracker.

The new Web3 landing focuses on actions that are live or directly verifiable: buy, lock, verify, build.

01

Buy IFR

IFR is live on Ethereum through the Uniswap V2 pool. The page links users directly to the configured token output.

02

Lock for access

IFRLock is the simple refundable access lock. CommitmentVault holds time tranches: new locks in V2 (time only), existing tranches in V1.

03

Build on proof

Builders can check lock status, set product thresholds, and route users into IFR-powered access flows.

Builder layer

Give products an on-chain access primitive without rebuilding token logic.

IFR Protocol already has the token, lock contract, lending contract, governance, and public documentation. The Web3 landing should act as the clean front door for integrations, not a second wiki.

Access checks Read locked IFR and map it to product tiers or partner policy.
Builder onboarding Point teams to the integration spec, verified contracts, and SDK starter.
Usage alignment Builders can design access around real user participation instead of recurring fees.
Asset-ready The current hero uses a static optimized image. Any future motion asset requires a separate performance and accessibility review.

Start with a wallet check, then move into the flow that fits.

Holders can buy or lock IFR. Builders can start from the integration docs. Developers can verify contracts and inspect the protocol surface before integrating.

Open builder docs Verify contracts