Proficy compared · Proficy

Compared

What we do, what they do, and where we lose.

Twelve features, four bots, every cell read off that product’s own public material rather than ours.

Bytecode checksum and rug history

Fingerprint the compiled contract, then report every other token deployed from the same code and how many of them died. Rick and PIRBView both trace the deployer’s wallet, which catches a repeat deployer but not the same code redeployed from a fresh one.

Proficy: 1.6M contracts
Phanes: deployer only
Rick: deployer only
PIRBView: deployer only

Free, with no token

Every feature, every group, nothing gated behind a coin.

Proficy: ✓Yes
Phanes: boosts, Pro
Rick: premium tier
PIRBView: $PIRB

AI research grounded in four years of scan history

Others analyse a contract with a model. Ours does that and adds what no model can produce: when the token was first seen and at what market cap, what it peaked at, how many groups have scanned it, and whether that count is rising today.

Proficy: scan history
Phanes: not documented
Rick: AI analysis
PIRBView: not documented

Every X post about a token, in the chat

Not a sentiment score. The post count, how many separate accounts, how many posts are repeats, how many accounts share identical copy, and then the posts themselves.

Proficy: ✓Yes
Phanes: not documented
Rick: profiles only
PIRBView: not documented

Follow any X account for post alerts

The difference is which accounts you may pick, not how many. Proficy takes any handle you give it; the alternative is choosing from a catalogue somebody else curated. Ours also run in DMs.

Proficy: any account
Phanes: curated list
Rick: no
PIRBView: not documented

The Phanes cell is from their live bot rather than their docs, which document six alert types and not this one.

Calls, tracked to peak, with a leaderboard

Proficy: ✓Yes
Phanes: ✓Yes
Rick: ✓Yes
PIRBView: not documented

Charts rendered in the chat

Fifteen timeframes, from per-block to weekly.

Proficy: ✓Yes
Phanes: ✓Yes
Rick: ✓Yes
PIRBView: ✓Yes

Stocks, ETFs and indexes

Quotes and candles for equities beside the token commands.

Proficy: ✓Yes
Phanes: ✓Yes
Rick: ✓Yes
PIRBView: no

Paper trading at live prices

Positions marked against the real price, not a dice game. Rick ships blackjack and a coin flip; the paper portfolio is the part nobody else has.

Proficy: ✓Yes
Phanes: no
Rick: games only
PIRBView: not documented

Public trending board on the web

Proficy: ✓Yes
Phanes: ✓Yes
Rick: not documented
PIRBView: not documented

Discord as well as Telegram

We are Telegram only, and have no near-term plan to change that.

Proficy: no
Phanes: ✓Yes
Rick: ✓Yes
PIRBView: not documented

Bot speaks your language

We translate into nine languages on request; we do not yet render the bot itself in them.

Proficy: translation only
Phanes: 18 languages
Rick: not documented
PIRBView: not documented

Feature	Proficy	Phanes	Rick	PIRBView
Bytecode checksum and rug historyFingerprint the compiled contract, then report every other token deployed from the same code and how many of them died. Rick and PIRBView both trace the deployer’s wallet, which catches a repeat deployer but not the same code redeployed from a fresh one.	1.6M contracts	deployer only	deployer only	deployer only
Free, with no tokenEvery feature, every group, nothing gated behind a coin.	✓	boosts, Pro	premium tier	$PIRB
AI research grounded in four years of scan historyOthers analyse a contract with a model. Ours does that and adds what no model can produce: when the token was first seen and at what market cap, what it peaked at, how many groups have scanned it, and whether that count is rising today.	scan history	not documented	AI analysis	not documented
Every X post about a token, in the chatNot a sentiment score. The post count, how many separate accounts, how many posts are repeats, how many accounts share identical copy, and then the posts themselves.	✓	not documented	profiles only	not documented
Follow any X account for post alertsThe difference is which accounts you may pick, not how many. Proficy takes any handle you give it; the alternative is choosing from a catalogue somebody else curated. Ours also run in DMs.The Phanes cell is from their live bot rather than their docs, which document six alert types and not this one.	any account	curated list	-	not documented
Calls, tracked to peak, with a leaderboard	✓	✓	✓	not documented
Charts rendered in the chatFifteen timeframes, from per-block to weekly.	✓	✓	✓	✓
Stocks, ETFs and indexesQuotes and candles for equities beside the token commands.	✓	✓	✓	-
Paper trading at live pricesPositions marked against the real price, not a dice game. Rick ships blackjack and a coin flip; the paper portfolio is the part nobody else has.	✓	-	games only	not documented
Public trending board on the web	✓	✓	not documented	not documented
Discord as well as TelegramWe are Telegram only, and have no near-term plan to change that.	-	✓	✓	not documented
Bot speaks your languageWe translate into nine languages on request; we do not yet render the bot itself in them.	translation only	18 languages	not documented	not documented

✓: ships it
-: documented, and does not
not documented: their docs do not say, so we do not either

Phanes

Telegram and Discord, free, no token.

Their docs

Rick

AI-first scanner, Telegram and Discord. No token; a premium tier.

Their docs

PIRBView

Holder-forensics specialist, built around the $PIRB token.

Their docs

The row that is actually the argument

Most of this table is parity. Every serious bot scans, charts and ranks calls. The first row is the one nobody else has: Proficy fingerprints the compiled bytecode of every contract it sees, so a new token is matched against 1,610,498 stored contracts and the card says how many of the matches are already dead.

Everyone else traces the deployer’s wallet instead. That catches the same person launching twice and stops working the moment they use a new one, which costs nothing. A deployer can change the name, the ticker, the address and the wallet. Changing the compiled code means starting over.

Try it in one message How the checksum works

And the two where they are ahead

We are Telegram only, and two of them also run on Discord. And one of them renders its whole interface in eighteen languages; we translate into nine on request, but the bot still speaks English at you. For a group that is not English-first, that is a real reason to pick them.

Both rows are in the table above, at the same weight as the rest, because a clean sweep down our own column would be worth nothing to the person reading it, and because we already publish the numbers that make us look smaller.

Every cell is read from that product’s own public command documentation, never inferred from a landing page. These are other people’s products and they ship constantly; if a cell here is out of date or wrong, tell us at support and we will correct it.