feat!: expose snap-only keyring methods through service + use explicit keyring.v1 for v1 account management Snaps#9390
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
ccharly
force-pushed
the
cc/feat/snap-account-service-snap-rpc-methods
branch
from
9cd4cab to
0221bce
Compare
Contributor
Author
|
@metamaskbot publish-preview |
Contributor
|
Preview builds have been published. Learn how to use preview builds in other projects. Expand for full list of packages and versions. |
ccharly
changed the title
keyring.v1 for v1 account management Snaps
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
…rations in withKeyringV2
ccharly
force-pushed
the
cc/feat/snap-account-service-snap-rpc-methods
branch
from
8c7abb2 to
803c8d6
Compare
Contributor
Author
|
@metamaskbot publish-preview |
Contributor
|
Preview builds have been published. Learn how to use preview builds in other projects. Expand for full list of packages and versions. |
hmalik88
reviewed
Jul 7, 2026
hmalik88
reviewed
Jul 7, 2026
Co-authored-by: Hassan Malik <41640681+hmalik88@users.noreply.github.com>
Co-authored-by: Hassan Malik <41640681+hmalik88@users.noreply.github.com>
hmalik88
previously approved these changes
Jul 7, 2026
hmalik88
approved these changes
Jul 8, 2026
FrederikBolding
approved these changes
Jul 8, 2026
pull Bot
pushed a commit
to dmrazzy/core
that referenced
this pull request
Jul 9, 2026
## Explanation <!-- Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes: * What is the current state of things and why does it need to change? * What is the solution your changes offer and how does it work? * Are there any changes whose purpose might not obvious to those unfamiliar with the domain? * If your primary goal was to update one package but you found you had to update another one along the way, why did you do so? * If you had to upgrade a dependency, why did you do so? --> ## [Asset Controller 10.2.0] ### Added - Add Robinhood Chain (`4663`/`0x1237`) in `MulticallClient` ([MetaMask#9443](MetaMask#9443)) ### Changed - `MulticallClient` memoizes `balanceOf` and `getEthBalance` call encodings per account address when building multicall batches, reducing redundant ABI encoding for wallets with many tokens ([MetaMask#9425](MetaMask#9425)) - Bump `@metamask/transaction-controller` from `^68.2.2` to `^68.3.0` ([MetaMask#9421](MetaMask#9421)) - Bump `@metamask/keyring-api` from `^23.3.0` to `^23.5.0` ([MetaMask#9390](MetaMask#9390)) - Bump `@metamask/keyring-snap-client` from `^9.0.2` to `^9.2.0` ([MetaMask#9390](MetaMask#9390)) - Bump `@metamask/account-tree-controller` from `^7.5.3` to `^7.5.4` ([MetaMask#9429](MetaMask#9429)) - Bump `@metamask/assets-controllers` from `^109.3.0` to `^109.3.1` ([MetaMask#9429](MetaMask#9429)) - Bump `@metamask/assets-controllers` from `^109.3.0` to `^109.4.0` ([MetaMask#9429](MetaMask#9429), [MetaMask#9450](MetaMask#9450)) ## [Assets-Controllers 109.4.0] ### Added - Add Robinhood Chain (`4663`/`0x1237`) entries in `multicall.ts` and `codefi-v2.ts` ([MetaMask#9443](MetaMask#9443)) ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Checklist - [ ] I've updated the test suite for new or updated code as appropriate - [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [ ] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Version and changelog/lockfile coordination only; functional changes are additive chain support and multicall encoding optimizations described in prior PRs. > > **Overview** > Cuts **monorepo release `1109.0.0`** by bumping published package versions and aligning dependent packages and `yarn.lock`. > > **`@metamask/assets-controller` `10.2.0`** documents Robinhood Chain (`4663`/`0x1237`) support in `MulticallClient`, memoized `balanceOf` / `getEthBalance` encodings in multicall batches, and several dependency bumps (including `@metamask/assets-controllers` to `^109.4.0`). > > **`@metamask/assets-controllers` `109.4.0`** documents Robinhood Chain entries in `multicall.ts` and `codefi-v2.ts`. > > **`bridge-controller`** and **`transaction-pay-controller`** update their `package.json` dependencies to `@metamask/assets-controller` `^10.2.0` and `@metamask/assets-controllers` `^109.4.0`, with matching changelog notes. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit c721375. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explanation
The new
SnapKeyring(v2), is no longer inheritingSnapKeyringV1(to make v1 calls more explicit).This PR now uses this new pattern (
keyring.v1) and also re-expose Snap-only methods that were part of the v1 keyring-API on theSnapAccountServicedirectly. Those methods can also be called using a standardKeyringClient(v1 or v2), but using the service is generally preferred to remove the need of constructing a keyring client to submit the request to the Snap.References
N/A
Checklist
Note
High Risk
Breaking API changes on RestrictedSnapKeyring and new SnapAccountService surface, plus account-creation and signing-routing behavior for v1 vs v2 Snaps across multichain providers.
Overview
Aligns the monorepo with
@metamask/eth-snap-keyringv23, where v1 account APIs live underkeyring.v1instead of top-levelcreateAccount.RestrictedSnapKeyringnow exposes optionalv1; BTC/SOL/TRX/XLM providers guardkeyring.v1and throw for v2-only Snaps on v1 derive-index creation.SnapAccountServiceadds messenger actions that proxyKeyringInternalSnapClientafterensureReady:getAccountAssets,getAccountBalances,getAccountTransactions,resolveAccountAddress, andsetSelectedAccounts. Selected-account forwarding andhandleKeyringSnapMessageusekeyring.v1when present; v2-only Snaps getsetSelectedAccountsand keyring-only messages via the RPC client (or reject v1 messages).Dependency bumps across controllers:
keyring-api^23.5.0,eth-snap-keyring^23.0.0,keyring-snap-client/keyring-snap-sdk^9.2.0, plusyarn.lock.Reviewed by Cursor Bugbot for commit 768ad9a. Bugbot is set up for automated code reviews on this repo. Configure here.