Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add channel reserve as a constraint during order matching/expression #403

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ffranr
Copy link
Contributor

@ffranr ffranr commented Oct 31, 2022

Pull Request Checklist

  • LndServices minimum version has been updated if new lnd apis/fields are
    used.

/*
Signals if this bid is interested in a minimal reserve channel.
*/
bool min_reserve_channel = 10;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding is that there isn't anything endogenous to a "minimum reserve" channel that distinguishes it from another channel. That the distinguishing factor need to be produced by Pool, is the bidder is in essence setting a stipulation on the asker's performance, that their node update channel balances to channel-reserve levels Pool hasn't supported before (and hence what is considered "minimum reserve" is super nebulous and could change in the future).

Let's discuss internally how to best create matches around this property

@dstadulis
Copy link
Contributor

For the record, per 2022-11-08 meeting this feature will be removed from sprints until work could resume in 2023-Q1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants