Every fake
leaves a clue.
Paste the address you were sent. Clue reads its deployer straight off Robinhood Chain and gives you a verdict: the official $CLUE, a real pons launch that is not ours, or not a pons contract at all. Or type a ticker and count the copies. Pons and gmgn can list them. Only this page can say which one is ours.
__CA__
Not published yet. The contract address appears here and on @clueonpons at the same moment, baked into this page. If an address shows up anywhere before that, or the address on X and the address on this page ever disagree, it is a copy.
move to steer the lens
Reading Robinhood Chain over JSON-RPC, live, from your browser. No backend, no key.
Paste the address you were sent.
This is the product, and it works today. Paste a contract address and the page reads its bytecode off the chain, matches it against the pons_v2 token template, and returns one verdict. Type a ticker instead and it lists every contract on chain 4663 carrying the name, with the same check on every row. Public reads, no scoring.
Reading the chain…
- Paste an address for a verdict, or type a ticker to list every ERC-20 on chain 4663 whose name or symbol matches. Everything here is read from the chain's explorer and RPC live, in your browser.
Pons and gmgn can list the copies. Neither can say which one is ours.
The ticker namespace on Robinhood Chain is not policed, so a name search anywhere returns a pile of contracts. Listing them is not the hard part. The hard part is the binding: one address, published by the project in two places at the same moment, and a check anyone can repeat. Clue is that check, and it also sees contracts deployed outside pons, which a pons search never shows.
- 1. Bytecode read
- eth_getCode, live RPC
- 2. Template match
- pons_v2 token, 3,248 bytes
- 3. Creator read
- Blockscout, as confirmation
- 4. Factory match
- pons_v2 deployer
- 5. Official match
- the CA on this page
Every token the pons_v2 factory deploys is the same 3,248-byte contract with three embedded addresses that differ per token. Clue reads the bytecode from the RPC and compares it byte for byte outside those three slots, so the factory verdict needs no explorer at all. The explorer's creator read is the second opinion, when it answers. A contract that fails both was deployed some other way. That is not proof of a scam, but it is proof it is not a pons launch.
verdict(address):
code = rpc.eth_getCode(address)
factory = code ≡ PONS_V2_TEMPLATE # 3,248 bytes, 3 slots masked
or explorer.creator(address) == PONS_V2_DEPLOYER
official = address == CA on this page
no code → not a contract at all
official → the one to trade
factory → a real pons launch, not ours
otherwise → not a pons contract
Public reads only. Nothing is scored, weighted or guessed, so anyone can fetch the same bytecode from the RPC and get the same answer, even with the explorer down.
Paste
The address someone sent you, or a ticker if you want to see the whole pile. Clue takes either.
Read
Bytecode from the RPC. Creator and token facts from the explorer when it answers. Public reads, in your browser.
Compare
The bytecode against the pons_v2 token template, the creator against the pons_v2 deployer, the address against the one baked into this page.
Verdict
Official, a real pons launch that is not ours, not a pons contract, or not a contract at all. In big type.
Did you buy the real one? Connect and find out.
Connecting requests account access and nothing else. The page then lists every token in the wallet whose name or symbol contains CLUE and runs each one through the same verifier: official, a real pons launch that is not ours, or not a pons contract. At launch it also reads your balance of the official contract, and only that one. If you were sold a copy, this is where it shows.
No wallet connected. Connect one on Robinhood Chain and this panel lists every CLUE-named token it holds, each with a verdict.
MetaMask or any EIP-1193 wallet. If the wallet has never seen chain 4663 the page offers to add it, with the public RPC and explorer, and nothing else.
- Account
- —
- ETH balance
- —
- Transactions sent
- —
- Official $CLUE balance
- —
- reading the wallet's token list…
- eth_requestAccounts
- asks for your address
- eth_getBalance
- reads ETH
- eth_getTransactionCount
- reads the nonce
- eth_call balanceOf
- reads official $CLUE, at launch
- explorer token list
- finds CLUE-named holdings
- eth_getCode per holding
- verdict on each
- Send a transaction
- absent
- Ask for a signature
- absent
- Request an approval
- absent
A pre-launch site asking for a signature is what a drainer looks like. This one cannot, and you can check the script rather than take that on trust.
Read this part first.
The token that launches on pons_v2 is a plain ERC-20 with a fixed supply. The search on this page is a working tool built on public chain reads. This table is the honest state of the project and it is updated before anything else on the page.
| Thing | State | What that means | |
|---|---|---|---|
| Block height, gas, client string | Live | Read from Robinhood Chain over JSON-RPC in your browser, several times a second. | |
| The address verdict | Live | Paste any address: bytecode is read from the RPC and matched against the pons_v2 token template, creator and token facts come from Blockscout when it answers, and the verdict is derived from those reads and nothing else. | |
| The bytecode template | Live | The 3,248-byte pons_v2 launch token, with its three per-token address slots masked, is printed in the page script. Verified against five launched pons_v2 tokens on 6 September 2026. | |
| The ticker search | Live | Queries the chain's Blockscout index for every token whose name or symbol matches. Results are whatever the chain holds right now. | |
| The deployer check | Live | Each contract's creator is read from Blockscout and compared with the pons_v2 launch deployer address, which is printed in the page script. When the explorer is down, rows fall back to the bytecode fingerprint from the RPC. | |
| Wallet connect, balance reads, holdings audit | Live | EIP-1193 direct. Your ETH balance and transaction count are read from chain 4663 the moment you connect, and every CLUE-named token the wallet holds gets the same bytecode verdict as the verifier above. | |
| The token, at launch | At launch | Live | A fixed-supply ERC-20 launched through pons_v2. One billion units to a bonding curve, no presale, no team allocation. Its address is published here and on X at the same moment, baked into this page. |
| The official highlight | At launch | Live | Before launch there is no official CLUE contract, so a search for CLUE shows only copies and says so. After launch the official row lights up. |
| Anything beyond the search | Design intent | Alerts, a public API, and per-wallet watchlists are described in the roadmap and are not built. Nothing on this page promises them by a date. |
Fixed supply, stated plainly.
$CLUE on Robinhood Chain. Supply is fixed at launch and the figure above is read from the token contract with totalSupply once there is one to read. Before launch it is the intended number and nothing more.
CLUE. Clue Protocol, and the same word as the domain and the handle. Search it on this page and count the copies.
No buy or sell tax. A plain pons_v2 launch token: fixed supply, bonding curve, buyback vault as pons runs it.
Robinhood Chain, id 4663, an Arbitrum Orbit rollup. The client string in the strip above is read live.
The official CA lives on this page and in the @clueonpons bio. Nowhere else, ever. If the two disagree, one of them is a fake, and it is not this page.
Shipping in public, without dates.
Now
This page. The ticker search, the deployer check, live chain reads, and the wallet reader.
Next
Token launch on pons_v2. The contract address appears here and on X at the same moment, and the official row lights up in the search.
Then
Search any ticker on the chain, not only ours, with the official address supplied by the project's own verified account.
Later
Alerts when a new contract appears carrying a watched name, and a public endpoint so other sites can run the same check.
Straight answers.
Pons and gmgn already list every launch with a ticker. What is different here?+
Listing is not the product. Three things are. Clue searches the whole chain, so it also shows contracts deployed outside pons, which a pons search never returns. It reads provenance at the bytecode level, matching the contract against the pons_v2 token template from the RPC, not just reading a dev wallet off an index. And it holds the binding no aggregator can: one official address, baked into this page and posted in the X bio at the same moment, so a pasted address gets a verdict rather than a list.
Is the search real, or a mockup?+
Real. Type any ticker and the rows come from the chain's Blockscout index at that moment. Search PONS and you will see dozens of contracts carrying the name. Every deployer badge is a second live read. Open the browser's network panel and watch the requests if you like.
What does "pons_v2 factory" on a row mean?+
Every token launched through pons_v2 is the same 3,248-byte contract, created by the same deployer. Both the template and the deployer address are printed in this page's script. A row with the badge matched one or both. A row without it was deployed some other way. That does not make it a scam, but it does make it not a pons launch.
Which CLUE is the real one?+
Before launch, none. Search CLUE today and every row is a copy of a token that does not exist yet. At launch the official address is baked into this page and posted on @clueonpons at the same moment, and the matching row lights up. If the address on X and the address here ever differ, do not trade either.
Can this page move my tokens?+
No, and you do not have to take that on trust. Connecting requests account access and reads balances, which is all it does. Fetch the script and search it for the ERC-20 write selectors or any signing method; there are none.
Why does the search sometimes pause?+
The explorer rate-limits anonymous reads, so deployer checks are run a few at a time and cached for your visit. If the limit is hit, the page says so and the rows still show what the name search returned.
Is $CLUE a rebase, a vault, a yield token?+
No. It is a plain fixed-supply token launched on pons_v2, with a working tool attached to it. The tool is the point. Anything beyond the search is listed in the roadmap as intent, not as a feature.
One address. Every copy flagged.
Paste the address you were sent and read the verdict. Then check the address here against the one on X before you do anything else. The chain reads are real and nothing on this page can move a thing.
contract __CA_SHORT__No contract address yet. When there is one it is published here and on X at the same moment, and it will be in the page source rather than written in by script.