Boot dotNS v0.8.0 from genesis - #24
Merged
Merged
Conversation
mordamax
approved these changes
Sep 15, 2026
Signed-off-by: Cosmin Paraschiv <cosmin@parity.io>
csmnprschv
approved these changes
Sep 15, 2026
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
3 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.
Description
Pins
DOTNS_TAGtov0.8.0. Its genesis is the first that declares itself on chain: a booted network answersprotocolVersion()with"0.8.0"and carries a declared codehash per registered contract from block zero, so it can be verified against the release.ppn fetchnow buildsdotns-addresses.jsonfromdeployments/expected.jsonat the tag. The genesis is built by running the dotns deploy pipeline on a fresh chain, so a network booted from it holds exactly the fresh-deploy address set;expected.jsonrecords that set and dotns CI parity-checks the genesis against it, so the two cannot disagree. The previous source, the live paseo manifest, records what a running testnet has and lags each release until that testnet upgrades.After boot,
cast call <DotnsProtocolRegistry> 'protocolVersion()(string)'against the previewnet eth-rpc should answer0.8.0.