The clock
The calendar is not a list of dates chosen by anyone. It is a clock that runs on Ethereum block numbers and unlocks each IMO when it reaches the year of the real listing.
- Starts at
- 1979
- Real days per game year
- 3
- Blocks per game year
- 21,600
- One block (12 s)
- ≈ 24 min of history
- Last listing
- 2026
- Axis ends
- 2030
How it is anchored
The clock contract stores the Ethereum mainnet block at which game time started. Game year = start year + (current block − start block) / blocks per year. Contracts on Base read the mainnet block through the chain's L1 block predeploy, so the site and the contracts can never disagree about what year it is. The site itself stores nothing: it reads the start block from the contract and computes the rest.
Until the contract reports a start block, the clock has not started. The site shows 1979 and every countdown is a projection that assumes the clock starts now.
What the clock does and does not do
- It unlocks an IMO when the year arrives. It does not launch it; brokers file prospectuses and backers choose. How an IMO works
- It never runs backwards, skips a year or unlocks out of order.
- It has no owner able to move it forward. Whether it should be possible to pause it is an open question, discussed below.
Pausing: the open question
Should the clock be pausable, so that IMOs stop unlocking if the launchpad is not yet known enough to give them a fair launch? The argument for is obvious: a great IMO wasted on an empty room is a loss for everyone. The arguments against are real too:
- Control. A pause key is an owner. It weakens the claim that nobody controls launches, which matters both for trust and for how regulators view who the offeror is.
- Trust. A discretionary pause looks like a rug lever, even if it can only stop future unlocks and never touch a live pool.
- Predictability. Every countdown on the site becomes a guess, and pauses can be front-run by whoever expects them.
The direction being explored is to replace discretion with a rule. Instead of a pause button, the clock only advances while an objective, onchain readiness condition holds, for example a minimum of ₸USD locked in Turbo staking. Nobody presses anything; if the community behind the launchpad is too small, the calendar waits, and it resumes the moment the threshold is met. If a pause ever exists it will be bounded (maximum duration, maximum number of pauses), governed by stakers rather than the team, and unable to affect any pool already trading. Roadmap