cli: Ensure chainSpec's bootnodes are still reachable on the p2p network
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 293
- Avg merge
- 18h 35m
- Merged PRs (30d)
- 3
Description
The correctness of any light-client depends heavily on the list of provided bootnodes.
Establish a connection on the p2p network with boot nodes to ensure they are still alive.
The following protocols should be probed:
- ping: Check if bootnode is reachable
- identify: The bootnode must support protocols that align with the
fork/genesis_hashspecified in the spec
Should be done after the following is closed:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #1263, which must be closed first, then trace how the CLI obtains and uses chainSpec bootnodes. The work is done when bootnodes are probed with ping for reachability and identify for protocols matching the specified fork/genesis_hash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100