keys manager implementation for using custom channel secrets and private key #122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request contains the implementation I made for my summer of bitcoin project "Integrating LDK with Lnprototest".
This includes:
keysmanagerimplementation for using custom private key and channel secrets which can be passed as command line arguments.keysmanageropenchannel_without_peer_addrfor opening a channel with a peer whose already connected(required for lnprototest integration)Example usage:
cargo run polaruser:polarpass@127.0.0.1:18443 ./ 8889 regtest 0000000000000000000000000000000000000000000000000000000000000001 0000000000000000000000000000000000000000000000000000000000000010/0000000000000000000000000000000000000000000000000000000000000011/0000000000000000000000000000000000000000000000000000000000000012/0000000000000000000000000000000000000000000000000000000000000013/0000000000000000000000000000000000000000000000000000000000000014/FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFHere:
private key = 0000000000000000000000000000000000000000000000000000000000000001
funding_key = 0000000000000000000000000000000000000000000000000000000000000010
revocation_base_key = 0000000000000000000000000000000000000000000000000000000000000011
payment_key = 0000000000000000000000000000000000000000000000000000000000000012
delayed_payment_base_key = 0000000000000000000000000000000000000000000000000000000000000013
htlc_base_key = 0000000000000000000000000000000000000000000000000000000000000014
commitment_seed = FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF