feat: publish the pallet-revive genesis with each release - #253
Open
mordamax wants to merge 6 commits into
Open
Conversation
Contributor
CI Summary
4naly3er AnalysisMedium (5)
Low (10)
Gas (14)
Informational (11)
Slither AnalysisHigh (3)
Medium (43)
Low (73)
Informational (64)
Deploy ContractsDeployed addresses vs the committed manifestExpected is the committed manifest; actual is this CI deployment of the same pipeline.
Labelsdependencies, other, type: docs |
mordamax
force-pushed
the
feat/pallet-revive-genesis-artifact
branch
2 times, most recently
from
August 26, 2026 22:49
aa33d85 to
b9ff6cb
Compare
Member
|
@mordamax please check PR template please |
mordamax
force-pushed
the
feat/pallet-revive-genesis-artifact
branch
3 times, most recently
from
August 27, 2026 11:08
aae3786 to
e722db8
Compare
mordamax
marked this pull request as ready for review
August 27, 2026 11:20
re-gius
reviewed
Aug 27, 2026
mordamax
force-pushed
the
feat/pallet-revive-genesis-artifact
branch
from
August 27, 2026 15:53
e722db8 to
6617fdb
Compare
mordamax
force-pushed
the
feat/pallet-revive-genesis-artifact
branch
from
August 27, 2026 19:48
6617fdb to
9ebffb8
Compare
Author
|
all done also dropped one line in |
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
Extends the release artifact with pallet-revive genesis state, so a chain can carry DotNS from block zero instead of deploying it afterwards.
build-genesis.shruns the existing deploy stages against anvil, dumps the EVM state and converts it to aGenesisConfigaccount list.paritytech/preview-net-v1does this today by cloning this repo at a movingmasterwith its own copy ofFACTORY_DEPLOYER_KEY. Building it here ties the artifact to the same commit and keys as the ABIs beside it, and lets that repo drop ~790 lines and two secrets.Follows the pattern #242 set — standalone asset, in the strict pre-publish check, plus a small path-filtered PR workflow (
genesis-extractor-test.yml) that tests the extractor, mirroringrelease-metadata.yml. Addresses are deliberately not re-emitted;deployments.jsonstays the only copy.The filename carries the TLD (
dotns-genesis-test.json) becauseDOTNS_TLDis baked into the registry initialiser, so it suits test networks only — the release body says so. Address parity againstdeployments/paseo-assethub/420420417.jsonis asserted, so a wrong factory key fails the build.Type
Scope
Related Issues
Follows #242, which made the release carry addresses. This adds genesis state to the same artifact.
Fixes
Checklist
Code
forge buildpassesforge testpassesTesting
Security
selfdestructordelegatecallDocumentation
Breaking Changes
How to test
Ran locally: five deploy stages, 33 genesis accounts, 19 names matching the live manifest, 9 extractor tests.
Notes
No Solidity changed, so the contract checkboxes are inherited state rather than something this diff exercises.
deployall.sh, which also has a factory-exists check and theEXPECTED_CREATE3_FACTORYguard. Drivingdeploy:allwould be DRY-er but needs the keystore flow and thepaseo_localalias, which I could not test locally. The constraint if you collapse it is in the script: the signer must stay the admin key, notdeploy-contracts.yml's public anvil account..github/PULL_REQUEST_TEMPLATE.mdhas a trailing space in its filename, so GitHub never loads it and new PRs open blank. Happy to fix separately.