Concepts
Verification
The five checks a quote must pass before it can win.
Verification decides which quotes are allowed to win. In the current version every quote runs five checks. All five must pass. The result is stored on the quote as verification.checks, one entry per check with name, ok and a human-readable detail.
| Check | Passes when |
|---|---|
price_within_max | The quote's price is at or below the order's max_price. |
provider_active | The quoting provider is active, not paused. Providers pause and resume with PATCH /v1/providers/me. |
serves_type | The provider lists the order's type among its types. |
quote_not_expired | The quote's expires_at has not passed. |
endpoint_reachable | The worker sends an HTTPS request to the provider's endpoint_url with a 3 second timeout and gets any HTTP response below 500, or a 402. |
Checks run when the quote arrives. At fill time the matcher also skips quotes that have expired since and quotes from providers that are now paused.
What v1 does not check
- The content of the provider's response to the actual call. Response checks are part of the whitepaper's design, but the method is TBD.
- The free-text
ruleon an order. It is stored and shown, not enforced. - Who verifies, and how disputes are handled. Both are open items (TBD).
Do not read a
verified quote as a guarantee of quality. In v1 it means the price fits, the provider is active, serves the type, the quote is fresh and the endpoint answered.The whitepaper plans for $FILO holders to vote on verification rules. See Governance.
Was this page helpful?