Vesting Schedule
Team allocation — 150M IFR locked for 4 years with a 12-month cliff. Fully on-chain, fully verifiable.
Vesting Contract (Mainnet): 0x2694Bc84e8D5251E9E4Ecd4B2Ae3f866d6106271
Visual Timeline
Current status: Cliff period active. Zero tokens have been released. The first tokens become claimable in March 2027.
How the Vesting Contract Works
The Vesting contract uses a simple and transparent mechanism:
- Months 0–11 (Cliff):
vestedAmount()returns 0. No tokens can be claimed. - Month 12 (Cliff End): Vesting calculation begins. At exactly the cliff boundary, vested amount is still 0.
- Months 13–48 (Linear): Tokens vest linearly.
vestedAmount = totalAllocation * (elapsed - cliff) / (duration - cliff) - Month 48+ (Complete):
vestedAmount()returns the full 150M IFR.
Only the designated beneficiary can call release() to claim vested tokens. The guardian can pause releases in an emergency but cannot redirect or withdraw tokens.
Release Schedule
| Date | Month | Event | Release | Cumulative |
|---|---|---|---|---|
| 05 Mar 2026 | 0 | Mainnet Deploy | 0 IFR | 0 IFR |
| 05 Sep 2026 | 6 | Cliff | 0 IFR | 0 IFR |
| 05 Mar 2027 | 12 | Cliff End | 0 IFR | 0 IFR |
| 05 Apr 2027 | 13 | Linear Start | ~4.17M IFR | ~4.17M IFR |
| 05 Sep 2027 | 18 | Linear | ~4.17M / mo | ~25M IFR |
| 05 Mar 2028 | 24 | Linear | ~4.17M / mo | ~50M IFR |
| 05 Sep 2028 | 30 | 50% Vested | ~4.17M / mo | ~75M IFR |
| 05 Mar 2029 | 36 | Linear | ~4.17M / mo | ~100M IFR |
| 05 Sep 2029 | 42 | Linear | ~4.17M / mo | ~125M IFR |
| 05 Mar 2030 | 48 | Fully Vested | ~4.17M IFR | 150M IFR |
Contract Parameters
| Parameter | Value | Description |
|---|---|---|
token |
0x77e9...7B | InfernoToken (IFR) |
beneficiary |
0x04FA...6239 | Core Developer wallet — trustee for team (immutable). Option B: migrate to multisig vesting after cliff (March 2027). |
cliffDuration |
31,536,000 | 365 days in seconds |
duration |
126,144,000 | 1,460 days (4 years) in seconds |
totalAllocation |
150,000,000 * 109 | 150M IFR (9 decimals) |
guardian |
0x6b36...67 | Can pause/unpause (transferable) |
paused |
false | Releases are active |
released |
0 | No tokens released yet |
Verify On-Chain
Anyone can verify the vesting parameters by calling read functions on Etherscan:
// Call vestingSchedule() on the Vesting contract
// Returns: (start, cliffDuration, duration)
start: 1741168424 // Mar 5, 2026 (Unix timestamp)
cliffDuration: 31536000 // 365 days
duration: 126144000 // 1,460 days
// Call these view functions:
totalAllocation() // 150,000,000,000,000,000 (150M * 1e9)
released() // 0 (nothing claimed yet)
beneficiary() // 0x04FABC52c51d1F8ced6974E7C25a34249b1E6239
vestedAmount() // 0 (cliff not reached)
releasableAmount() // 0 (nothing to claim)Transparency: The Vesting contract source code is verified on Etherscan. All parameters are immutable and set at deployment — they cannot be changed by anyone.
Security Features
- Immutable beneficiary — Cannot be changed after deployment
- Immutable allocation — 150M IFR locked, no more can be added
- No admin withdrawal — Only the beneficiary can call
release() - Guardian pause — Emergency brake, cannot redirect funds
- Transferable guardian — Guardian role can be transferred to Multisig/DAO
- Fee-exempt — Vesting contract is exempt from transfer fees
- No reentrancy risk — Simple transfer with checks-effects-interactions pattern
See the Security page and Fair Launch page for more details on how the team allocation fits into the overall token distribution.