AutonomOracle Terminal
Fair Fill Intelligence

Fill reliability dashboard

Track whether venues actually settle position requests. This is a request-to-settlement funnel: submitted requests become filled, cancelled/refunded, pending, or dropped if no matching settlement is seen after the configured drop window.

This is intentionally separate from price-quality. A non-fill claim is more serious than a bad-bps claim, so dropped requests stay inspectable by signature and correlation key.
time window
generated: · window: 30m· dropped after: Open venue performance →
most reliable now

No venue has enough successful resolved requests for this filter yet. Failed-only or zero-fill venues are shown below, but cannot be crowned most reliable.

0
requests
0
filled
0
dropped
fill rate
visual funnel

Request → settlement reliability

higher fill + lower drop/fail is better
No request lifecycle records for this window/filter yet.
recent request lifecycle

Inspectable request tape

click request, settlement, or correlation key to verify on Solscan
No recent request lifecycle records for this filter yet.
methodology
Fill reliability tracks order requests, not just settled fills. A non-fill is measured by request legs that never produce a matching settlement/cancel.
Dropped is conservative: no fill or cancel observed after the configured drop window. Pending means still inside that window.
GMX uses the order account as the correlation key. Position accounts are reused and are not used as request ids.
Every dropped request remains inspectable by request signature and correlation account before making any public venue claim.
Ranking is fill-rate first and penalizes failed+dropped outcomes. A failed-only or zero-fill venue is never eligible for the most-reliable headline.