fix: refresh all network genesis hashes (0.12.1) - #44
Merged
Conversation
mordamax
approved these changes
Aug 14, 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
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
All three built-in network genesis hashes pointed at chains that no longer exist. This updates them to the values the chains return today and releases 0.12.1.
PASEO_ASSET_HUB0xbf0488...ef19f0x23e730eb1c6fecae09c917439a5038cb6122d0d48980e8b9bbf0ff56f94a2ca6PREVIEWNET0x477dd8...125250x8c27ddf678c2ae9bef0efebfc485a9309f3d735c6d3fbb8d947afc3ace0e80f4PREVIEWNET_ASSET_HUB0x860d75...c7867c0x4d11c803cc6921429e3876638977ad006ea1bba8cd3976a0bca2f164e7026210Changes
src/networks.tsgenesisHashliterals.rpcUrls are unchanged, all three endpoints respond.test/integration.spec.tsPASEO_ASSET_HUB.genesisHash.package.json0.12.0to0.12.1.CHANGELOG.md,forum-post.mdCLAUDE.md.README.mdneeds no change, its network table lists export names and no hashes.Why these changes
The host routes each connection request to a network by genesis hash. A stale pin means the host does not recognise the chain a product asks for, so the product hangs at
connection-status: "connecting"until the test times out. The RPC endpoint is reachable and nothing looks wrong in the logs, which makes this expensive to diagnose.This blocks paritytech/product-sdk#297, where four demos fail
boot.spec.tsfor exactly this reason.Testing
Verify the pins against the live chains: