Description

Adds support for metamask_accountChanged notification via wallet_notify (CAIP-319) notification to enable our wallet-standard implementation to forward account changed events via the wallet standard change event

This is not a pattern we want to continue since the Multichain API should not require account changing. This is a one off bespoke implementation to support a Solana wallet-standard interface.

E2E testing for this feature should be handled in the Wallet Standard powered test dapp one we have it cc @EdouardBougon @baptiste-marchand

Demo video

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/4193

Manual testing steps

0. Build in flask
1. Generate 2 Solana Accounts
2. Go to any site
3. Open the dev console and run the following script:

const extensionPort = chrome.runtime.connect(<your extension id>)

extensionPort.onMessage.addListener((msg) => {
  console.log(msg.data)
})

extensionPort.postMessage({
  type: "caip-x",
  data: {
    jsonrpc: "2.0",
    method: "wallet_createSession",
    params: {
      requiredScopes: {},
      optionalScopes: {
        "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp": {
          methods: ["getAccount"],
          notifications: [],
          accounts: ['solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp:<SOLANA_ACCOUNT_ADDRESS_1>',
          'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp:<SOLANA_ACCOUNT_ADDRESS_2>']
        }
      },
  sessionProperties: {'solana_accountChanged_notifications': true},
};,
  }
})

4. Switch between the two Solana accounts in the account selector in the wallet UI
5. You should see console logs in the dev console:

{
    "method": "wallet_notify",
    "params": {
        "scope": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
        "notification": {
            "method": "solana_accountChanged",
            "params": "<YOUR_SOLANA_WALLET_ADDRESS>"
        }
    }
}

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.