The court
Admin powers
Last updated 5 November 2026
The whole list
Every owner-controlled function in the deployed Minos system, in one table. If a power is not listed here, the key does not have it. The contracts are verified on Sourcify with exact matches, so this table can be checked against the code, function by function.
| Function | Can do | Cannot do | Protection |
|---|---|---|---|
| setPaused MinosFactory | Stop all buys on Minos: the curve, new launches, and graduated tokens through the Minos router | Stop sells, move funds, or stop trading anywhere else | Multisig and timelock on mainnet (planned) |
| setPlatformWallet MinosFactory | Redirect the platform fee share from future trades. Every change emits a public event | Move fees already earned; those stay with the old wallet | Multisig and timelock on mainnet (planned) |
| setGraduationExecutor MinosFactory | Set the graduation executor one time, during setup | Change it ever again. A wrong value means redeploying the factory | One-time in the code itself |
| registerDepositor MinosFactory | Register curves, the router and boosts as revenue pool depositors | Move any pool funds | Multisig on mainnet (planned) |
| forceGraduate BondingCurve | Finish a parked graduation under the fixed tier rules | Change the price, the amounts or the destination. It reverts if no tier qualifies | Multisig on mainnet (planned) |
| setRegistrar RevenuePool | Choose which factory may register depositors | Move funds. Note: moving it stops graduations for the old factory’s live tokens | Multisig on mainnet (planned), plus the published migration gate |
| removeDepositor RevenuePool | Stop a curve’s future deposits into the pass pool | Touch earned balances or staked passes. Blocked deposits wait in the curve | Multisig on mainnet (planned) |
| setFounderPass RevenuePool | Wire the pass contract one time | Change it afterwards | One-time in the code itself |
| mint, batchMint MINOS PASS | Mint passes | Mint past 707. The cap is enforced by the contract | Hard cap in code; multisig (planned) for the key |
| setBaseURI MINOS PASS | Change where the pass metadata points | Change supply, ownership or staking | Multisig on mainnet (planned) |
| setQuestMintOpen MINOS PASS | Open or close the quest mint | Mint passes, change the mint price or the cap | Multisig on mainnet (planned) |
| withdrawMintProceeds MINOS PASS | Withdraw the HYPE the quest mint collected from buyers | Touch fee claimables, pool balances or any other funds | Multisig on mainnet (planned) |
| freeze, unfreeze ReferralRegistry | Toggle a flag the website honors | Alter any binding or move funds. Bindings cannot be edited | Multisig on mainnet (planned) |
| enableFeeAmount, setOwner V3 Factory (upstream Uniswap code) | Enable new pool fee tiers; hand over that ownership | Touch pools, positions or funds | Multisig on mainnet (planned) |
What no key can do
No owner function, on any contract, can: change the 1% trade fee, the 150 HYPE graduation bar or the fixed supply of 1,000,000,000; withdraw the burned liquidity position; move curve funds or anyone’s earned, claimable balance; edit a referral binding after it is set; or mint a 708th MINOS PASS.
The honest line
Today this is a testnet deployment. Every owner role above sits on one deployer wallet. The mainnet plan moves those roles behind a multisig with a timelock, before any real funds are involved. Two setters, the graduation executor and the pass contract wiring, are already one-time in the code itself. They need no trust at all. Everything else in the Protection column is a plan. It is written here as a plan, not as a fact.