Security

What is enforced, what is tested, and what is not.

Enforced on chain

• Nobody controls a live coin. The curve and the pool are Meteora's. The pad's program has no instruction that trades, withdraws, pauses trading or removes liquidity.
• The star is paid, not owed. A harvest moves the star's share to the star's wallet in the same instruction. The coin account holds exactly its rent after every harvest.
• A launch proves itself. register_coin requires the pool's creator transfer in the same transaction, so a pool cannot be registered by anyone but who created it, and only on the pad's config.
• Terms are pinned. The star share travels in the launch instruction; a changed setting fails the launch.
• Stray SOL is never stuck. SOL sent to a coin account or its harvest address is paid out with the next harvest.

Tested

Ten end-to-end tests run the built program in LiteSVM against the mainnet binaries of Meteora DBC, DAMM v2 and Metaplex: launches, every refusal of register_coin, adoption, harvests with every lamport accounted for, stray SOL, two coins on two stars, the treasury, a full graduation with pool trades and the position's fees, and the admin's whole surface.

What you still trust

• The program is not third-party audited, and its upgrade authority is a single key held by the operator.
• Meteora's programs, as every Meteora launchpad does.
• The star list: a name is as good as FOMO's data on the day it was read.
• The site stores icons and metadata; the chain only holds the URI.