Chain Coverage

The Supported Chains page is the gentle intro — what Prysm tracks, address shapes, native tokens. This page is the deep reference: a per-feature matrix showing which chains each feature actually covers, plus the chain-specific behaviour that doesn’t fit on the intro page.

Feature-by-chain matrix

Rows are chains. Columns are the major user-facing features. A check means the feature works exactly the same as on every other supported chain; a dash means it isn’t available on that chain.

Chain	Tracking (`/add`, `/list`)	Auto-detect	`/og`	`/bag`	`/ath`	Real-time prices	Forum-topic scoping
Ethereum	✅	✅	✅	✅	✅	✅	✅
Base	✅	✅	✅	✅	✅	✅	✅
BSC	✅	✅	✅	✅	✅	✅	✅
Polygon	✅	✅	✅	✅	✅	—	✅
Arbitrum	✅	✅	✅	✅	✅	—	✅
Optimism	✅	✅	✅	✅	✅	—	✅
Avalanche	✅	✅	✅	✅	✅	✅	✅
MegaETH	✅	✅	✅	✅	—	—	✅
Solana	✅	✅	✅	✅	—	—	✅
Sonic	✅	✅	✅	✅	—	—	✅
TON	✅	✅	✅	✅	—	—	✅
Tron	✅	✅	✅	✅	—	—	✅
Sui	✅	✅	✅	✅	—	—	✅

A few notes about reading this table:

Tracking covers /add, /list, the compact and detailed views, alerts, holdings, and PvP — the day-to-day watchlist surface area. It works the same on every chain.
Auto-detect is the paste-detection that turns a contract dropped into chat into a tracked token. Every chain is reachable by auto-detect; the format of the address is what tells Prysm which chain it’s on.
/og accepts every chain shortcut because the search runs against the chain you specify — there’s no per-chain backend restriction. Solana has a small extra wrinkle (see below).
/bag computes “what does it cost to own X% of supply” against the chain’s native token. Every chain has a native-token price source, so every chain works.
/ath is the only feature with chain-specific gaps. It’s EVM-only and excludes MegaETH and Sonic (Sonic isn’t classified as EVM in Prysm).
Real-time prices means live price streaming for tracked tokens. Polling-based price updates still work on every chain — the difference is only how fast a price change appears in your views.
Forum-topic scoping is universal: in any group that has Telegram forum topics enabled, watchlists are automatically scoped per topic regardless of chain.

All-time high is the only chain-restricted feature

Outside of /ath, every Prysm feature works the same way on every chain. If you can /add a token, you can hit /bag against it, search it with /og, set alerts on it, and put it in a PvP session.

/ath is the exception because it relies on a historical OHLCV data source that only covers the seven EVM chains in the table above. Pass an unsupported chain — /ath ton, /ath sol, /ath mega, /ath sonic — and Prysm replies with the list of chains that do work instead of failing silently.

Per-chain notes

These are the pieces of behaviour worth knowing per chain. Address formats and native tokens live on the Supported Chains page — this section only covers the things that don’t fit there.

Solana

Pump.fun bonding-curve pairs are honoured by /og. Pre-migration pump.fun tokens often read with null liquidity on standard tooling; Prysm treats them as real pairs anyway when running /og on Solana. See the filtering rules for the full set of exemptions.
Addresses are case-sensitive. Solana mints use base58 with mixed case — paste them exactly as you copied them. Prysm preserves case internally and won’t lowercase them like it does for EVM.
No real-time streaming. Price updates for Solana tokens happen on the polling cycle, not via a live stream.

TON

Addresses always start with EQ or UQ and are 48 characters total. The two prefixes denote different bounce flags on TON; both are accepted as inputs and Prysm preserves whichever one you pasted.
Case-sensitive. Like Solana, the base64url encoding of TON addresses is meaningful — don’t normalise it.
No /ath support. TON isn’t covered by the bot’s historical OHLCV source.

Tron

Addresses start with T followed by 33 base58 characters (34 total). The format is unique enough that auto-detect is unambiguous on a paste.
Case-sensitive. Tron addresses encode a checksum in the capitalisation — paste exactly as copied.
No /ath support.

Sui

Optional ::module::name suffix on type tags. A Sui coin can be referenced either as the bare 64-hex package address or as the full type tag (0x2::sui::SUI). Prysm accepts both shapes and resolves them to the same coin.
Addresses are 64 hex characters (twice the EVM length), which is what lets auto-detect tell Sui from EVM at a glance even though both start with 0x.
No /ath support.

MegaETH

EVM-shaped, but excluded from /ath. MegaETH addresses look exactly like Ethereum addresses (0x + 40 hex), so the disambiguation prompt for a multi-chain 0x… paste includes MegaETH. Everything else works the same as any other EVM chain except that /ath mega isn’t supported.

Sonic

EVM-shaped addresses, non-EVM classification. Sonic uses 0x + 40 hex address shape but Prysm classifies it as a non-EVM chain in its own right. In practice this means you can paste a Sonic contract the same way you’d paste any EVM contract, but Sonic doesn’t participate in the EVM disambiguation list and /ath isn’t supported.

Polygon, Arbitrum, Optimism

Polling, not streaming. These three EVM chains are tracked via polling for live price updates rather than a real-time stream. Watchlist views update at the polling cadence; nothing else differs.

Address formats

The exact patterns Prysm matches for each chain are listed on the Supported Chains page along with examples. That table is the one source of truth — it isn’t duplicated here.

Where to next

Supported chains The intro view — every chain Prysm tracks with shortcuts, address formats, native tokens, and caveats.

Chain shortcuts The full list of chain commands and how they slot into other lookups as a chain hint.

All-time high What /ath shows, which chains it covers, and how to read the output.