Publish the fork's own nodes as bootNodes, optionally under a public host - #132
Merged
Merged
Conversation
pepoviola
approved these changes
Aug 29, 2026
pepoviola
left a comment
pepoviola
left a comment
Collaborator
There was a problem hiding this comment.
Looks good, the only qq is if we have a simple way to get the patched spec to use after spawn
pepoviola
added a commit
that referenced
this pull request
Aug 31, 2026
* Verify overrides against chain metadata, patch live HostConfiguration * Address review: error on required items, pin reads to bite block, test metadata paths * Write a bundle manifest describing the bite artifacts * Publish the fork's own nodes as bootNodes, optionally under a public host (#132) * Pack a step's artifacts into one restorable bundle (#136) * Publish the fork's own nodes as bootNodes, optionally under a public host * Pack a step's artifacts into one restorable bundle --------- Co-authored-by: Javier Viola <363911+pepoviola@users.noreply.github.com> * Address review: drop binary-version tracking from the manifest --------- Co-authored-by: Javier Viola <363911+pepoviola@users.noreply.github.com>
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
2 participants
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.
Stacked on #131.
A published chain-spec ships with
bootNodes: [], so a node this process did not start has no way to find the fork — the peer wiring only exists in the spawned nodes' arguments.--publish-bootnodes [<host>]fills the list with the fork's own nodes: no value publishes the loopback addresses (same-host consumers), a value advertises that name instead, rewriting only the host (/ip4/127.0.0.1/…→/dns4/<host>/…, or/ip4/for a literal IP) and keeping port, transport and peer id. Same model asppn service patch-bootnodes.Addresses are captured while the network is up but written after the artifacts are generated, so the reusable
bitebundle is untouched and only the published one advertises this run's nodes. Specs are matched by their ownpara_idrather than by file name, since a fork carries the source chain's spec id (collectives_polkadotvs the file'scollectives-polkadot).Closes #123