chore(descriptors): re-pin paseo chains after genesis reset - #297
Merged
Conversation
📦 Bundle size impactComparing
Thresholds — warn: ≥10% or ≥5.0 KB · fail: ≥20% or ≥15.0 KB (bundled). Percentage only applies once the baseline is ≥ 10 KB. |
Imod7
marked this pull request as draft
August 13, 2026 17:05
Imod7
marked this pull request as ready for review
August 14, 2026 17:42
TarikGul
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
paseo-individualityandpaseo-asset-hubwere re-genesised. The bundled descriptors stillpinned the old genesis hashes, so they addressed chains that no longer exist. This re-pins
both from their live RPC and updates the two places that hard-coded the old values.
paseo-individuality0xc5af1826…65afa50x89a63b11…48c5440fpaseo-asset-hub0xbf0488db…ae4ef19f0x23e730eb…f94a2ca6Changes
descriptors/.papi/metadata/paseo_*.scaledescriptors/chains/paseo-*/.papi/polkadot-api.jsongenesisandcodeHashdescriptors/chains/paseo-*/generated/package.jsonchain-client/src/presets.tsexamples/*/e2e/fixtures.ts(8)PASEO_ASSET_HUB.genesisHash, not a literalpending-changesets/descriptors-paseo-genesis-reset.mdminorpnpm-workspace.yaml@parity/host-api-test-sdkto^0.12.1pnpm-lock.yaml--frozen-lockfile, so the release does not reach CI without thisNote for reviewers: version bump
The changeset is
minor. Previous descriptor re-pins werepatch, so this is a departure,but not a judgement call: the
paseo-individualityregeneration removes typed APIsurface, and on 0.x a removal is how a breaking change is signalled.
ResourcesFriendRequest*constants (4 return asNotification*)GameNfts,NftCandidates, no replacementCoinageRecyclersUnloaded, replaced by two entriespaseo-asset-hubis additive only (Scarcity,NftClaims, twoDotnsGatewayconstants), so asset-hub consumers upgrade safely.Testing
chain-clientwas 26/26 green before and 26/26 green after. That is the problem it fixes:the suite compares the descriptor to a constant, and both held the dead hash, so it passed
against a chain that does not exist. It went red twice during the change, once per wrong
constant.
typecheckandcheckclean; workspace green except four pre-existingformatBalancelocale failures inpackages/utils, untouched here.E2E. Green is not currently reachable on this repo (main's last four runs: one green, three
red), so the comparison is against main @
1981a2d, this branch's parent.This PR fixes 7 tests:
contracts boot:16,contracts submit:35,tx dispatch-error:17,tx finalized:16,tx on-status:18,tx submit-remark:20and:49. They failed on mainbecause the descriptor and the test host agreed on the dead hash while the RPC served the live chain, so decoding and tx submission ran against mismatched metadata.
The remaining failures are not from this PR.
contracts query:44and:63fail on maintoo. The rest is a
connection-status: "connecting"timeout that lands on a different testevery run with no repeats: run 31808934300 hit signer connect, chain-client lifecycle and host storage-ops; run 31821921037 hit storage prefix, signer switch-account and tx finalized. Six tests, one signature, which points at the shared chain connection under nine parallel demos.