Under the hood
How the toolkit thinks and how it works — the design calls behind it and the mechanics of the moving parts. Written to be reviewed and argued with.
Design notes
The reasoning behind the main design decisions, and the trade-offs taken.
System overview: how the pieces fit together
The whole picture in one diagram — node, engine, database, CLI, cron, Claude, Telegram and dashboard — and exactly how each part talks to the others.
Read →Setting fees: a sigmoid with a cost floor
Mapping a channel's balance ratio to an outbound fee through a logistic curve, then flooring it at the measured cost of refilling — with worked numbers.
Read →Choosing peers for reach, not centrality
Why connecting to the big hubs often adds nothing, and a two-stage ranking that scores how much a candidate would extend our reachable horizon.
Read →Budgeting rebalances from a single signal
How one measured number caps spend, escalates on failure, chunks against liquidity limits, and why we use it over a tiered scoring model or a rolling median.
Read →Primary and fallback rebalance routes
How the planner lays out one primary route per depleted channel plus secondary fallbacks, then lets two ledgers decide which actually fire.
Read →Internals
For more details, refer to the code docs on GitHub: github.com/lnbright/ln-operator/docs.