Conge

No. Conge shows automated, rule-based checks on public data — it is not financial advice, and it never tells you to buy, sell, or hold anything. Always verify independently before acting on anything it shows.

No. Conge is entirely read-only. It never requests a wallet connection, a signature, a private key, or a transaction of any kind — it only reads public on-chain and block-explorer data.

Because Conge would rather say it couldn't check something than guess. An Unknown check never counts toward the risk level — not as a red flag, and never as a pass — and each one says why. The usual reasons:

The shared public RPC is rate-limited. The owner and sell-simulation checks read the chain through a public RPC endpoint shared by everyone using this chain, and it has a tight limit. Conge already retries automatically, at both the Worker and the app level, but under load these checks can still come back as "Sell simulation could not complete" or "Owner unknown". That's a known limitation, not an error in Conge.

The block explorer is slow. Under load, some Blockscout lookups — contract verification and deployment time especially — can take several seconds. Each one gets 10 seconds; if it doesn't answer in time (or returns an error), the checks that depend on it say the block explorer couldn't be read, with the failed request under Technical details.

There's nothing to check. Some Unknowns aren't failures at all: owner privileges can't be read when the source isn't verified, and a sell can't be simulated when no liquidity pool turns up among the top holders.

For the first two, tapping Rescan a little later usually goes through.

After every scan, the Scan and Rescan buttons pause for 3 seconds and count down ("Scan again in 3s"). The owner and sell-simulation checks share one public RPC with everyone else on this chain, and it has a tight rate limit; a short pause keeps quick repeat taps from flooding it — which would only make your next scan, and everyone else's, more likely to come back Unknown. Nothing is wrong, and the buttons come back on their own.

Conge only scores tokens. If the address is a wallet (no contract code), or a contract that isn't a standard token — a router, a liquidity pool, or anything else without a token name, symbol, and decimals — it says so and stops, rather than showing a risk level that wouldn't mean anything. Double-check you copied the token's own contract address. If the block explorer couldn't confirm what the address is right then, Conge says that instead; trying again a moment later usually works.

No. Conge is not affiliated with, endorsed by, or connected to Robinhood Markets, Inc. in any way. It's an independent project that happens to support Robinhood Chain, a network operated by someone else.

No — the repository is private right now. You don't have to take that on faith, though: everything Conge does runs in your own browser, reading public Blockscout data and, through its read-only Worker relay, the chain's public RPC — so you can open your browser's network tab and watch exactly what it requests and where.

By a fixed set of transparent, rule-based checks — no model, no hidden scoring. The overall level is the worst result among the checks that actually produced data. See how it works for the full list of checks, their exact thresholds, and what each level means.

Robinhood Chain mainnet (chain ID 4663) only, for now. Support for other chains isn't currently planned but could be added later.