Operating it
The owner
Whoever OWNER was at deploy time owns the Launchpad, the referral handler, the referral router and the access registry. The owner's wallet can change, at /tokens/admin or straight on the explorer:
- The fees, for launches created after the change. A launch keeps the fees it was created with.
- The creation cost, up to 0.1 ETH.
- The treasury, which receives creation costs and the protocol's share of fees.
- The LP receiver, which is minted every graduated pool's liquidity position from then on.
- Who may create: everyone, or only addresses on the registry's allow list.
- Who may trade: any address the owner blocks is refused by every gauge.
The owner can also, on the explorer only, replace the curve, the token implementation or the gauge implementation for future launches, and change the curve's parameters. These are the original launchpad's controls, kept as they are. Nothing the owner does reaches a launch that already exists.
The treasury
The protocol's share of every fee accumulates in the referral handler. Anybody may send it to the treasury; it can only go there. The treasury's own wallet sees the amount and a button for it on any token page and on the settings page.
The liquidity position
A graduated pool's liquidity is one full range position, minted to the LP receiver. The pool's 1% swap fee accrues to it. The LP receiver's wallet sees a Collect pool fees button on a graduated token's page, which takes both sides of what has accrued through Uniswap's PositionManager. The position can also be managed on Uniswap's own site.
This is the one thing to be clear with buyers about: the liquidity is not locked. The reference launchpad works the same way, and every token page says who holds the position.
Creators
A creator claims their reward from the token page, whenever they like, and anybody may trigger the claim for them; the money can only go to the creator. The reward is a share of every fee on the curve. After graduation the pool's fees go to the liquidity position, not to the creator.
Referrals
Anybody with a wallet can register one code, a short word, at /tokens/referrals. Their link is /tokens?ref=<code>. A visitor who arrives through it and then trades is recorded as theirs on the chain, once, and from then on a share of the fee on every trade that visitor makes is credited to the code: 20% of what reaches the referral handler, and 30% once the code has brought 30 ETH of trades. The referrer withdraws from the same page.
The owner can change the tiers and the volume thresholds, set expiries on referrals, and give a code a custom duration, on the referral handler through the explorer.
Blocking
A blocked address cannot buy, sell or create. Blocking is the owner's, at /tokens/admin or on the registry through the explorer. There is no pause switch: the original launchpad has none, and a pause would be a way for the owner to freeze everybody's trades.
Reading the chain
The app reads through LAUNCH_RPC_URL. The public Robinhood endpoints rate limit and are not meant for production traffic; a real deployment uses its own endpoint from an RPC provider. Every chain read is allowed to fail: a page whose read failed says so and renders the rest.
Keys
Nobody's key is ever held by the app. The owner's key stays with the owner and is used from the owner's own terminal to deploy and from the owner's wallet to change settings. The throwaway key used for the testnet deployment owns nothing.