Same team, wallet lost
Use only when the same team controls the already registered official domain. CoinGecko must still show that domain.
Project control guide
Wallet recovery and community takeover
Two fail-closed paths restore access without treating wallet control, silence, or provider metadata as proof of project safety.
Choose the correct path
Community takeover (CTO)
Use when a new community team operates the project. CoinGecko, DexScreener, a historical snapshot, the new wallet, and the new domain must agree.
Required sequence
- 1
Update public sources first
CoinGecko must map the exact chain and contract. A CTO must also update its website or socials there and obtain matching DexScreener evidence.
- 2
Connect the replacement wallet
MoonMath uses a one-time SIWE signature. A signature authenticates a wallet; it does not by itself prove organization control.
- 3
Prove the official domain
Publish the generated DNS TXT record or HTTPS well-known file. Never share wallet keys, seed phrases, registrar credentials, or API keys.
- 4
Wait through cooling off
Lost-wallet recovery waits seven days. A community takeover waits fourteen days so the current owner can dispute it.
- 5
Keep evidence stable
MoonMath checks the contract, providers, public metadata, and domain proof again. Missing, changed, contradictory, or unavailable evidence blocks activation.
Prevent future lockout
- Use a hardware wallet or multisig for the owner role.
- Keep a separate admin wallet and remove departing team members promptly.
- Separate wallet, registrar, CoinGecko, and DexScreener credentials and enable phishing-resistant MFA.
- Store recovery codes offline and periodically verify public contract, website, and social metadata.