Scanning
Contracts, tickers, the checksum database and the security stack.
Scanning is roughly four fifths of everything Proficy does. It is the one command worth knowing properly.
| /p<contract | name> also /r | Full token scan: price, security, holders, checksum, links. |
| /c<contract | name> | Token chart, rendered in the chat. |
| /ce_<checksum id> the second letter is the chain: /ce_ Ethereum · /cb_ BNB Chain · /cs_ Base · /cr_ Robinhood Chain | Contract checksum: every other token deployed from the same bytecode. |
| /wallets<contract address> tapped from a card as /wh_<id>; a bare /wh is not a command | The holder map: whales, top 10 and top 20 share, LP burn and bundles. |
| /b<contract | name> | Bubble map of the top holders and how their wallets connect. |
What you can paste
- A raw contract address, on any supported chain. No command needed, and this is how almost every scan actually starts.
- A ticker or a name:
/p btc,/p pepe. Ambiguous names resolve to the highest-liquidity match. - A
$TICKERanywhere in an ordinary sentence, which scans it without anybody running a command at all. - A pair address, which resolves to its base token.
The shortcuts under every card
This is the part that makes a second scan cost nothing. Every card the bot prints carries command links for that exact token, so nobody ever pastes the same address twice, and every row of a trending board is one too. They are links to tap, not commands to memorise: each one has the token’s id already glued on after the underscore.
/p_ApZuxd the scan again, refreshed /c_ApZuxd the chart /wh_ApZuxd the holder map: whales, top 10, top 20, bundles /b_ApZuxd the Bubblemaps cluster picture /cr_cbcfb8bb every contract sharing this bytecode /dr_a075ac58 everything this deployer has launched /sc_NVDA the Smart Chart, from a stock quote
/wh_ is the only form of the holder map that is one keystroke from something else, so it is worth being precise about: there is no /wh command. Typing /wh 0xabc… does not open the holder map, it runs an ordinary scan. Tap the link on the card, or type the full name: /wallets <address>. That form needs a real contract or pair address rather than a ticker, so /wallets pepe will not resolve either.
The letter after /c and /d is the chain, and the card always prints the right one: /ce_ Ethereum, /cb_ BNB Chain, /cs_ Base, /cr_ Robinhood Chain, with /de_ /db_ /ds_ /dr_ for the deployer. The checksum database explains what those two open. Bubble maps come from Bubblemaps and cover Ethereum, BNB Chain and Solana.
The holder map
/wh_ under any card opens the full holder picture, which is more than the card has room for: the biggest holder, the top ten and top twenty share, whether LP is burned, how many wallets bought at launch and what they are still sitting on. Holders are drawn as 🐳 🦈 🐬 🐟 🦐 by what their position is worth, and every one of them opens that wallet in an explorer.
It reads holders straight off the chain, so it is the precise version of the sniper and bundle percentages the card estimates. Available on Solana, Ethereum, BNB Chain, Base and Robinhood Chain, which are the chains whose holder data can actually be fetched. The answer is cached per token, so a room all tapping the same card costs one lookup.
Where the full stack runs
Checksum history, holder distribution, sniper detection and tax simulation need per-chain infrastructure. They run on Solana, Ethereum, BNB Chain, Base and Robinhood Chain, which between them are about 95% of scan volume. The other twenty-one chains are priced, charted, tracked and linked, but a card there will be shorter.
The checksum database
1,548,982 contracts, accumulated since 2022. Its value is entirely in its age. A checksum database started this month can tell you nothing about who has rugged before. This is the part of Proficy that cannot be cloned in a weekend, and it is the reason the scan is worth running even if you already ran somebody else’s.
It has its own page, because it is the one field on the card that is worth understanding properly: The checksum database.