How This Build Works

What the site actually runs on today: sample data, one live clock, no chain.

Orbit's front end is complete and every rule on these pages is implemented. What sits behind it today is not a chain and not a server: it is a deterministic sample-data layer that lives in the repository.

Nothing here is on-chain yet

No coin, wallet, balance, trade or transaction on this site exists outside the browser. Explorer links are built from generated hashes and will not resolve on Robinscan.

What the “backend” is#

src/lib/config.tsThe protocol rules: fee, split, epoch, modes, graduation threshold, the two tokens. Change a value here and every screen follows.

src/lib/data.tsThe sample universe: 24 coins, their holders, trades, airdrops and the network totals, all derived from the rules above.

src/lib/rng.tsA seeded pseudo-random generator (FNV-1a → mulberry32) and an address generator.

File	What it holds
`src/lib/config.ts`	The protocol rules: fee, split, epoch, modes, graduation threshold, the two tokens. Change a value here and every screen follows.
`src/lib/data.ts`	The sample universe: 24 coins, their holders, trades, airdrops and the network totals, all derived from the rules above.
`src/lib/rng.ts`	A seeded pseudo-random generator (FNV-1a → mulberry32) and an address generator.

There are no API routes, no server actions, no database, no environment variables and no RPC client. Coin and docs pages are generated at build time, one per ticker and slug.

Same input, same output#

Every figure is seeded from a string. hash("APO") produces Apogee's market cap, holder list, trade history and transaction hashes, and will produce exactly the same ones on every machine, on every reload. That is what makes the screens stable enough to design against.

What is live, and what is frozen#

The countdown to the next airdropLive. It is wall-clock time modulo the epoch, so every coin and every tab agrees.

What happens when it reaches zeroNothing. No new airdrop is generated; the countdown simply starts again.

A coin's ageFixed. A coin that launched 9 minutes ago is 9 minutes old on every visit.

Airdrop historyDerived from that fixed age, so the list never grows.

Prices, volume, holdersFixed per coin. Nothing moves between reloads.

Connecting a walletA flag in localStorage. Any wallet in the picker connects the same sample address; nothing is signed and no account is read.

Behaviour	In this build
The countdown to the next airdrop	Live. It is wall-clock time modulo the epoch, so every coin and every tab agrees.
What happens when it reaches zero	Nothing. No new airdrop is generated; the countdown simply starts again.
A coin's age	Fixed. A coin that launched 9 minutes ago is 9 minutes old on every visit.
Airdrop history	Derived from that fixed age, so the list never grows.
Prices, volume, holders	Fixed per coin. Nothing moves between reloads.
Connecting a wallet	A flag in localStorage. Any wallet in the picker connects the same sample address; nothing is signed and no account is read.

How the numbers are built#

Fees. A coin's 24h holder payout is its sample volume × the 2% fee × 70%, converted at the sample ORBIO price. Every other fee figure is derived from that one.
Holders. Between 60 and 500 ranks per coin, weighted by a power law. The listed ranks hold about 78% of supply; the rest is an unlisted tail.
Airdrop history. One entry per epoch since launch, each paying the coin's full set, with an amount jittered around the average.
Your wallet. Rewards reads whichever address you connect, and finds your rank in every coin you hold.

What a production backend still has to do#

Read pons for real coins, balances, volume and bonding progress.
Run the distributor: snapshot balances at each epoch boundary, compute the paid set, and send one transaction per airdrop.
Index payouts per wallet so Rewards and the airdrop feed show real history with real transaction hashes.
Connect wallets properly and sign launches and trades.
Confirm the placeholders: the graduation threshold, and both token supplies and prices.