A token can pass every structural check and still be run by a wallet that has rugged before. The missing context is the deployer — who created it, and how established that wallet is. Here’s how to read it before you trade.
Honeypot and structural checks read this contract. They can’t see the wallet behind it — and a fresh wallet spun up to launch-and-rug looks identical, at the contract level, to an honest new project. The deployer’s track record is the context those checks miss.
A contract’s deployer is whoever sent its creation transaction — but a normal RPC node won’t tell you who that was; it takes a block explorer. true402’s deployer-check resolves it for any Base token and profiles the wallet in one call.
# Who deployed this token, and how established is that wallet? ~$0.008 USDC, no account.
curl -s -X POST https://true402.dev/api/v1/base/deployer-check \
-H 'content-type: application/json' \
-d '{"token":"0x<token-address>"}'
# { "deployer":"0x…", "txCount":1320, "contractsCreated":22, "ethBalance":"…",
# "risk":"low", "flags":[] } # established wallet → reassuring
# fresh throwaway → "risk":"medium", "flags":["fresh_deployer"]The discriminating signal is wallet age: an established deployer (hundreds–thousands of txs) is reassuring; a near-empty, brand-new wallet is the classic throwaway. The number of contracts a wallet has shipped is context, not a verdict — legit protocols ship many (Aerodrome 24, DEGEN 22), so a high count is never treated as "serial rugger." A fresh_deployer flag means: size down and verify.
Deployer reputation is one input. Pair it with a rug/honeypot check on the token itself and the on-chain rug red flags — an established deployer and a clean, sellable contract is a much stronger signal than either alone.
A contract's deployer is the wallet that sent its creation transaction — but you can't read it from a normal RPC node; you need a block explorer (Blockscout, Etherscan) or a service that queries one. true402's deployer-check resolves the deployer of any Base token in one call (POST the token address) and profiles that wallet, so an agent can vet the creator before it trades. ~$0.008 over x402, no account.
Look at the deployer wallet's track record, not just this one contract. The most useful signal is age: an established wallet with hundreds or thousands of transactions and a history of shipping contracts is far less likely to be a throwaway than a wallet created minutes before the launch. A brand-new, near-empty deployer wallet is the classic rug setup. true402's deployer-check reports the wallet's tx-count, balance, and how many contracts it has shipped, and flags a fresh throwaway.
Not on its own. Raw "number of contracts deployed" does NOT identify a rugger — legitimate protocols ship many contracts from one wallet (on Base, Aerodrome's deployer made 24, DEGEN's 22). So a high count is reported as context, never treated as a verdict. What actually discriminates is a FRESH wallet (almost no history) deploying a token. Whether a deployer's earlier tokens actually rugged is a deeper, separate check.
It means extra caution. A deployer wallet with near-zero history that was funded shortly before deploying the token is the common pattern for a throwaway launched to rug and abandon. It is not proof — legitimate new projects also start with a fresh wallet — but it removes the reassurance an established, long-lived deployer gives you. Treat a fresh-deployer flag as "size down and verify," and always pair it with a rug/honeypot check on the token itself.