Identity & status
"Is the ownership renounced?" is the first question every degen asks, because on most chains an owner can do anything. On Diggers the question has a beautiful answer: there was almost nothing to own in the first place.
A Diggers coin has exactly two configuration roles, independent and per-coin. The burn owner can tune the burn share: how the token-side fee splits between burning and the Daily Contest Pot. The fee owner can rotate the wallets in the creator reward table: swap which addresses collect the 70% creator slice. What the fee owner cannot touch is the split itself, the share percentages are welded in at launch. That is the complete list. There is no third key, hidden or otherwise.
| Owners CAN | Owners CANNOT | |
|---|---|---|
| Tune burn vs contest split | ✓ | |
| Rotate the reward-recipient wallets | ✓ | |
| Transfer or renounce their role | ✓ | |
| Change the reward share percentages | ✕ | |
| Change the 1% pool fee | ✕ | |
| Mint supply | ✕ | |
| Touch anyone's balance | ✕ | |
| Remove liquidity | ✕ | |
| Pause or block trading | ✕ | |
| Upgrade the contract | ✕ |
Each key can be transferred to a new owner or renounced outright. Renouncing is permanent: the config it guarded freezes at its current values for the life of the coin, and the site displays RENOUNCED on the coin page for everyone to see. There is no recovery path, which is exactly what makes it meaningful.
Separate from those per-coin keys, the launchpad itself has one bounded owner. Its powers are deliberately narrow and every one of them is about configuring the platform, never reaching into a coin. The protocol owner can open or pause new coin creation, adjust the platform's team fee share within a hard cap it can never exceed, rotate the fee-recipient wallet, one-shot activate the optional staking and backing integrations, and transfer or renounce itself, at which point config freezes forever.
| Protocol owner CAN | Protocol owner CANNOT | |
|---|---|---|
| Open or pause new coin creation | ✓ | |
| Adjust the team fee share (up to a hard cap) | ✓ | |
| Rotate the platform fee recipient | ✓ | |
| One-shot activate staking / backing | ✓ | |
| Transfer or renounce itself | ✓ | |
| Touch any coin's balances or supply | ✕ | |
| Remove or move any pool's liquidity | ✕ | |
| Reach into a coin's accruals or contest | ✕ |
The traditional token gives its deployer a master key and asks the community to trust it will not be used. Diggers inverts the design: supply, the 1% pool fee, the reward-share table, liquidity, trading, the anti-whale shield, the contest, the points, the graduation bars, all of it is immutable from birth with no owner input possible. The two per-coin keys that remain exist only because teams legitimately evolve: burn strategies change as a coin matures, and reward wallets sometimes need rotating when contributors join or leave. Both are cosmetic to safety: neither can touch a holder's money.
Two small keys: adjusting the token-side burn-versus-pot split, and rotating reward recipient wallets. Supply, liquidity, the 1% pool fee, the split table percentages and all trading mechanics are frozen at birth for everyone, creator included.
It permanently gives up those two keys. After renouncing, the burn split and recipient wallets are frozen forever, and the coin runs with zero admin keys of any kind.
Yes. Quick launch passes ownership to the zero address at creation, so the coin is born renounced with no keys ever existing.
No. Those functions do not exist in the contracts, for anyone. A creator's keys never extend to balances, supply, liquidity, trading or accrued rewards.