Skip to content

Add Tokens

There are two ways to put a token on your watchlist. Both finish in the same place — the token is saved, the price snapshot is stored, and a confirmation message appears with two follow-up buttons.

  1. Paste the contract address. Copy a contract from anywhere — DexScreener, X, a chat — and drop it straight into the chat with Prysm. The bot detects the chain, fetches the token, and replies with a preview plus an Add to Watchlist button. Tap it and you’re done.

  2. Run /add <contract_address>. If you’d rather type, send the command directly. Prysm skips the preview and adds the token in one shot.

Both paths land on the same success message and the same pair of inline buttons.

Paste anything that looks like a contract — Prysm reads the format and figures out the chain.

  • EVM (0x + 40 hex chars) — Ethereum, Base, BSC, Polygon, Arbitrum, Optimism, Avalanche, MegaETH.
  • Solana — base58, 32–44 characters.
  • TONEQ… or UQ… (48 chars), or the raw 0:abcdef… form.
  • TronT… (34 chars).
  • Sui0x + 64 hex, optionally with the 0x…::module::name coin-type suffix.

For the full list of supported chains and the exact regexes Prysm uses, see Supported chains.

Once Prysm has the token, the message rewrites to:

Token Added Successfully!
🔹 PEPE  Pepe

Price: $0.0₅1234
Market Cap: $5.2M
24h Change: 🟢 +12.4%

📊 Etherscan
📊 DexScreener

The chain emoji on the token line and the ”📊” markers are real custom emojis in Telegram — they render in colour in the client, not as the fallback glyphs shown above.

Etherscan and DexScreener are tappable links. The explorer is fixed per chain (BscScan for BSC, Solscan for Solana, TON Viewer for TON, etc.). The chart provider follows your /settings preference — DexScreener is the default; DexTools, Defined, and GMGN are also available.

Two buttons appear under the message:

  • 📊 View List — jump straight to your full watchlist.
  • 🔔 Set Alert — start the alert flow for the token you just added.

Drop multiple contracts in one message — newline- or comma-separated — and Prysm processes them as a batch. Up to 20 contracts at a time; anything past 20 is skipped, and so are contracts that would push you over your token limit. You’ll get a single summary message back listing what was added and what failed.

EVM addresses (0x + 40 hex) aren’t unique to one chain — the same address can be deployed on Ethereum and on BSC and on Polygon all at once. When Prysm sees an EVM-shaped address, it checks the supported EVM chains and tracks the first chain where the token is live.

If the contract you pasted exists on a chain Prysm didn’t pick, the cleanest fix is to look up the token on a block explorer for the chain you actually want, copy that explorer’s contract address from there, and paste it back — the address is the same, but pasting it again after Prysm has cached metadata won’t help. For most tokens this isn’t an issue: the chain Prysm finds first is the one with real liquidity.

The commands are identical in both. What changes is whose watchlist the token lands on.

  • In your DM — the token goes on your personal watchlist. Only you see it.
  • In a group — the token goes on the group’s shared watchlist. Anyone in the group can add tokens; no admin permission required. If the group is in Silent Auto-Track mode, /add is ignored — pasted contracts are picked up automatically and added without a confirmation message. See Silent Auto-Track for the modes.

In a forum-topic group, each topic has its own slice of the group’s watchlist — adding a contract in #general is separate from adding the same contract in #alpha.

By default you can track up to 5 tokens in your DM. Groups start with 6. Forum topics inside a group are additionally capped per-topic.

If you hit your cap, Prysm replies with a warning instead of adding:

⚠️ You've reached your token limit (10 tokens).

Please remove a token before adding a new one,
or contact the dev @epicvillages to request a
limit increase.

Remove something with /remove to free a slot, or message @epicvillages directly to ask about a higher cap.

A few flows return a warning instead of the success message:

  • Already tracking it. “⚠️ You are already tracking this token!” in DM, or “⚠️ This group is already tracking this token!” in a group. Nothing else happens.
  • Bad address. ”❌ Invalid token address or token not found.” Usually means the chain detector couldn’t find liquidity — the contract exists, but no DEX pair has been indexed for it yet.
  • Limit reached. See the limits section above.