How it works
When you launch a token calledPEPE, the factory registers pepe.makx.eth (or the chain equivalent) and writes all metadata as ENS text records. The result:
| Chain | Subdomain | URL |
|---|---|---|
| Ethereum | pepe.makx.eth | makx.fun/pepe |
| Base | pepe.makx.base.eth | makx.fun/pepe |
| BNB Chain | pepe.makx.bnb | makx.fun/pepe |
pepe.makx.eth.
What’s stored on-chain
Every token’s ENS subdomain includes these text records:Standard records
| Key | Description |
|---|---|
avatar | Logo/image URL (supports IPFS and NFT references) |
description | Project description |
url | Website URL |
com.twitter | Twitter/X handle |
org.telegram | Telegram handle |
Makx-specific records
| Key | Description |
|---|---|
name | Token display name |
io.makx.token.symbol | Token ticker |
io.makx.token.decimals | Always 18 |
io.makx.token.totalSupply | Total supply (no decimals) |
io.makx.token.address | Token contract address |
io.makx.launchpad.address | Bonding curve contract address |
addr(node)) points to the token contract, not the bonding curve.
Resolving a token
Look up any Makx token using standard ENS resolution:Updating metadata
After launch, the Makx team (not the token creator) can update text records viaupdateRecord() or updateRecords() on the TokenENS contract. Subdomain ownership can also be transferred for token team handoffs.