The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →To check a Polymarket trade, inspect its Polygon transaction and identify the exchange contract that emitted the fill. Compare that address with the matching standard CTF or NegRisk exchange address below. This classifies the exchange used for a fill—not a v1 or v2 label on the outcome tokens currently held in a wallet.
What the contract check tells you
The useful evidence is the transaction or trade record for an acquisition or sale. The exchange address associated with its fill can indicate whether that trade used a legacy or newer exchange, provided you also identify whether it was a standard CTF or NegRisk trade.
As an Amazon Associate I earn from qualifying purchases.
A wallet’s current token balance alone may not show which exchange executed each acquisition. Check transaction provenance for the particular fill you want to classify. The available sources do not establish that outcome tokens themselves carry a v1/v2 label, or that a token can be classified solely by its token ID.
Addresses to compare on Polygon
The third-party Substreams Registry polymarket-pnl package page lists the following exchange addresses. Treat them as a starting point and verify them against current official deployment information before relying on them for an action.
#1 Best Overall
| Exchange category | Legacy v1 address | Newer v2 address |
|---|---|---|
| Standard CTF | 0x4bfb41d5b3570defd03c39a9a4d8de6bd8b8982e |
0xE111180000d2663C0091e4f400237545B87B996B |
| NegRisk | 0xC5d563A36AE78145C45a50134d48A1215220f80a |
0xe2222d279d744050d28e00520010520000310F59 |
These are Polygon addresses, and the category matters: compare a standard CTF fill with the CTF row, and a NegRisk fill with the NegRisk row. Do not infer an exchange generation from an address without first identifying its role in the transaction.
How to check a particular fill
- Find the relevant fill. Open the transaction or trade record associated with the position acquisition or sale you want to inspect. If you have only a current balance, locate the transaction history for the acquisition; the balance by itself is not enough to establish which exchange handled it.
- Identify the emitting exchange. In the Polygon transaction details, locate the contract address that emitted or handled the fill. A wallet address, outcome-token contract, or unrelated contract in the same transaction is not the exchange address you are trying to compare.
- Determine the exchange category. Establish whether the fill was for standard CTF or NegRisk. The address comparison only works against the corresponding category in the table.
- Compare the full address. Match the exchange address character for character with the relevant legacy v1 or v2 entry. A match identifies the exchange associated with that fill according to the indexed address list; it does not by itself establish the history of every token currently in the wallet.
What is known about the transition
The Substreams Registry page reports that the v2 contracts were deployed on 2026-03-31 and that production cutover occurred at approximately 11:00 UTC on 2026-04-28. It describes v1 contracts as handling historical fills after that cutover. These dates and the address list are claims from a third-party indexed dataset, not an official Polymarket migration instruction.
Polymarket’s FAQ explains outcome shares and notes that they may be sold before an event resolves, but it does not provide a procedure for identifying the exchange behind a particular fill. Polymarket’s maintained CTF Exchange v2 source repository documents v2 architecture; its NegRisk collateral adapter takes a legacy Conditional Tokens contract address. That distinction is a reason not to conflate exchange generation with the underlying token contract, but it is not a complete migration policy or a user-facing checker.
Free tools Windows power users keep installed
One-click scans. No signup required.
Limits of the available check
No official user-facing guide was located that explains how to identify an individual position’s exchange generation from the Polymarket website alone. A Polymarket Rust client README describes protocol generations and says token-backed order protocols can be auto-detected through a version endpoint, while position-backed orders use Exchange V3. That is client implementation documentation, not a validated workflow for checking an already-held position: Polymarket Rust client README.
For a consequential decision, confirm the exchange address and deployment details in current official Polymarket documentation or contract records. The address comparison is evidence about a specific fill’s exchange provenance; it does not prove that holdings were migrated, that all acquisitions used one exchange, or that the indexed dataset is a complete official migration record.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
