feat: prepare chain upgrade

[beer-1]

Description

This PR introduces the v1.1.4 chain upgrade, which includes:

• Account Abstraction (AA): Enables native support for account abstraction.
• Move Precompile Upgrade: Updates Move precompiles to support the latest compiler version.

Checklist

• Confirm whether there is incompatible precompiles or not before merging this with query interface

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title, you can find examples of the prefixes below:
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes update the application to use a new upgrade handler for version v1.1.4. The handler reads and bundles Move VM precompiled modules and publishes them with a compatible upgrade policy. The app initialization logic is updated to register this new handler, replacing the previous v1.1.1 handler.

Changes

Cohort / File(s)	Change Summary
App Upgrade Handler Reference Update app/app.go	Changed import and registration of upgrade handlers from v1_1_1 to v1_1_4 during app initialization.
New v1.1.4 Upgrade Handler app/upgrades/v1_1_4/upgrade.go	Introduced RegisterUpgradeHandlers for v1.1.4, reading and publishing Move VM precompiled modules with a compatible policy.

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant v1_1_4 Upgrade Handler
    participant Move VM Precompiled Module Reader
    participant Move Module Keeper

    App->>v1_1_4 Upgrade Handler: RegisterUpgradeHandlers(app)
    v1_1_4 Upgrade Handler->>Move VM Precompiled Module Reader: ReadStdlib()
    Move VM Precompiled Module Reader-->>v1_1_4 Upgrade Handler: Return modules
    v1_1_4 Upgrade Handler->>Move Module Keeper: Publish bundle (COMPATIBLE policy)
    Move Module Keeper-->>v1_1_4 Upgrade Handler: Success/Error
    v1_1_4 Upgrade Handler-->>App: Handler registered

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

A new upgrade hops in, v1.1.4,
Bundling modules, ready to explore.
Old handler replaced, the app feels bright,
Move VM modules bundled tight.
With compatible cheer, the upgrade's complete—
A rabbit's work is swift and neat! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c9d395e and 4deb1c6.

📒 Files selected for processing (2)

• app/app.go (2 hunks)
• app/upgrades/v1_1_4/upgrade.go (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Run test and upload codecov
• GitHub Check: golangci-lint
• GitHub Check: Analyze (go)

🔇 Additional comments (5)

app/app.go (2)

59-59: LGTM! Import statement correctly updated for v1.1.4 upgrade.

The import statement has been properly updated from v1_1_1 to v1_1_4 to align with the new upgrade handler version.

---

252-252: LGTM! Upgrade handler registration correctly updated.

The function call has been properly updated to use the v1.1.4 upgrade handlers, maintaining consistency with the import change. The conditional check ensures handlers are only registered when loading the latest version.

app/upgrades/v1_1_4/upgrade.go (3)

1-16: LGTM! Package structure and imports are well-organized.

The package declaration, imports, and dependencies are properly structured for the v1.1.4 upgrade handler. All necessary modules are imported for the upgrade functionality.

---

17-17: LGTM! Version constant correctly defined.

The upgrade name constant matches the expected v1.1.4 version string.

---

20-42: Upgrade handler v1.1.4 approved – no changes needed

The new upgrade handler in app/upgrades/v1_1_4/upgrade.go

• mirrors the v1.1.1 logic,
• loads the same stdlib modules via vmprecom.ReadStdlib(),
• uses the existing COMPATIBLE policy (as covered by tests and previous upgrade),
• and publishes to StdAddress in line with all other modules.

All compatibility and address‐conflict concerns have been exercised in v1.1.1 and in extensive module tests. No further action is required.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/prepare-upgrade

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None