Docs / Protocol
Architecture
Three programs, one of them ours, and what the site reads.
The programs
| Program | Role |
|---|---|
FomoPad 6hi7ve53… | Registers coins on stars, is the fee claimer of the launch config, harvests and splits fees, holds the locked positions. |
Meteora DBC dbcij3LW… | The curve: mints the coin, settles every curve trade, migrates at graduation. |
Meteora DAMM v2 cpamdpZC… | The pool after graduation. |
Accounts
| Account | Seeds | Holds |
|---|---|---|
| Config | ["config"] | admin, treasury, launch config, star share, fee share, pause, counters, the pad’s unclaimed share |
| Coin | ["coin", mint] | mint, pool, creator, star, the shares it launched with, totals. Nothing between harvests. |
| Fee claimer | ["fee_claimer"] | Signs claims on Meteora; owns the position NFTs. No data. |
| Harvest | ["harvest", coin] | The temporary wrapped-SOL account a claim lands in, created and closed within one harvest. |
What the site reads
The coin accounts (one getProgramAccounts), their DBC pools, their Metaplex metadata, the launch config, and the DAMM v2 pools of graduated coins, in batches. Trades come from the pools' own transactions, decoded from Meteora's swap events, and are cached in the browser. Mainnet reads go through the site's /api/rpc because the public RPC refuses browsers; nothing else runs server-side besides the metadata store.