Community Bootstrap Event

Plan B — Treasury + Community Safe Funding. No team ETH. No presale. Pure community price discovery.

Why Plan B?

Funding Breakdown

* The earlier Community EOA → Community Safe migration sent 60M IFR and delivered 57.9M after the 3.5% transfer fee. That was a separate migration. Bootstrap funding itself arrived in three transfers: 144.75M + 50M + 5.25M IFR.

How It Works

Step 1 — Contribute ETH

During the 90-day bootstrap window, anyone can contribute between 0.01 and 2 ETH by calling contribute() on the BootstrapVaultV3 contract. You can contribute multiple times up to the 2 ETH maximum per wallet. Your contribution is recorded on-chain and visible in real time.

Step 2 — Finalise

After the 90-day window closes, anyone can call finalise(). This is permissionless — no admin needs to trigger it. The contract automatically:

• Uses IFR from its balance for LP pairing (pre-funded by Treasury & Community Safe)
• Pairs all contributed ETH with the IFR to create the Uniswap V2 LP
• Retains the LP tokens in BootstrapVaultV3 because the Mainnet Team.Finance locker was disabled; the vault exposes no LP withdrawal function

Step 3 — Claim IFR

After finalisation, each contributor calls claim() to receive their IFR share. Your share is proportional to your ETH contribution:

your_IFR = (your_ETH / total_ETH) × IFR_in_vault

Pricing

The IFR start price is determined organically by total ETH raised. There is no fixed price — the community decides through participation.

IFR price (ETH) = total_ETH_raised / IFR_in_vault

Example Scenarios

ETH Target Scale

* These are community reference targets, not hard caps or soft caps. The LP is always created regardless of ETH raised.

Smart Contract

Security

• nonReentrant on all state-changing functions (OpenZeppelin ReentrancyGuard)
• No admin keys — all parameters immutable at deployment
• No pause, no admin withdraw — fully trustless (V3 adds permissionless refund() after 30-day grace period)
• Reviewed in Security Audit (8 PASS, 2 WARN, 0 FAIL)
• 30 focused BootstrapVaultV3 tests in the canonical contract suite

Participate

LP Custody

On Mainnet, Team.Finance was not configured: teamFinanceLocker is the zero address and lpLockId is zero. The LP tokens created by finalise() therefore remained in BootstrapVaultV3. This means:

• BootstrapVaultV3 exposes no LP withdrawal or recovery function
• The team has no contract path to remove the retained LP
• Custody is verifiable directly from the LP-token balance of BootstrapVaultV3

Parameters

Timeline

Token Distribution Timeline

FAQ

Can I contribute more than 2 ETH?

No. The maximum is 2 ETH per wallet. This is an anti-whale measure to ensure fair distribution. The limit is enforced on-chain and cannot be bypassed.

What happens if very little ETH is raised?

The LP is always created, regardless of ETH amount (no soft cap). Less ETH means a lower IFR price and shallower liquidity. The bootstrap succeeds even with a single contributor.

Can I get my ETH back?

Yes, under specific conditions. If finalise() has not been called within 30 days after the bootstrap window closes, contributors can call refund() to reclaim their full ETH contribution. This is a V3 safety mechanism to protect contributors if LP creation is delayed. Once finalised, all ETH is in the LP and cannot be withdrawn.

When is the Bootstrap Event?

The Bootstrap Event ran from 07.03.2026 to 05.06.2026 and is now finalized. finalise() was executed on 05.06.2026 23:51 UTC (Block 25254575, TX 0x949848bd…). IFR is now tradeable on Uniswap V2 ↗.

How much IFR will I receive?

Your claim is calculated as (your_ETH / total_ETH) × 100,000,000 IFR. The other 100M IFR funded the LP side. For example, if total ETH raised were 10 ETH and you contributed 1 ETH, the 10% claim would be 10,000,000 IFR.

Who can call finalise()?

Anyone. The finalise() function is fully permissionless. After the 90-day window closes, any Ethereum address can trigger it. The result is identical regardless of who calls it.

Announcement Channels

• X (@IFRtoken) — Launch announcements and weekly updates
• Telegram Announcements — Official announcements (read-only)
• Telegram Community — Community discussion
• GitHub Discussions — Technical Q&A
• GitHub Repository — Full source code (open source)

What Happens After Bootstrap Finalise?

The Problem — Low Liquidity

Pool after finalise() used the actual 0.030 ETH raised:

• Initial LP: 100M IFR + 0.030 ETH
• Current pool snapshot 16.06.2026: 0.083261656 ETH + 36.128M IFR
• Liquidity is still thin; contributor buys, voluntary locks, and lending offers remain the immediate stabilization steps

The Solution — 3 Layers of Protection

Layer 1: CommitmentVault (Contributor Lock)

Contributors first buy IFR on Uniswap, then lock 50% of their current IFR balance in CommitmentVault with LOCK_BPS=5000. The current operational plan uses 10 TIME_ONLY tranches with a 30-day unlock; the remaining 50% is reserved for LendingVault offers.

Historical snapshot 16.06.2026: C1/C2/C3 had claimed, but no contributor locks or LendingVault offers existed yet. Current follow-up 30.07.2026: all three contributors completed their CommitmentVault locks and LendingVault offers; three offers provide 52,155,440.952845656 IFR, with 0 IFR lent. LendingVault V1 borrowing remains intentionally disabled with ifrPriceWei = 0.

Layer 2: LendingVault (Organic Buy Pressure)

Contributors can offer IFR through LendingVault. Mainnet V1 borrowing remains intentionally disabled while ifrPriceWei = 0. If activated in a future audited design, repayment may require a borrower to acquire IFR externally; V1 liquidation itself performs no Uniswap purchase and instead distributes ETH collateral between the liquidator and lender.

Layer 3: LP Reserve Safe (Team)

400.6M IFR secured in Gnosis Safe 3-of-5. Added only by governance-controlled decisions; no automatic reserve addition has executed.

• Milestone 1 (pool 1 ETH): +50M IFR
• Milestone 2 (pool 5 ETH): +100M IFR
• Milestone 3 (Sept 2026): initial LiqRes lock ended; Governance has not proposed or executed a withdrawal

Why This Works With Low Initial Liquidity

1. CommitmentVault → no dump
2. LendingVault → organic buy pressure
3. LP Reserve Safe → added at milestones
4. System is self-reinforcing