How it works

A coin, a dated event, a clock.

The countdown is shown for context. It does not set or move the price.

Coins can go to zero. Nothing here is financial advice, and no coin promises returns, rewards or utility.

Three steps

01
Pick an event
Choose a tile from our fixed event list. Every tile has a source, a target time and a status. You cannot pin an arbitrary URL.
02
Launch on pump.fun
Name, ticker and image. You sign the create transaction in your own wallet. We never see your keys.
03
Get a coin page
We check the transaction on-chain, then publish a page with the live countdown to the event next to a link to the chart.

Event sources

Seven sources, each read on the server with a 4 s timeout, at most three at a time, cached per source. A source that fails backs off and its last good read is shown as stale. If a source has never answered, its events are not shown.

observed: the target as the source states it
derived: estimated by us from source data
computed: calculated in code, no API
static: copied from an official page, with the date we read it

Launch Library 2

What we read: The next upcoming orbital launches: NET (no earlier than) time, its precision, provider, pad and the status word (Go, TBC, TBD, Hold).
Endpoint: ll.thespacedevs.com/2.3.0/launches/upcoming
Refresh: every 10 min (600 s cache)
Data kind: observed
Caveats: The NET can slip, sometimes by days. We show the slip when the date changes.
Keyless API with a strict rate limit, so we read it at most every 10 minutes.
An outcome (success, failure, partial failure) is shown only when the source states it.

Solana RPC

What we read: getEpochInfo (slots in epoch, slot index) and getRecentPerformanceSamples.
Endpoint: Solana JSON-RPC getEpochInfo
Refresh: every 1 min (60 s cache)
Data kind: derived
Caveats: Epoch end = slots left x average slot time from the last 30 performance samples.
It is an estimate. It moves a little on every read as slot times change.

mempool.space

What we read: The next difficulty adjustment (estimated retarget date, blocks left) and the current tip height.
Endpoint: mempool.space REST API
Refresh: every 5 min (300 s cache)
Data kind: observed
Caveats: Difficulty adjustment time is mempool.space's own estimate.
Halving = blocks left x 10 min, computed by us (derived). Real block times vary, so the date drifts.

Polymarket Gamma API

What we read: Scheduled end dates of a few large open markets from the public Gamma API.
Endpoint: gamma-api.polymarket.com/events
Refresh: every 10 min (600 s cache)
Data kind: observed
Caveats: We show the scheduled end date only. Display only: no odds, no trading, no betting links.
Markets can resolve earlier or later than the scheduled end.
Markets about death, violence or war are skipped.

Computed (Meeus)

What we read: Nothing external. Next new moon, full moon and equinox or solstice, computed in code.
Endpoint: Algorithm notes below
Refresh: Computed, cached 10 min
Data kind: computed
Caveats: About 1 minute accuracy. See the algorithm notes below.

Nager.Date

What we read: The next public holiday for a handful of countries (US, GB, DE, JP, BR, FI), nationwide holidays only.
Endpoint: date.nager.at/api/v3/NextPublicHolidays
Refresh: every 10 min (600 s cache)
Data kind: observed
Caveats: The target is local midnight in the country's capital time zone.

Federal Reserve calendar (static)

What we read: FOMC meeting dates, hard-coded from the official Federal Reserve calendar.
Endpoint: federalreserve.gov FOMC calendars
Refresh: Static list, verified 2026-10-13
Data kind: static
Caveats: Target = 2:00 pm ET on the meeting's last day, the usual statement time. The calendar lists dates only.
2027 dates are tentative until the Fed confirms them.

Sky: the algorithm

Moon phases and seasons are computed in code, with no API. We use Jean Meeus, Astronomical Algorithms, 2nd edition (1998):

Chapter 49, phases of the Moon: the mean phase from the lunation number, plus the periodic and planetary correction terms.
Chapter 27, equinoxes and solstices: the mean instant for the year, corrected by the periodic terms table.
Both give Dynamical Time. We convert to UT with the Espenak-Meeus polynomial for deltaT (TD minus UT, about 75 s in 2026).

Accuracy is about 1 minute. The target is rounded to the second, and the tile says computed.

Status and slips

Scheduled: The target is in the future and has not moved past the threshold.
Slipped: The target moved by more than the threshold since our first stored reading.
Cancelled: The source marks the event cancelled.
Passed: The target time is behind us, or the source reported an outcome. We show an outcome only if the source gave one.

Slips are measured only from our own stored readings. The first reading of an event starts its history; a new reading is stored only when the target moves by at least the threshold. The history on an event or coin page always shows the real window it covers, starting from that first reading.

Launch Library 2: 1 min
Polymarket Gamma API: 1 h

Computed, static and holiday events do not slip, and block-time estimates (Solana epoch end, Bitcoin difficulty adjustment and halving) drift by themselves, so we keep no slip history for them.

Verification of launches

After you sign, your wallet sends the transaction and our server checks it on-chain before the coin gets a page. We store a coin only when all of these hold:

The transaction is confirmed and succeeded.
The fee payer is the creator wallet that started the launch.
The mint address signed the transaction.
The mint is the first account of a pump.fun create instruction in that transaction.

The coin page shows this as a receipt: mint, creator, transaction signature, slot, block time and metadata link, each linked to Solscan or IPFS so you can check it yourself.

What the clock is not