Publish fork bootnodes and write a bundle manifest - #130
Closed
mordamax wants to merge 1 commit into
Closed
Conversation
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
1 participant
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 #129 — review that first; this PR's diff is only its own changes and will retarget to main when #129 merges.
--publish-bootnodeswrites the spawned network's own multiaddrs into the published chain-specs, so artifacts are dialable off the box. Opt-in, so the default staysbootNodes: [].manifest.jsonnext toready.json: per chain the bite block, source RPC, spec/snapshot files with sizes, any carried upgrade and its hash, plus thedoppelgangerversions that produced the snapshots.spawnwarns when local binaries differ, since a snapshot from a newer node fails to restore in ways that look like corruption.Closes #123
Closes #126