-
Notifications
You must be signed in to change notification settings - Fork 388
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
Make message fields public #665
Make message fields public #665
Conversation
Codecov Report
@@ Coverage Diff @@
## master #665 +/- ##
==========================================
+ Coverage 91.36% 91.40% +0.04%
==========================================
Files 35 35
Lines 21703 21703
==========================================
+ Hits 19828 19838 +10
+ Misses 1875 1865 -10
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems good to me.
8a1cba4
to
8a281d0
Compare
f004fcf
to
3025ad6
Compare
Documented the rest of the messages. I did skip onion related messages and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of the docs could use a bit more detail, but looks good. I agree excess_data stuff should not be included, its there just for serialization round-trips and should never be set by users.
/// The channel ID | ||
pub channel_id: [u8; 32], | ||
/// The HTLC ID | ||
pub htlc_id: u64, | ||
pub(crate) sha256_of_onion: [u8; 32], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not expose this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't expose any of the onion stuff and this one by itself would not be useful. Should I expose these?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall sounds good to me, we don't have to describe in details how each field must be processed, just their protocol semantic.
Code Review ACK 010d4ba Purpose of this PR arises in the context of increasing the scope of data verifiable by the external signer. I think comments are good enough to export fields. We can have follow-ups to describe implementation requirements with regards to processing/verifying message semantics (see #665 (comment)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good mod three slight comment notes.
010d4ba
to
39183c7
Compare
39183c7
to
500c00a
Compare
No description provided.