Skip to content
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

Merged
merged 137 commits into from
Feb 19, 2025
Merged

Conversation

l-monninger
Copy link
Collaborator

@l-monninger l-monninger commented Feb 15, 2025

Summary

  • RFCs: $\emptyset$.
  • Categories: protocol-units

Changelog

Testing

Test 1: , Start a leader and its follower:

CELESTIA_LOG_LEVEL=FATAL nix develop --extra-experimental-features nix-command --extra-experimental-features flakes --command bash  -c "just movement-full-node native build.setup.eth-local.celestia-local.test-followers --keep-tui"

The test execution should have no errors.

Test 2: Do the migration.

  1. Build the full node:
cargo build -p movement-full-node
  1. Start a full node with process compose:
CELESTIA_LOG_LEVEL=FATAL nix develop --extra-experimental-features nix-command --extra-experimental-features flakes --command bash  -c "just movement-full-node native build.setup.eth-local.celestia-local --keep-tui"
  1. Test 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:

target/debug/movement-full-node admin bring-up elsa-to-biarritz-rc1 upgrade local::0000000000000000000000000000000000000000000000000000000000000001 local::b2b66215f89a6c41493da9e40d14d4e615d8e6e546e4bad04d61419550c858bf local::ac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80

Outstanding issues

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'm not sure it's important or not.

l-monninger and others added 30 commits December 17, 2024 10:38
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.
@l-monninger l-monninger changed the base branch from main to l-monninger/secure-signing-e2e-integration February 15, 2025 03:58
Copy link
Contributor

@musitdev musitdev left a 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.

@musitdev musitdev added the cicd:bridge-containers Builds bridge containers. label Feb 16, 2025
@musitdev
Copy link
Contributor

There's some issue to build everything. The BigDecimal issue from Aptos code is present. I work on it.

@musitdev
Copy link
Contributor

The build works now. There's still an issue with Helios container push.

@musitdev musitdev changed the base branch from l-monninger/secure-signing-e2e-integration to main February 18, 2025 08:43
@musitdev musitdev changed the base branch from main to l-monninger/secure-signing-e2e-integration February 18, 2025 08:46
@musitdev musitdev changed the base branch from l-monninger/secure-signing-e2e-integration to main February 18, 2025 16:55
@radupopa369 radupopa369 merged commit 4694590 into main Feb 19, 2025
38 of 95 checks passed
mcmillennick pushed a commit that referenced this pull request Mar 9, 2025
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cicd:bridge-containers Builds bridge containers.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants