-
Notifications
You must be signed in to change notification settings - Fork 406
Work through each BOLT and fill out error conditions #129
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
Comments
I think we're already good on BOLT 8 as there aren't really any "requirements" in it aside from the crypto spec, which we handle fine, and any errors result in disconnection, which I believe is correct. |
AFAICT, BOLT 3 stuff is all correct, again there aren't many requirements there just a list of scripts and tx formats, all of which should pretty immediately result in failing to send signatures to channel peers, but I read through it again as well and didnt see anything obvious. |
Lol, github got a bit overeager, sadly. |
Yay BOLT 7! |
Technically we know about all the various flags, even if we dont implement all the optional ones (see #236) so BOLT 9 is "implemented". |
…rwarding-tests # Conflicts: # src/ln/channelmanager.rs
@rrybarczyk, this one should be a good first issue if you're looking for something to hack on, and nice to understand the whole procotol :) (generally moar tests are always well welcomed) |
|
Uh oh!
There was an error while loading. Please reload this page.
Need to make sure we're compliant with all the various actions we're supposed to take as specified in the BOLTs, as well as ensure ErrorActions are always Some() in HandleError. Some of these should be pretty easy, some will be way more involved.
BOLT 10 we don't have any implementation of yet (#58), and BOLT 11 is in rust-lightning-invoice.
The text was updated successfully, but these errors were encountered: