THE IDEA

Every fomo thesis on this coin creates an agent that trades the coin. That is the whole idea. The rest of this page is how it is built so that nobody, including the deployer, can touch it.

On fomo.family a thesis is a public bet with a name attached. Someone puts money behind a coin and writes down why. fomolings gives that act a body on chain. The moment a thesis on this coin appears, the program gets a queue entry, and the next hatch turns that entry into a keyless account holding real SOL that buys under the value it was born at and sells above. A thesis is no longer just a post. It is a market maker that exists because of the post and ends when the post closes. Nothing is posted here. This site reads.

THE COIN

The coin is a plain pump.fun launch with a total supply of one billion. Nothing about the token is modified. No tax, no transfer hook, no blacklist, no mint authority. The mechanism lives in the creator fee stream and the program that spends it. If pump.fun stopped paying creator fees the program would keep working on what the vault already holds and on profit shares, and would hatch less often.

THE VAULT

The vault is a program derived address seeded from the word vault and the mint. No key exists for it. The program has no instruction that moves SOL from the vault to any wallet. The only debit is the grant at hatch, and the grant can only go to a freshly created fomoling, which is itself keyless. Anyone can read the vault's counters: SOL in, granted, returned, profit shared, coins burned, hatch count, retire count, queue length, and the value the program last read.

THE WITNESS

The program needs to know when a thesis opens and closes on fomo.family and cannot read that itself. The witness is a key held by the deployment that calls enqueue and retire. It cannot call anything that moves SOL to a wallet, because no such instruction exists. Enqueue writes a small entry that costs the witness rent. Retire sends SOL to the vault and burns coins. If the witness stopped forever, existing fomolings would keep working and nothing new would hatch. If it were malicious, the worst it could do is retire fomolings early, which sends SOL to the vault and burns coins, or queue theses that do not exist, which the theses page would expose because every queue entry carries a thesis id anyone can look up on fomo.family.

HATCHING

Hatch is permissionless and reads no clock. It requires the vault to hold at least the grant and the queue to be non empty. It closes the oldest entry, creates the fomoling, reads the coin's value from the curve or the pool in the same transaction, writes that as the birth value, and transfers the grant. The value read is the spot value implied by the reserves, virtual SOL reserves over virtual coin reserves on the curve or the pool's SOL vault over its coin vault after migration, times total supply, in lamports. A Hatched event carries the birth value and the slot.

THE BAND

Six levels. Bids at birth times 0.98, 0.96 and 0.94. Asks at birth times 1.02, 1.04 and 1.06. Levels are fixed at hatch. Each bid spends one rung, a third of the grant. Each ask sells a third of the coins held at that moment. A tick fills every level the live value has crossed since the last fill, nearest birth first, so a six percent drop in one move fills all three bids in one tick, subject to the impact cap.

THE IMPACT CAP

Before every swap the program computes the impact the swap would have against the live reserves. Over three hundred basis points, the swap is cut to the largest size that stays under the cap and the remainder is recorded as a partial on the rung. The next tick continues it. Fomolings are never the thing that moves the coin by more than a small step, in either direction, and a wall of hatching fomolings absorbs into the market instead of spiking it.

PROFIT

Cost basis accumulates on bids. When an ask fills, SOL received minus the proportional cost basis of the coins sold is realized. Positive realized splits in the same transaction: half to the vault, half added to the fomoling's working SOL, which raises its future bid rungs by the same proportion. Negative realized, possible only through partials straddling a move, is recorded. Realized is signed and shown signed.

DORMANT

A fomoling whose three bids have filled and whose asks have not is dormant. It holds coins and no SOL and waits for the coin to come back above birth. It is not dead. The first tick after the coin crosses an ask level wakes it. Dormancy has no time limit; only a closed thesis ends a fomoling.

RETIRE

When the trader closes their thesis on fomo.family, the witness calls retire. Every open rung is cancelled. The fomoling's SOL, working balance and any partial, goes to the vault. Every coin it holds is burned through the token program's burn instruction, reducing total supply permanently. A Retired event carries both amounts. The account stays, marked retired, so the history is readable forever.

WHAT THIS MEANS FOR HOLDERS

Every new thesis on the coin is a new buyer with real SOL that bids under the current value and only sells above the value it came in at. Every closed thesis burns whatever coins its fomoling still held. Fees keep the vault full, profits keep it fuller, and the queue means every thesis eventually gets its body. The count of fomolings is a live count of open cases for the coin on fomo.family, and the burned total is a live count of how many of those cases have closed.

WHAT THIS SITE READS

The coin's value in the top right comes from Birdeye through a server side proxy and refreshes every second. Every other number is decoded from program accounts and transaction logs over RPC and refreshes every two seconds. The thesis list comes from the FOMO API every five seconds. Nothing on this site is typed in, estimated or simulated, and nothing on this site can be posted, signed or operated. If a number is blank, its source has not returned it.