the token currently called
Anyone can rename it. Burn 1M tokens, pick a new identity, and the token — and this entire page — becomes something else. The supply never comes back. The pool never moves.
Change the token
Burn the required tokens and the token is yours to name. No allowlist, no gatekeeper — just supply, destroyed forever.
Up to 32 bytes. Emoji count for more than one.
Up to 12 bytes.
https:// or ipfs:// only — data: URIs are rejected on-chain.
This palette is derived from the name — the whole site repaints.
- →Your pool, price and LP positions are untouched.
- →Wallets and explorers cache metadata and may lag or never refresh.
- →The tokens you burn are destroyed, not collected. Supply only ever falls.
- →Every skin is recorded on-chain, forever, with your address.
Hall of skins
Every identity this token has worn, newest first — read straight from the chain.
Hover or tap any skin to wear it.
How it works
Hold and connect
Any injected wallet on Arc, holding enough to burn. Gas is USDC, so there is no second token to go and buy first.
Choose an identity
Name, ticker and image. Validation here mirrors the contract byte-for-byte, so nothing fails on-chain.
Burn to claim it
One transaction destroys your tokens outright — nobody collects them. Sub-second finality on Arc means the rename lands almost as fast as you can watch.
Everything repaints
The name, ticker, image and this entire page's palette change at once — and the skin is recorded forever.
What changes instantly
- ✓
name()andsymbol()on the contract — the real, canonical source of truth. - ✓This site, and anything else reading the chain directly.
- ✓Total supply falls by the burn, permanently, and the skin history records who paid it.
What may lag, or never update
- !Wallets, explorers, DexScreener and token lists usually read an ERC-20's name once and cache it. There is no standard “metadata changed” event for ERC-20 to force a refresh.
- !The contract emits
SkinChangedandNameUpdatedanyway, so any indexer that wants to follow along can. - ✓Your pool is unaffected either way. A Uniswap v4 pool is keyed by token addresses, never names — liquidity, price and LP positions never move.
Contracts
Uniswap v4 is deployed on Arc mainnet only. On testnet those addresses hold no code — and an EVM call to a codeless address succeeds while doing nothing — so this pool runs on our own deployment of Uniswap's PoolManager. Same source, different instance.