First LI.FI Intents Loop
Run the bounded LI.FI solver checks before unattended operation.
What You Will Prove
This tutorial proves that the LI.FI configuration can be read, identity can be checked, and the serve loop can run one bounded iteration.
It does not ask you to leave an unattended solver running.
1. Check Readiness
pnpm --filter @steerprotocol/collateral-rail-quote-server lifi:readiness -- --strictThis should report whether the solver identity, quote routes, uploaded quotes, orders, and configured routes line up for the active LI.FI environment.
2. Run One Loop
pnpm --filter @steerprotocol/collateral-rail-quote-server lifi:serve -- --live --onceUse --once first. It keeps the experiment bounded and makes the output easier
to review.
3. Read The Report
Look for:
- identity readiness.
- quote publish results.
- selected order validation.
- replay storage status.
- fill plan or fail-closed reason.
- finalise plan only when status payloads support it.
What Happened
lifi:serve is the operational loop. It can refresh quotes, poll orders, dedupe
order ids, derive build requests, generate hook material, fill, and reconcile.
The single-iteration mode is the bridge between local confidence and unattended
operation.