-
Notifications
You must be signed in to change notification settings - Fork 1
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
Use external transport crate #366 #367
Conversation
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 looks good to me. Waiting to approve until I have a chance to double-check the transport crate, but it seems like you have a good abstraction. My comments are almost all formatting.
Review of the transport crate: As discussed on slack, we might want to add a callback to the
It looks to me like there aren't major changes in the transport crate except maybe adding an |
With regard to the transport crate, indeed, not much changed, it's basically the same with the exception of the abstract Trait |
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.
Thank you for the fixes. My only remaining recommendation is to update the rustfmt.toml
with the imports_granularity
specification - it looks like that file already supports unstable features, although I'm not sure which ones. Mukund may have mentioned something about line-wrapping documentation, but I think that is an issue for a different PR.
Before merging, we should merge boltlabs-inc/transport#1, and change the transport dependency back to "main" branch |
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, approving pending the transport fix.
The extracted transport crate can be found here: https://github.com/boltlabs-inc/transport
We should make sure it all still makes sense, including the level of abstraction.
Specifically, the feature
allow_explicit_certificate_trust
, does that make sense to also live inside the transport crate, I do believe so, but just checking. Also, the abstraction forZkChannelAddress
that now implements the traitAddress
, which is part of the transport crate.