Admin and timelocks
Every admin power is listed here with its limit. If a power is not on this page, the admin does not have it.
Who holds the keys
Section titled “Who holds the keys”| Testnet | Mainnet | |
|---|---|---|
| Admin | The deployer key | A 2-of-3 Safe wallet |
| Timelock on protocol changes | 10 minutes (600 s) | 24 hours (86,400 s) |
| Guardian | Can only pause | Can only pause |
The timelock owns the launch factory, the registries and the fee vault. A protocol change is queued in public, waits out the delay, and only then takes effect, so anyone can see it coming.
What the admin can do
Section titled “What the admin can do”| Power | How fast | Limit |
|---|---|---|
| Add a new version of the launch factory | After the timelock | Existing tokens keep the rules they launched with |
| Add or disable a venue | After the timelock | Affects new launches only |
| Change the creation fee | At once | Never above 0.05 HYPE; new launches only |
| Pause new launches (guardian) | At once | Cannot touch existing tokens, trades or balances |
What the admin can never do
Section titled “What the admin can never do”- Remove liquidity. Graduation liquidity is locked; no contract has a function that withdraws it.
- Withdraw fee balances. Creators’ and referrers’ balances in the fee vault belong to them. There is no admin withdrawal.
- Change a live token. A token’s curve, fees and venue are fixed when it is created. Its contract has no owner.
- Mint tokens. Supply is fixed at creation.
This record holds confirmed rules only. Contract addresses appear after deployment and verification.