-
Notifications
You must be signed in to change notification settings - Fork 404
Wrap transaction creation keys #664
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
Wrap transaction creation keys #664
Conversation
Codecov Report
@@ Coverage Diff @@
## master #664 +/- ##
==========================================
+ Coverage 91.30% 92.12% +0.82%
==========================================
Files 35 35
Lines 21400 23242 +1842
==========================================
+ Hits 19539 21412 +1873
+ Misses 1861 1830 -31
Continue to review full report at Codecov.
|
812d2d6
to
61c28c1
Compare
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.
The two new commits basically LGTM. Would be nice to add a new sentence to the old TxCreationKeys docs to indicate that its the "trusted" version, and then can just make the full key set pub.
61c28c1
to
182516a
Compare
doc and pub change done |
182516a
to
b8fe822
Compare
Allows calling of InMemoryChannelKeys methods. The wrapping makes it obvious to signer implementers that the pre-derived keys are a local cache and should not be trusted in a validating signer.
This makes it obvious to signer implementers that the pre-derived keys are a local cache and should not be trusted in a validating signer.
b8fe822
to
6f635c6
Compare
I made this PR independent of #662 and incorporated the |
Oops, got trigger-happy with a "nit" commit. Oh well, we'll survive. |
And make them public. This allows calls to
InMemoryChannelKeys
.The wrapping of TxCreationKeys makes it obvious to signer implementers that the pre-derived keys are a local cache and should not be trusted in a validating signer.