-
Notifications
You must be signed in to change notification settings - Fork 12
Revamped lynx contract deployments for signing infrastructure
#441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revamped lynx contract deployments for signing infrastructure
#441
Conversation
…dinator and Dispatcher. Moving forward these contracts will be easier to upgrade - the pain point is just this time.
…ter updated deployment
ba384dd to
371cfe0
Compare
lynx contract deployments for signing infrastructurelynx contract deployments for signing infrastructure
Fully redeploy root signing infrastructure since old SigningCoordinatorChild was out of sync.
…torChild was out of sync.
…t was already previously deployed.
…did not update old SigningCoordinatorChild which became out of sync with new SigningCoordinator. Really the entire infra needed to be fully deployed again i.e. everything started from scratch. Since the contracts are now properly proxied, upgrading will be easier moving forward.
lynx contract deployments for signing infrastructurelynx contract deployments for signing infrastructure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR bumps the version from 0.26.0-alpha.1 to 0.26.0-alpha.2, introducing several infrastructure improvements and dependency updates.
- Updates SigningCoordinatorDispatcher contract to use upgradeable proxy pattern with proper initialization
- Enhances verify.py script to support verification of multiple contracts simultaneously
- Adds new script for deploying signing cohorts on additional chains
Reviewed Changes
Copilot reviewed 10 out of 13 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| tests/test_signing_coordinator.py | Updates test fixture to deploy SigningCoordinatorDispatcher as a proxied contract with proper initialization |
| setup.cfg | Version bump to 0.26.0-alpha.2 |
| scripts/verify.py | Refactors to accept multiple contract names and verify them in batch |
| scripts/signing_cohort_additional_chain.py | New script for deploying signing cohorts on additional chains for already formed cohorts |
| requirements.txt | Updates multiple Python dependencies (contains several future version numbers) |
| package.json | Version bump to 0.26.0-alpha.2 |
| package-lock.json | Updates lock file to reflect package.json version change |
| deployment/constructor_params/lynx/root-signing-infra.yml | Adds proxy initialization configuration for SigningCoordinatorDispatcher |
| deployment/constructor_params/lynx/child-signing-infra-base.yml | Updates SigningCoordinatorDispatcher address reference |
| deployment/artifacts/lynx.json | Updates contract addresses and ABIs for redeployed contracts on lynx network |
| contracts/contracts/coordination/SigningCoordinatorDispatcher.sol | Migrates to upgradeable pattern using Initializable and OwnableUpgradeable |
| Pipfile | Updates nucypher-core Git reference from "handover" to "main" branch |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| flake8 = "*" | ||
| isort = "*" | ||
| nucypher-core = { git = "https://github.com/nucypher/nucypher-core.git", ref = "handover", subdirectory = "nucypher-core-python" } | ||
| nucypher-core = { git = "https://github.com/nucypher/nucypher-core.git", ref = "main", subdirectory = "nucypher-core-python" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Type of PR:
Required reviews:
What this does:
Overall we need to redeploy
SigningCoordinatorandSigningCoordinatorDispatcherto be properly proxied. In this case the addresses of the contracts change, so we need to update other things. After this deployment they will be properly proxied, so next time we'll just upgrade the contracts without changing the address and some additional steps will no longer need to be done.lynx- these contracts are now properly proxied so will require only an upgrade the next time (we have to pay the price this time)lynxregistryAdditionally:
Issues fixed/closed:
Why it's needed:
Notes for reviewers: