Skip to content

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

Closed
5 of 8 tasks
TheBlueMatt opened this issue Aug 25, 2018 · 7 comments · Fixed by #143
Closed
5 of 8 tasks

Work through each BOLT and fill out error conditions #129

TheBlueMatt opened this issue Aug 25, 2018 · 7 comments · Fixed by #143

Comments

@TheBlueMatt
Copy link
Collaborator

TheBlueMatt commented Aug 25, 2018

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 1
  • BOLT 2
  • BOLT 3
  • BOLT 4
  • BOLT 5
  • BOLT 7
  • BOLT 8
  • BOLT 9

BOLT 10 we don't have any implementation of yet (#58), and BOLT 11 is in rust-lightning-invoice.

@TheBlueMatt
Copy link
Collaborator Author

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.

@TheBlueMatt
Copy link
Collaborator Author

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.

@TheBlueMatt
Copy link
Collaborator Author

Lol, github got a bit overeager, sadly.

@TheBlueMatt
Copy link
Collaborator Author

Yay BOLT 7!

@TheBlueMatt
Copy link
Collaborator Author

Technically we know about all the various flags, even if we dont implement all the optional ones (see #236) so BOLT 9 is "implemented".

@ariard
Copy link

ariard commented Jul 29, 2019

@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)

@ConorOkus ConorOkus moved this to Todo in LDK Roadmap Dec 7, 2021
@ConorOkus ConorOkus moved this from Todo to In Progress in LDK Roadmap Dec 7, 2021
@TheBlueMatt
Copy link
Collaborator Author

ErrorAction has been required for quite some time.

@github-project-automation github-project-automation bot moved this from In Progress to Done in LDK Roadmap May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants