FillProof Verify · don't trust

Settlement coverage

FillProof verifies a fill by finding it on the Polygon chain, at the contract that settled it. This is the list of contracts we scan, and the ones we do not. It is generated from the scanner's own configuration, so it cannot disagree with what the scanner does.

Contracts we scan

A fill that settled at one of these can be matched on chain and, where marked, have its fee cross-validated.

Contract From block Fee verified
0xe111…996b
0xe111180000d2663c0091e4f400237545b87b996b
ctf-exchange
84,902,353 yes
0xe222…0f59
0xe2222d279d744050d28e00520010520000310f59
ctf-exchange-neg-risk
85,058,176 yes
0x4bfb…982e
0x4bfb41d5b3570defd03c39a9a4d8de6bd8b8982e
ctf-exchange-v1
33,605,403 not yet measured
0xc5d5…f80a
0xc5d563a36ae78145c45a50134d48a1215220f80a
ctf-exchange-neg-risk-v1
50,505,492 not yet measured

Where this says not yet measured, we match fills at that contract but have not verified that our reading of its fee matches the chain. Fees on those fills are reported as unknown, never as zero.

Contracts we do not scan

These settle real activity and we exclude them deliberately. A fill that settled at one of these appears on your report as unmatched — never counted as verified.

0xe3333700ca9d93003f00f0f71f8515005f6c00aa

This contract behaves like a Polymarket exchange in every way we can test, but we cannot establish which markets it settles — so we do not claim to have checked anything that settled there.

UNIDENTIFIED CONTRACT, UNDER INVESTIGATION (ruled 2026-11-07). a CTF Exchange V2 deployment by every structural test — same proxy pattern, same three events, 4 topics/7 words, prices are probabilities on 885/885 rows. But WHAT IT SETTLES is unknown: its token ids are STRUCTURED (<prefix><zeros><0000|0001>, in outcome pairs, 874/874 rows against 0/90,499 on covered venues) rather than keccak-derived, and gamma resolves 0/25 of them against 14/25 and 25/25 on the covered venues. ~1.0% of rows and rising, up from 0.4%. Scanning it would be safe and cheap; naming what it settles is unestablished, so it is excluded and said rather than included on a guess.

0xd91e80cf2e7be2e162c6513ced06f1dd0da35296

This contract converts and settles positions rather than matching trades, so it emits no fill events at all — a position changed through it will not appear in your report, and is not counted as verified.

the neg-risk ADAPTER. 15,310 logs over 2,000 blocks and NOT ONE OrderFilled — it converts and settles positions rather than matching orders. Position changes through it are real economic events that no amount of OrderFilled scanning will ever show.

How much settles where we do not look

0.84% of the fill events we observed settled on contracts we do not cover. That is a median over 24 hourly samples taken between 19 November 2026, 10:43 and 20 November 2026, 10:45 UTC, covering Polygon blocks 97,586,260 to 97,644,039 and 141,234 fill events in total.

Of that, 0.84% settled on contracts listed below with a stated reason, and 0.00% on contracts we have not yet explained. Both are uncovered; only the second is something we cannot account for.

Where those events settled:

ContractEvents Share of observed
0xe3333700ca9d93003f00f0f71f8515005f6c00aa 1,218 0.86%

What this list is not

The percentage above inherits that blind spot: its denominator is the events we saw, so a contract emitting a signature we have never seen contributes to neither side of the fraction. It is the figure we use internally to notice a known gap growing, and it is published here with its denominator named rather than withheld.

Back to FillProof