Using /og

/og takes one of three shapes. Pick the one that matches what you have in your hand — a symbol, a contract, or a contract you already know lives on a specific chain.

The three command shapes

`/og <chain> <symbol>`

Use this when you know the symbol but not the contract. Prysm searches every pair on that chain for an exact symbol match, picks the earliest pair per token, and returns the top 15 oldest, sorted oldest first.

/og sol scribbli
/og eth pepe
/og base higher

The first argument is a chain shortcut — anything in the Chain Shortcuts list works (eth, ethereum, base, bsc, bnb, polygon, matic, avax, avalanche, arb, arbitrum, op, optimism, sol, solana, sonic, ton, tron, trx, sui, mega, megaeth). The second argument is the symbol — case-insensitive.

`/og <contract>`

Use this when someone pasted you a contract and you want the OG list for whatever symbol it represents. Prysm auto-detects the chain from the address format, looks the contract up to find its symbol, then runs the same oldest-pairs search.

/og 7GCihgDB8fe6KNjn2MYtkzZcRjQy3t9GHdC8uHYmW2hr
/og EQDCJL0iQHofcBBvFBHdVG233Ri2V4kCNFgEBu_w9pIBLKD0
/og TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t

Non-EVM addresses are uniquely identifiable by format (Solana, TON, Tron, Sui), so there’s no ambiguity — Prysm goes straight to the right chain. EVM-shaped addresses (0x + 40 hex) can live on multiple chains; if more than one matches, Prysm will ask you to disambiguate (see below).

`/og <chain> <contract>`

Use this to disambiguate a multi-chain EVM contract — when the same 0x… exists on Ethereum and BSC and Polygon and you want results for one specific chain.

/og eth 0x6982508145454ce325ddbe47a25d4ec3d2311933
/og bsc 0x6982508145454ce325ddbe47a25d4ec3d2311933

Prysm uses the chain you passed as a hint, looks up the contract on that exact chain, reads the symbol, and runs the OG search there.

Accepted contract formats

Same address shapes the rest of the bot accepts — EVM (0x + 40 hex), Solana (base58, 32–44 chars), TON (EQ… / UQ…), Tron (T…), and Sui (0x + 64 hex with an optional ::module::name suffix). For the full chain list and exact regexes see Supported chains.

Multi-chain EVM disambiguation

When you pass a single EVM contract and Prysm finds it on more than one chain, it can’t pick for you. Instead of guessing, it replies with the candidate chains and asks you to specify:

This contract exists on multiple chains
(Ethereum, BSC). Specify a chain:
/og <chain> 0x6982508145454ce325ddbe47a25d4ec3d2311933

Re-run the command with a chain shortcut in front of the address — that locks Prysm to one chain and returns the OG list for that chain only.

Error responses

A handful of one-line replies you may see:

Contract not found anywhere. Prysm couldn’t find any pair for this address on any supported chain.
```
Could not find this contract on any supported chain.
```

Bad chain shortcut. The first argument isn’t a recognised chain.

Unknown chain "polkadot". Supported: eth, ethereum, base, bsc, bnb, polygon, matic, avax, avalanche, arb, arbitrum, op, optimism, sol, solana, sonic, ton, tron, trx, sui, mega, megaeth

Chain hint didn’t match. You passed a chain plus contract, but Prysm couldn’t find the contract on that chain. Either the address isn’t deployed there or it has no indexed pair.
```
Could not find 0x6982508145454ce325ddbe47a25d4ec3d2311933 on Polygon.
```
Zero results after filtering. A symbol search ran fine but every match was filtered out (no liquidity, honeypot pattern, inflated FDV, or simply nothing exists with that exact symbol on that chain). See Filtering and scams for the rules.
```
No PEPE tokens on Polygon with sufficient liquidity.
```

Walkthrough

You see a Solana contract pasted in a chat and want to know whether it’s the original SCRIBBLI or one of the clones. Paste it after /og — no chain, no symbol needed.

Input: /og 2P9L4xZk5h2vRq7mB3nYjW8tFcK1aHpSeXuVbN6oMdAg

Reply:

SCRIBBLI — OG Checker

#  CA     MCAP     VOL24H   DATE  AFTER
1. 2P9L4  $11.3K   $19.3K   30/04 OG
2. 8c3Jd  $1.23M   $4.7M    01/05 +188m
3. Fx3Xh  $95.9K   $573K    01/05 +266m
4. EMVy6  $272K    $7.6K    01/05 +6h
5. Zp2NS  $99.2K   $0       01/05 +17h
OG launched: 30/04/26

Chart : 1 2 3 4 5


Note: Solana CAs show the first 5 chars (pump.fun tokens often share the same suffix).

The contract you pasted starts with 2P9L4… — the row-1 CA in the table is 2P9L4, so the address you were sent is the OG. The OG launched on 30/04/26 with a $11.3K market cap. The numbered chart links at the bottom open 📊 DexScreener (or whatever you’ve set in /settings) for each row.

Where to next

Reading results Every column explained — CA, MCAP, VOL24H, DATE, AFTER, and the OG-launched footer.

Filtering and scams Which pairs qualify, which get rejected, and why the list might come up empty.

OG Checker overview What /og solves and when it's the right tool.