Admin
Contract controls for the fee-routing contract and site settings. Contract actions require the on-chain owner; harvesting is open to anyone.
Overview
…Harvest
Sweep every token’s pending creator fees, claim the pons escrow and book it 80/20 into the pools. Anyone can call this; the keeper does it on a schedule.
Launches
Pausing stops new launches through the contract. Tokens already launched keep trading and paying fees.
Pools
Withdraw ETH from the recipient pool for off-ramp and provider funding, or from the treasury.
Keepers
Wallets that may harvest and set do-not-pay. They can never withdraw funds; only the owner can.
Loading history…
Do-not-pay
Honour a removal request. The alias can’t be named in new launches, and its share of later harvests goes to the treasury.
Loading history…
Ownership
Two-step transfer: the new owner accepts from their own wallet before anything changes. Move ownership to a multisig before heavy traffic.
Settlement operations
…Review recipient ownership, country, currency and payout eligibility with the provider before approval. Approval permits dispatch only in the matching environment.
Site token CA
…Publish the token contract address shown below the homepage hero. Saving asks the owner wallet for a signature; no on-chain transaction is sent. Leave it empty to hide the CA.
Emergency recovery
Recovers ETH or ERC-20 tokens held by the contract. ETH recovery consumes unaccounted ETH first, then treasury, then recipient funds. Use only in an emergency.