-
Notifications
You must be signed in to change notification settings - Fork 86
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
Gas Upgrades and Beta Fixes #1055
Conversation
Provide From conversion impls to construct PrivateKey and Signature from byte arrays. The conversions into PrivateKey are fallible, while a Signature is allowed to be constructed from any 64 bytes.
Add TestSigner providing an in-process Signing implementation for tests.
TryFromBytes is not needed, neither is the public key as a member of HashiCorpVault state.
…yz/movement into musitdev/alloy-integration
…github.com/movementlabsxyz/movement into l-monninger/secure-signing-e2e-integration
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.
Thanks for doing it. I've planned to work on it this weekend, so I was able to work on other things.
I've done the bring-up elsa-to-biarritz-rc1 upgrade
locally using local keys and it works.
I have this message during the migration:
2025-02-16T09:44:03.888562Z INFO maptos_framework_release_util: release proposal transaction failed, but we will still attempt to vote through: Proposing("submitting transaction failed with: Unknown(Transaction committed on chain, but failed execution: MiscellaneousError(Some(CONSTRAINT_NOT_SATISFIED)))")
2025-02-16T09:44:07.679691Z INFO maptos_framework_release_util: release proposal transaction failed, but we will still attempt to vote through: Proposing("submitting transaction failed with: Unknown(Transaction committed on chain, but failed execution: MiscellaneousError(Some(CONSTRAINT_NOT_SATISFIED)))")
I have 2 questions:
- This migration process is only for existing node that was started before the update. If I start a node from this rev commit, do I have to do it?
- now in the
bring-up elsa-to-biarritz-rc1 upgrade
you've to pass the key string<MAPTOS_SIGNER> <DA_SIGNER> <MCR_SIGNER>
. Can we change the keys from the current config because for the existing nodes we've to migrate from local keys to vault keys or there's something else to do before.
There's some issue to build everything. The |
…com/movementlabsxyz/movement into l-monninger/gas-upgrades-beta-fixes
…on incompatibilities
The build works now. There's still an issue with Helios container push. |
Co-authored-by: Andy Golay <andygolay@gmail.com> Co-authored-by: musitdev <philippe.delrieu@free.fr> Co-authored-by: Mikhail Zabaluev <mikhail.zabaluev@movementlabs.xyz> Co-authored-by: Richard Melkonian <35300528+0xmovses@users.noreply.github.com> Co-authored-by: Icarus131 <anirudhprasad131@protonmail.com> Co-authored-by: primata <primata@movementlabs.xyz> Co-authored-by: Icarus131 <anirudhprasad131@gmail.com> Co-authored-by: Richard Melkonian <r.v.melkonian@gmail.com> Co-authored-by: Radu Popa <radupopa21be@gmail.com>
Summary
protocol-units
Changelog
Testing
Test 1: , Start a leader and its follower:
The test execution should have no errors.
Test 2: Do the migration.
In another terminal, do the migration describe in this doc
In the movement repo root, execute this command to do the full upgrade in one command and random keys:
Outstanding issues
I have this message during the migration:
I'm not sure it's important or not.