Frequently asked questions

Yes. No account, no sign-up, no wallet connection. Paste a public Polymarket wallet address and read the result.

No — and you should be wary of anything that asks you to. Strategy Scanner never requests a wallet connection, a signature or a private key. It reads public data only. No legitimate wallet viewer needs your signature to show you someone else's public trading history.

No. Reading public blockchain and API data leaves no trace for the owner, and no notification is sent.

Any Polymarket wallet address — a 42-character string starting with 0x. You can also search by Polymarket username and pick the profile from the dropdown.

Because Polymarket's positions endpoint only returns what a wallet still holds or can still redeem. The moment a trader redeems a winner, that row is deleted. Losers stay forever as resolved rows worth nothing.

Adding it up therefore keeps the losses and discards the wins. Measured on a top leaderboard wallet, that sum gave −$663,368 for a wallet genuinely up around $3.6 million. Strategy Scanner takes lifetime PnL from Polymarket's own series and rebuilds per-market results from real USDC cash flows instead. The full derivation is in the guide.

Those metrics come from a bounded window of the wallet's most recent activity, not its whole life. The header states the window — how many events, and how far back. Portfolio value, cash balance, position value and Total PnL are not scoped that way; they cover the whole wallet.

Reconstructing a complete lifetime history is slow, and done partially it yields numbers that look authoritative without being reliable. An earlier build did exactly that and declared wallets “fully scanned” when they were not. Rather than repeat that, the window is bounded and labelled honestly. A deeper history engine is a separate, later phase.

Polymarket splits one question into bracket markets that resolve independently. One decision — who gets nominated, say — can appear as twenty-three near-identical rows. By event shows the decision; By market shows the individual executions underneath it.

A market is only scored when three things hold: money demonstrably went in, no outcome ends up short on shares, and no neg-risk conversion touched it. A negative share balance proves the buy happened outside the window; a conversion moves value between markets without a price, which a per-market cash replay cannot follow.

Excluded markets still appear in the tables — they are just not counted, and the page reports how many were counted out of how many were touched.

No. They sit in their own tab, split into liquidity rewards, maker rebates, taker rebates and yield. A wallet can earn well from market-making while making very few profitable directional bets, and merging the two would hide exactly that.

Check the window stated under the header first — a Recent figure only covers that span. Then compare markets analysed against markets touched. Then open the row on Polygonscan and verify the transaction yourself. If it still looks wrong, tell us the wallet address and what you expected.

No account data, because there are no accounts. Your recently scanned wallets and your theme choice live in your own browser's local storage and are never sent to the server. The server keeps a short-lived cache of public Polymarket data keyed by wallet address, and IP addresses briefly in memory for rate limiting. The privacy policy has the detail.

Polymarket's public APIs for positions, activity and the PnL series, and a public Polygon RPC node for live token balances. Polymarket's API is an index of Polygon's own event log, so this is chain data — and every trade row links to Polygonscan so you can confirm it independently.

Positions refresh within about twenty seconds, the PnL series within a minute, and recent activity within a few minutes. Caching exists so that hundreds of people viewing one wallet cost Polymarket a single request rather than hundreds.

There is nothing stored to remove — no wallet is enrolled, listed or indexed here. Wallet pages are excluded from search engines, and the cache expires on its own within minutes. Polymarket activity is public on the Polygon blockchain and is outside anyone's ability to erase.

That view decoded Polygon transfers, took around 48 seconds to load, and still returned an undercount because the public nodes it relied on have pruned the older blocks. It was pulled rather than shipped misleading, and returns when it can be done properly.

Paused, not removed. Replaying someone's fills against your own balance only means something with a complete fill history, which this version deliberately does not read.

Not currently. The data layer is isolated behind one adapter, so other prediction markets are feasible later, but nothing else is supported today.

Not a public one. The endpoints behind the interface exist to serve it and are rate limited accordingly. If you want programmatic access, the CSV and JSON exports are the supported route.

No. Strategy Scanner reports what public data shows about past activity, nothing more. Past performance does not predict future results, and mirroring a large trader at a small size behaves very differently from the original.