chore: update IPFS bootstrap peer addresses - #162
Merged
Merged
Conversation
Swap the two fixed bootstrap/swarm peers to the new IPs/peer IDs: - 65.109.51.31 -> 65.109.48.56 (peer 12D3KooWLdrSru7LzYY4YDcfnJsrJeshTQooR2j38NkGvoj2yADp) - 167.86.114.131 -> 65.108.192.207 (peer 12D3KooWDwELw6jSdihhM9tv5yGXVgLSr3VVYcV2FjBm2j5pyUPF)
Contributor
|
Dappnode bot has built and pinned the built packages to an IPFS node, for commit: dd3f102 This is a development version and should only be installed for testing purposes.
Hash: (by dappnodebot/build-action) |
Contributor
🛠️ Package harness worker error
Note This is a harness infrastructure or worker failure, not a package verdict. Retry after resolving the reported condition. |
This file contains hidden or 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.
Context
The two fixed IPFS bootstrap / swarm peers used by this DAppNode package were outdated. This PR swaps them to the new public IPs and Peer IDs.
Approach
Update
src/configure-ipfs.shso the post-config script:bootstrap addandswarm connectto the two new peers:/ip4/65.109.48.56/tcp/4001/p2p/12D3KooWLdrSru7LzYY4YDcfnJsrJeshTQooR2j38NkGvoj2yADp/ip4/65.108.192.207/tcp/4001/p2p/12D3KooWDwELw6jSdihhM9tv5yGXVgLSr3VVYcV2FjBm2j5pyUPFRemoved (stale) entries:
/ip4/65.109.51.31/tcp/4001/p2p/12D3KooWLdrSru7LzYY4YDcfnJsrJeshTQooR2j38NkGvoj2yADp/ip4/167.86.114.131/tcp/4001/p2p/12D3KooWCAx5zWejUDotqc7dcvpvNstM9eZRdtdne1oXZ1DpdLFbNo other files or behaviour are affected.
Test instructions
ipfs bootstrap list— should contain exactly the two new multiaddrs and nothing else (besides default IPFS bootstraps).ipfs swarm peers | grep -E '12D3KooWLdrSru7LzYY4YDcfnJsrJeshTQooR2j38NkGvoj2yADp|12D3KooWDwELw6jSdihhM9tv5yGXVgLSr3VVYcV2FjBm2j5pyUPF'— should list both new peer IDs once they connect.