Repository navigation
Conversation
markettes
force-pushed
the
feat/simple-auto-channel-open-data
branch
from
October 30, 2026 18:26
d9a5091 to
ded13c5
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First of a four-PR stack that replaces #615–#621 with the simpler rule from review: open a fixed-size channel to a peer whose route has been earning fees and that we recently couldn't serve for lack of outbound.
Adds the ChannelOpenRecommendation entity, one row per node and peer, holding the evidence (earned fees, amount routed, refusals, usable outbound, capacity) plus the size and fee policy it would open at, with its lifecycle statuses. Node gets the per-node settings: enabled, mode, funding wallet, fixed channel size and a budget with its refresh interval. One migration, AddAutoChannelOpen.
Repositories: recommendations (upsert, expire, fail unrealized promotions, last decision per peer for the cooldown), per-channel aggregates over ForwardingHtlcEvents grouped in the database (earned fees, settled out, INSUFFICIENT_BALANCE refusals), nodes with the feature on, and sats committed to opens since the budget period began. Defaults live in Constants.
Nothing reads this yet; the job comes in the next PR.