Skip to content

Conversation

@jophish
Copy link
Contributor

@jophish jophish commented Oct 16, 2025

Description

If an account is able to be upgraded to a smart account, a bottom sheet is shown prompting the user to upgrade before sending the transaction. If the request did not mark atomicity as required, the user can continue with the transaction without upgrading (potentially executing send calls individually/sequentially). If atomicRequired is true on the TX, the user must upgrade their account in order to continue with the transaction.

Test plan

See video. First example is when upgrading is optional, second is required.

smart-account-upgrade-2025-10-16_16.23.50.mp4

Related issues

Backwards compatibility

Network scalability

If a new NetworkId and/or Network are added in the future, the changes in this PR will:

  • Continue to work without code changes, OR trigger a compilation error (guaranteeing we find it when a new network is added)

Copy link
Contributor

@bakoushin bakoushin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@jophish jophish added this pull request to the merge queue Oct 17, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 17, 2025
@jophish jophish added this pull request to the merge queue Nov 7, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants