chore: record the live testnet manifests - #315
Merged
Merged
Conversation
Contributor
CI Summary
Deploy ContractsDeployed addresses vs the expected setExpected is the committed expected-address set; actual is this CI deployment of the same pipeline.
Labelsother, type: docs |
GHkrishna
approved these changes
Sep 22, 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
Records what the two live testnets actually run.
paseo-assethubis updated to the post-v0.8.0 in-place-upgrade state: the store factory lives behind a proxy at0x99605a92…71f6, its beacons moved with it, and the outgoing factory and beacons stay recorded under*Legacykeys because the migrated stores remain on them (see chore: review-only diff of the Paseo v0.8.0 upgrade (do not merge) #312).previewnetgets its first committed manifest, read from its chain. It runs an unmodified v0.8.0 genesis, so every address equalsdeployments/expected.json. A README explains the chain id shared withpaseo-assethuband the*Legacyconvention.release-metadata.mjs verifylearns two general rules: a*Legacymanifest entry is a superseded deployment that holds no registry key by design, and a key tolerated unset is also tolerated undeclared where an older genesis set it.Type
Scope
Related Issues
Fixes
Checklist
Code
forge buildpassesforge testpassesTesting
Security
selfdestructordelegatecallDocumentation
Breaking Changes
Breaking changes:
How to test
Both verifies end with "matches the chain".
Notes
Manifests are records of live networks; the Paseo one diverges from expected.json where its history does (Legacy entries, a lens deployed before the current set), and the previewnet one matches it exactly