Release v0.1.0 — M1, the transparency core · FairLaneRouter/FairLane-Router

The indexer, the database, GET /v1/summary with its SSE stream, the live
board and the methodology page, all running on real mainnet data.

Measured on the deployed product (2026-09-22):

SC-001, a landing visible in the public summary after confirmation (p95) —
17.8 s against a budget of 60 s. 58 data points over 26 minutes, 1397
polls, 0 failures; p50 14.1 s, worst case 18.6 s, none over budget.
SC-002, first screen on a 3G connection — 1.76 s against a budget of 2 s.
Chrome "Fast 3G" profile, 3 runs on github.io (1.73 / 1.76 / 1.81).
Before the optimisation it was 2.54 s.

Not measured here, and this has to be said out loud:

SC-003 is checked by hand on 100 landings. A control set with an
independently known channel is only possible from M3 on, once the system
sends transactions itself.
SC-007 and SC-008 need accumulated history and 30 days of collection.
SC-005 and SC-006 cannot be measured by construction: the dashboard shows
what the channels charge, not what could be saved by choosing between
them. There are no recommendations, no sends of our own and therefore no
proof of savings in this release — that is M2 and M3.

Navigation Menu