FAQ

Inferno is a deflationary ERC-20 token on Ethereum with a fee-on-transfer mechanism. Every transfer permanently burns 2.5% and routes 1% to a pool fee receiver. The token powers a lock-to-access model where users lock IFR to gain premium features in partner products.

Deflationary means the total supply decreases over time. Every IFR transfer burns 2.5% permanently — those tokens are sent to the zero address and can never be recovered. There is no mint function, so supply can only go down. Starting from 1 billion IFR, the circulating supply shrinks with every transaction.

Locking means your tokens are held in a smart contract to prove commitment — you can unlock at any time with no penalties or cooldown. There are no yield rewards for locking. Staking typically involves earning rewards over time and may have lock-up periods. IFR uses locking for access verification, not yield generation.

IFR uses 9 decimals as a deliberate design choice for the token's intended use case. This provides sufficient precision for fee calculations and lock amounts while keeping numbers more human-readable. One IFR equals 1,000,000,000 base units (1e9).

No. Inferno follows a Community Fair Launch Model (CFLM) — no presale, no venture capital, no seed round. All 1 billion IFR tokens are distributed at deployment: 40% to DEX liquidity, 20% to the liquidity reserve, 15% to the team (vested over 36 months with a 12-month cliff), 15% to treasury, 6% to community grants, and 4% to the partner ecosystem.

Open MetaMask, click “Import Tokens”, and paste the IFR contract address. Set decimals to 9. Make sure you are connected to the correct network (Sepolia for testnet, Ethereum mainnet after launch). The official contract address is published in the project documentation.

Call the lock(amount, lockType) function on the IFRLock contract. The lockType is a string tag identifying which partner product you are locking for. You can also use the Token Dashboard which provides a graphical interface for locking. Your tokens move from your wallet into the contract and can be unlocked at any time.

Your tokens are held in the IFRLock smart contract. No one — not the team, not governance, not any admin — can access or move them. They remain yours. Partner products verify your lock on-chain via isLocked(wallet, minAmount) and grant access based on the result.

Yes. There is no lock-up period, no cooldown, and no penalty for unlocking. Call unlock() and your full locked amount returns to your wallet instantly. The IFRLock contract is fee-exempt, so no transfer fees are deducted during lock or unlock operations.

The minimum lock amount depends on the partner product. Each partner sets their own tier requirement. Typical tiers are 500, 1,000, 5,000, or 10,000 IFR. The IFRLock contract itself has no hardcoded minimum — it accepts any non-zero amount.

The transfer fee powers the deflation mechanism: 2.5% is permanently burned (supply decreases with every transfer) and 1.0% flows into the BuybackVault (strengthens liquidity). IFR is not a trading token — users lock once and use benefits permanently. Transfers are rare (buy, lock, unlock), not daily. For protocol-internal operations (Lock, Unlock, Rewards), fee-exempt status applies — zero fees.

IFRLock, LiquidityReserve, BuybackVault, BurnReserve, and PartnerVault are fee-exempt. This ensures internal protocol transfers (lock, unlock, reward payouts) incur no fees. The exemption list is on-chain transparent and only changeable via Governance proposals with a 48-hour timelock. The full status is documented in the Transparency Report.

The BuybackVault collects the 1% pool fee from every transfer. After a 60-day activation delay, it uses Uniswap V2 to buy back IFR with accumulated ETH. 50% of bought-back tokens are burned permanently, 50% go to the treasury. This creates additional buy pressure and deflation. The vault has a cooldown period between buybacks and a 5% maximum slippage setting.

Yes. IFR works on Uniswap V2. Users should set slippage to at least 4% (3.5% fee + AMM slippage). The FeeRouter contract provides optimized routing with correct parameters. Fee-on-transfer tokens are fully DEX-compatible but require CEX coordination for centralized listings, which is planned for Phase 2+ after mainnet.

The Benefits Network connects IFR lockers with partner businesses. Users lock IFR tokens, and partner products check the lock status on-chain to grant premium access. Partners earn Creator Rewards from the PartnerVault for each locking user. It is a two-sided marketplace built on verifiable on-chain data.

Each partner defines their own tiers. A typical structure might be: Basic (500 IFR), Standard (1,000 IFR), Premium (5,000 IFR), VIP (10,000 IFR). The partner calls isLocked(wallet, minAmount) with the tier threshold and grants features accordingly.

Partners call the read-only function isLocked(walletAddress, minimumAmount) on the IFRLock contract. It returns true or false. This is a single on-chain call with no API keys, no user databases, and no privacy concerns. The partner never needs to store wallet addresses.

Partners register through the onboarding process described in the Business Onboarding documentation. After registration, a governance proposal adds the partner to the PartnerVault. Partner tiers range from Launch Partners (up to 5M IFR allocation) to Tier 3 (500K IFR). All allocations are milestone-based and vested.

When a user locks IFR for a partner's product, the partner earns a percentage of the lock amount from the Partner Ecosystem Pool (40M IFR). The reward rate is governance-controlled with hard bounds of 5–25% (policy target 10–20%). Rewards vest over 6–12 months. The system is designed to always remove more IFR from circulation than it distributes.

The FeeRouter is a smart contract that processes protocol fees on IFR swaps. The default fee is 0.05% (5 basis points) — significantly lower than standard DEX fees. It supports EIP-712 signed vouchers for fee discounts and has a governance-enforced hard cap of 0.25% (25 bps).

IFR Points are off-chain loyalty rewards earned through real actions in the ecosystem (wallet setup, token import, lock guide). At 100 points, you receive a one-time discount voucher for the FeeRouter. Points are NOT a token — they are not transferable, have no trading value, and cannot be sold.

Points are awarded for five event types: wallet connection, token import, completing the lock guide, first lock, and referral. Each event type has a daily limit to prevent abuse. Points are tracked off-chain in the Points Backend using SIWE (Sign-In with Ethereum) authentication.

Points can be redeemed for a one-time protocol fee discount voucher when you reach 100 points. The voucher is EIP-712 signed, tied to your wallet address, and valid for a single FeeRouter swap. There are no other current uses for points — and there are no promises of future uses.

No. IFR Points are purely off-chain data stored in a database. They exist on no blockchain, cannot be transferred between wallets, have zero monetary value, and are not tradeable. They serve one purpose: qualifying for a single-use protocol fee discount. This is intentional to avoid regulatory ambiguity.

The Governance contract is a timelock governor. The owner creates proposals (encoded function calls on target contracts). Each proposal must wait the full delay period (default 48 hours) before it can be executed. This gives the community time to review and the Guardian time to cancel if needed.

The timelock is a mandatory waiting period between proposal creation and execution. The default delay is 48 hours, configurable between 1 hour and 30 days via self-governance (the Governance contract must propose a change to itself). This prevents instant parameter changes and gives stakeholders time to react.

Currently, only the Governance owner can create proposals. The governance model follows a phased approach: Phase 0 (single EOA), Phase 1–3 (multisig with increasing signers), Phase 4 (full DAO with token-weighted voting). Each phase increases decentralization while maintaining operational capability.

Governance can change fee rates (sender burn, recipient burn, pool fee), fee exemptions, the pool fee receiver, guardian address, timelock delay, PartnerVault parameters (reward rate, emission cap, authorized callers), and FeeRouter parameters (protocol fee, voucher signer, fee collector). All changes require the full timelock delay.

The total supply (no mint function exists), the 9-decimal precision, the maximum fee cap (5% hardcoded), the FeeRouter fee cap (0.25% hardcoded), and the token name/symbol. These are immutable by design — no governance proposal, no admin action, and no upgrade can modify them.

The protocol has undergone Slither static analysis (0 high/critical findings), an independent ChatGPT audit (7/7 PASS), and has 361 automated tests with 99% statement coverage. A professional third-party audit by an established firm is planned before mainnet launch.

The project has a Responsible Disclosure policy documented in SECURITY_POLICY.md. Critical bugs should be reported privately via GitHub Security Advisory. The Guardian can pause contracts and cancel governance proposals in emergencies. The patch process follows a documented 6-step procedure with severity classification.

The IFRLock contract uses OpenZeppelin's ReentrancyGuard and Pausable patterns. Your locked tokens cannot be accessed by any admin, team member, or governance action. The contract is fee-exempt, so the exact amount you lock is the exact amount you get back when unlocking. Only your wallet can call unlock().

No. After ownership transfer to the Governance contract, the deployer has no direct control over any protocol contract. Locked tokens are controlled solely by the locking wallet. The Governance contract can change parameters (fees, exemptions) but cannot move user funds. There is no upgrade proxy — contracts are immutable once deployed.

The Guardian is a separate role from the owner, designed for emergency response. The Guardian can cancel any pending governance proposal before execution and can pause contracts via the Pausable pattern. The Guardian cannot create proposals, execute proposals, or access user funds. It is a safety mechanism, not an admin backdoor.