Skip to main content
If you take a wallet address from a Polymarket profile, a leaderboard, or from polynode’s prediction-market endpoints and ask the perps exchange about it, you will usually get nothing back. This page explains why, and what polynode does about it.

​
Two addresses per user

Most Polymarket users trade prediction markets through a proxy wallet — a small smart contract deployed for them on Polygon. That contract address is their public identity: it is what appears on their profile page, on leaderboards, and in every prediction-market dataset (including polynode’s /v3 wallet endpoints). The perps exchange identifies users differently: by the signer — the private-key account that controls the proxy. The signer is not shown on the Polymarket frontend, and there is no public endpoint that translates one into the other. So a user’s prediction-market history lives under one address, and their perps account lives under another. Without the mapping, you cannot connect them.

​
What polynode does

Every perps wallet endpoint accepts either address form and resolves it server-side: 
# Polymarket profile (proxy) address — resolved to the perps account automatically
curl "https://api.polynode.dev/v3/perps/wallets/0x09b428f7c2b469786286214aa5c90dd9015f7320?key=$KEY"
The response always tells you what was resolved: 
{
  "input": "0x09b428f7c2b469786286214aa5c90dd9015f7320",
  "wallet_type": "deposit",
  "signer": "0x509e390373f5bde0bb02c1019ee39cf0ef23a1a4",
  "registered": false
}
The relationship between a proxy and its signer never changes, so once an address has been seen, repeat lookups are instant.

​
Wallet types

Polymarket has used a few different wallet types over the years, depending on how an account signed up. wallet_type tells you which one you’re looking at, using Polymarket’s own names:
wallet_typeWho has oneResolution
eoaUsers trading with a plain wallet, no Polymarket contract at all.The address is its own perps account.
depositEvery new Polymarket account — the deposit wallet is the current standard.Resolved automatically.
safeOlder accounts that signed up by connecting a browser wallet (MetaMask etc.) — these got a Gnosis Safe.Resolved automatically.
proxyOlder accounts that signed up with an email login — these got a Polymarket Proxy.Not yet resolvable — see below.

​
”Deposit wallet” vs “beacon wallet”

If you’ve seen both terms: they’re the same thing. The deposit wallet is Polymarket’s current wallet type, and the newer ones are built so Polymarket can upgrade all of them at once — that upgradeable variant is what gets called a “beacon wallet”. There’s also an earlier, standalone variant from before that change. Both behave identically, both resolve automatically, and this API reports both simply as deposit — you never need to tell them apart.

​
The proxy-wallet edge case

Email-login accounts use a Polymarket Proxy wallet whose owner cannot be resolved automatically yet. For these, requests return 422 with a clear error: 
{
  "error": "polymarket proxy wallet",
  "detail": "this is a Polymarket Proxy wallet (email-login accounts); automatic resolution is not available for these yet — pass the account's signer address directly",
  "address": "0xf0318c32136c2db7fec88b84869aee6a1106c80c"
}
If you have the account’s signer address from another source, pass it directly — everything works from there. Automatic resolution for proxy wallets is on our roadmap.

​
Registration

Having a signer does not mean the user trades perps. Most Polymarket users have never activated a perps account. Check cheaply with: 
curl "https://api.polynode.dev/v3/perps/wallets/0x.../registered?key=$KEY"
Once an account shows registered: true it stays that way; accounts that were false are picked up within minutes of activating, so newly onboarded perps users appear quickly.