FREQUENTLY_ASKED
01_How do I submit a token?
Connect a wallet, paste the contract address (or Chia asset id), and hit AUTOFILL_FROM_CHAIN to pull the name, symbol, and decimals straight off-chain. Add a logo, then sign the submission. That's it.
02_Do I need gas or a listing fee?
No. Submitting only requires a wallet signature (a personal_sign message — no transaction, no gas, no fee). The signature ties your submission to an address so we can rate-limit and fight spam.
03_What does the portal check?
On-chain, automatically: the contract/asset exists, the on-chain decimals match (hard requirement) and symbol matches, the address isn't already listed, the symbol/name don't collide with a different token on that chain, and the logo is a square PNG. Liquidity and contract-security signals are gathered too and shown to the reviewers.
04_Does it look for duplicates and conflicts?
Yes. An exact address already listed or queued is a hard duplicate and is rejected. A different address reusing an existing token's symbol or name on the same chain is flagged prominently on the pull request for reviewer scrutiny — scam tokens often impersonate real ones this way.
05_What happens after I submit?
If validation passes, a pull request is opened automatically against the public app-tokens repository, and the 9mm team reviews and merges it there — merge means listed. Borderline signals (a symbol conflict, a security flag) are highlighted on the pull request. Hard failures are rejected immediately with the reason. You can follow the status any time on the TRACK_ page with your tracking token.
06_Which chains are supported?
PulseChain, Base, Ethereum, Sonic, BNB Chain, Chia. EVM chains validate by contract address; Chia uses CAT asset ids.
07_Where do approved tokens end up?
They're committed to the public app-tokens repository and served from the CDN — the exact same token lists the 9mm apps already read. Nothing about how the lists are consumed changes; the portal just becomes the way tokens get into them.
08_My token is already on another list — will it be included automatically?
It can be discovered automatically. The registry ingests third-party token lists on a schedule, then routes new tokens through the same validation and the same team-reviewed pull-request path before listing.