-
Notifications
You must be signed in to change notification settings - Fork 30
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
GET channel request spec should specify possible values for "state" enum string #15
Comments
these two states are intentionally broad to limit complexity for implementing state updates on the LSP side |
but happy to consider more granular states if people want that |
My instinct is more granular, like PAID, PARTIAL_PMT, REFUNDED, FAILED, RETRYING, or such... but I defer to our actual node admins. |
Proposal. Please let me know if you are missing something or you disagree with any states:
|
these look great to me. only nit is I think we could come up with a cleaner name for |
Sure, let it be |
In the response of the GET channel request, it is unclear what the possible values for
state
should be.I suggest two states:
PENDING
(channel has been requested but the open has not been initiated yet. it may be none, partially, or fully paid for at this point, which the user can deduce from theamount_paid
variable)OPEN_INITIATED
(the channel opening transaction has been broadcast. provides no info whether it has confirmed or is active yet)thoughts?
The text was updated successfully, but these errors were encountered: