feat: generate and use private key from environment variable and add support for dnsaddr seed peers #27
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.
Description
In order to generate a private key earlier that can be used at any start from env vars, we needed a solution.
Now there is a new cli option called
--generate-identity
. With this option, you can generate a new identity (an encoded libp2p private key) that can be used to set value later forSHA_P2POOL_IDENTITY
environment variable (the command outputs a json whereprivate_key
field is the one need to use).If that var is set, when starting p2pool with
--stable-peer
flag, it will look for first for this env var and tries to decode and use it.Also
/dnsaddr/*
seed peer addresses were not supported, now it is supported, so p2pool will parse all the TXT DNS records and add them to kademlia to bootstrap.Motivation and Context
How Has This Been Tested?
After starting/stopping many times p2pool, the peer ID remains the same.
What process can a PR reviewer use to test or verify this change?
See testing.
Breaking Changes