paritytech / paritytech/zombie-bite
Populate bootNodes with the spawned fork's own node addresses
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12
- Forks
- 7
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 6
Description
Sub-task of #119 (item 3).
generate_chain_spec clears bootNodes, which is safe but leaves published specs unusable off the box - peer wiring lives only in the spawned nodes' args. After spawn, write the fork's own node addresses into the specs (or expose a hook), so consumers don't each need a patch-bootnodes step.
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 at generate_chain_spec and trace the fork-spawn path to see where the spawned nodes' addresses become available. Determine whether writing those addresses into the generated specs or exposing a hook fits the existing flow. Done means consumers can use the published fork specs without a separate bootnodes patch step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100