You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: re-introduce resolveAccountAddress on v2 KeyringSnapRpc (#585)
<!-- CURSOR_SUMMARY -->
> [!NOTE]
> **Medium Risk**
> Touches signing-request routing contracts across API, client, and Snap
handler; incorrect behavior could mis-route dapp signing, though changes
are additive and optional for Snaps.
>
> **Overview**
> Restores **`keyring_resolveAccountAddress`** on the v2 snap keyring
stack so MetaMask can ask a Snap which account address should handle a
signing request for a given CAIP-2 scope and JSON-RPC call.
>
> **keyring-api (v2)** adds the RPC method constant, request/response
structs (nullable `ResolvedAccountAddress`), the optional
`resolveAccountAddress` on `KeyringSnapRpc`, and a
**`snap.resolveAccountAddress`** capability flag.
>
> **keyring-snap-client** and **keyring-snap-sdk** wire the method
through: the client sends validated RPC calls; the SDK handler
dispatches to `keyring.resolveAccountAddress` or throws if unsupported.
Tests cover success, `null` responses, and missing implementation.
>
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
5951828. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
0 commit comments