Docs: update multichain peer-dep and Solana APIs

Remove guidance to explicitly install @metamask/connect-multichain for single-ecosystem packages and simplify install commands across EVM and Solana quickstarts. Rename Solana methods and Wallet Standard features (solana_signMessage → signMessage, solana_signAndSendTransaction/signAndSendAllTransactions → signAndSendTransaction) and update batch guidance to use the variadic signAndSendTransaction call. Revise error handling docs to use the new multichain error classes (RPCInvokeMethodErr, RPCHttpErr, RPCReadonlyResponseErr, RPCReadonlyRequestErr) and expose wallet RPC codes on err.rpcCode; remove the internal transport 1013 note from provider docs. Misc: update Wagmi quickstart to require @metamask/connect-evm@^2.1.0 and adjust examples/usages across multichain, evm, solana, reference, and troubleshooting pages to match the new APIs and patterns.

Author: shahbaz17

metamask-connect/evm/guides/migrate-from-sdk.md

@@ -44,8 +44,8 @@ npm uninstall @metamask/sdk
 # For React Native, remove
 npm uninstall @metamask/sdk-react
 
-# Install new (EVM). @metamask/connect-multichain is a required peer dependency since @metamask/connect-evm 2.0.0.
-npm install @metamask/connect-evm @metamask/connect-multichain
+# Install new (EVM only)
+npm install @metamask/connect-evm
 ```
 
 ### 2. Update imports
@@ -346,10 +346,6 @@ If your dapp supports (or plans to support) both EVM and Solana, consider upgrad
 The EVM client is built on top of `createMultichainClient` internally, so the upgrade is
 straightforward:
 
-```bash npm2yarn
-npm install @metamask/connect-multichain
-```
-
 ```typescript
 import { createMultichainClient } from '@metamask/connect-multichain'
 

metamask-connect/evm/index.mdx

@@ -99,7 +99,7 @@ We recommend using an Infura API key for production dapps. MetaMask Connect EVM
 
 To migrate:
 
-- Replace `@metamask/sdk` with `@metamask/connect-evm` in your dependencies, and add `@metamask/connect-multichain` (a required peer dependency since `@metamask/connect-evm` 2.0.0).
+- Replace `@metamask/sdk` with `@metamask/connect-evm` in your dependencies.
 - Update imports from `MetaMaskSDK` to `createEVMClient`.
 - Switch from synchronous to async initialization.
 - Update your provider access pattern.

metamask-connect/evm/quickstart/javascript.md

@@ -125,13 +125,9 @@ You've successfully set up MetaMask Connect EVM.
 Install the EVM client in an existing JavaScript project:
 
 ```bash npm2yarn
-npm install @metamask/connect-evm @metamask/connect-multichain
+npm install @metamask/connect-evm
 ```
 
-:::note
-Since `@metamask/connect-evm` 2.0.0, `@metamask/connect-multichain` is a required peer dependency that you must install explicitly.
-:::
-
 ### 2. Initialize MetaMask Connect EVM
 
 Initialize the EVM client using [`createEVMClient`](../reference/methods.md#createevmclient).

metamask-connect/evm/quickstart/nodejs.md

@@ -42,13 +42,9 @@ polyfilling in browser or React Native environments.
 Install the EVM client in an existing Node.js project:
 
 ```bash npm2yarn
-npm install @metamask/connect-evm @metamask/connect-multichain
+npm install @metamask/connect-evm
 ```
 
-:::note
-Since `@metamask/connect-evm` 2.0.0, `@metamask/connect-multichain` is a required peer dependency that you must install explicitly.
-:::
-
 ### 2. Initialize MetaMask Connect EVM
 
 Create a file (`index.mjs`) and initialize the client using [`createEVMClient`](../reference/methods.md#createevmclient).

metamask-connect/evm/quickstart/react-native.md

@@ -55,13 +55,9 @@ npx create-expo-app MyProject --template
 Install MetaMask Connect EVM and its required polyfill packages:
 
 ```bash
-npm install @metamask/connect-evm @metamask/connect-multichain react-native-get-random-values buffer @react-native-async-storage/async-storage readable-stream
+npm install @metamask/connect-evm react-native-get-random-values buffer @react-native-async-storage/async-storage readable-stream
 ```
 
-:::note
-Since `@metamask/connect-evm` 2.0.0, `@metamask/connect-multichain` is a required peer dependency that you must install explicitly.
-:::
-
 ### 3. Create polyfills
 
 Create `polyfills.ts` (at the project root or in `src/`) with all required global shims.

metamask-connect/evm/quickstart/wagmi.md

@@ -97,11 +97,11 @@ TOD0: Update with new screenshot and link
 Install MetaMask Connect EVM along with its peer dependencies to an existing React project:
 
 :::note Version requirements
-This quickstart requires `wagmi@^3.6.0`. The `metaMask` connector is imported from the `wagmi/connectors` subpath (part of the `wagmi` package), and requires `@metamask/connect-evm`, which in turn requires `@metamask/connect-multichain` as a peer dependency.
+This quickstart requires `wagmi@^3.6.0`. The `metaMask` connector is imported from the `wagmi/connectors` subpath (part of the `wagmi` package) and requires `@metamask/connect-evm@^2.1.0`.
 :::
 
 ```bash npm2yarn
-npm install @metamask/connect-evm @metamask/connect-multichain wagmi@^3.6.0 viem@2.x @tanstack/react-query
+npm install @metamask/connect-evm@^2.1.0 wagmi@^3.6.0 viem@2.x @tanstack/react-query
 ```
 
 ### 2. Import required dependencies
@@ -320,7 +320,7 @@ If you previously used `@metamask/sdk` with Wagmi, the MetaMask connector now us
 
    ```bash npm2yarn
    npm uninstall @metamask/sdk
-   npm install @metamask/connect-evm @metamask/connect-multichain wagmi@^3.6.0
+   npm install @metamask/connect-evm@^2.1.0 wagmi@^3.6.0
    ```
 
 2. Update hook usage for wagmi v3:

metamask-connect/evm/reference/provider-api.md

@@ -338,7 +338,6 @@ Common codes and their meaning include:
 - `4902` - The chain isn't recognized by the wallet. Add it with `wallet_addEthereumChain`, or pass `chainConfiguration` to [`switchChain`](methods.md#switchchain).
 - `-32602` - The parameters are invalid.
 - `-32603` - Internal error.
-- `1013` - An internal transport disconnect. The SDK retries automatically, so don't treat it as a user-facing disconnect.
 
 For the complete list of errors, see [EIP-1193](https://eips.ethereum.org/EIPS/eip-1193#provider-errors)
 and [EIP-1474](https://eips.ethereum.org/EIPS/eip-1474#error-codes).
@@ -349,8 +348,11 @@ returned by the MetaMask provider, and can help you identify their meaning.
 :::
 
 :::note Typed errors
-The multichain core exports typed error classes for `instanceof` checks: `ProtocolError`,
-`StorageError`, and `RpcError` from `@metamask/connect-multichain`.
+When you use the multichain client, the core (`@metamask/connect-multichain`) exports typed error
+classes for `instanceof` checks: `RPCInvokeMethodErr` (wraps wallet `invokeMethod` errors—read the
+wallet's original code from `err.rpcCode`), `RPCHttpErr`, `RPCReadonlyResponseErr`, and
+`RPCReadonlyRequestErr`. The EVM provider itself rejects with a standard EIP-1193 `ProviderRpcError`
+(use `err.code`).
 :::
 
 ## Next steps

metamask-connect/index.md

@@ -96,7 +96,6 @@ See [supported platforms](supported-platforms.md) for the full matrix.
 ### Which blockchain networks does MetaMask Connect support?
 
 MetaMask Connect supports Ethereum and all EVM-compatible networks (Polygon, Arbitrum, Optimism, Linea, Base, etc.) through `@metamask/connect-evm`, Solana through `@metamask/connect-solana`, and both simultaneously through `@metamask/connect-multichain`.
-Since their 2.0.0 releases, `@metamask/connect-evm` and `@metamask/connect-solana` require `@metamask/connect-multichain` as an explicitly installed peer dependency.
 See [integration options](integration-options.md) to choose the right package.
 
 ### Do I need an Infura API key to use MetaMask Connect?

metamask-connect/integration-options.md

@@ -58,12 +58,6 @@ If your dapp supports both EVM and Solana, use [`@metamask/connect-evm`](evm/ind
 [`@metamask/connect-solana`](solana/index.mdx) together to
 support both ecosystems while keeping familiar provider interfaces for each.
 
-:::note
-The `@metamask/connect-evm` and `@metamask/connect-solana` packages require
-`@metamask/connect-multichain` as an explicitly installed peer dependency since their 2.0.0 releases.
-Install it alongside whichever single-ecosystem package you use.
-:::
-
 ## Compare options
 
 |                    | Multichain                                   | Single-ecosystem                                                       | Multi-ecosystem                         |

metamask-connect/multichain/guides/send-transactions.md

@@ -133,7 +133,7 @@ console.log('Estimated gas:', gasEstimate)
 
 ## Build and send a Solana transaction
 
-Build a transaction with `@solana/web3.js`, serialize it to base64, then send it with `solana_signAndSendTransaction`.
+Build a transaction with `@solana/web3.js`, serialize it to base64, then send it with `signAndSendTransaction`.
 This signs and broadcasts the transaction in one step:
 
 ```javascript
@@ -163,8 +163,9 @@ const base64Transaction = Buffer.from(serialized).toString('base64')
 const result = await client.invokeMethod({
   scope: 'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp',
   request: {
-    method: 'solana_signAndSendTransaction',
+    method: 'signAndSendTransaction',
     params: {
+      account: { address: fromPubkey.toBase58() },
       transaction: base64Transaction,
     },
   },
@@ -174,15 +175,16 @@ console.log('SOL tx signature:', result.signature)
 
 ## Sign a Solana transaction without sending
 
-Use `solana_signTransaction` to get the signed transaction back without broadcasting it.
+Use `signTransaction` to get the signed transaction back without broadcasting it.
 This is useful when you need to inspect or modify the signed output before submitting:
 
 ```javascript
 const signResult = await client.invokeMethod({
   scope: 'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp',
   request: {
-    method: 'solana_signTransaction',
+    method: 'signTransaction',
     params: {
+      account: { address: fromPubkey.toBase58() },
       transaction: base64Transaction,
     },
   },
@@ -196,11 +198,10 @@ console.log('Transaction ID:', txId)
 
 ## Error handling
 
-| Error code | Description                   | Action                                                                     |
-| ---------- | ----------------------------- | -------------------------------------------------------------------------- |
-| `4001`     | User rejected the request     | Show a retry option. Do not treat as an application error.                 |
-| `-32002`   | Request already pending       | Wait for the user to respond in MetaMask before retrying.                  |
-| `1013`     | Internal transport disconnect | The SDK retries automatically. Don't treat it as a user-facing disconnect. |
+| Error code | Description               | Action                                                     |
+| ---------- | ------------------------- | ---------------------------------------------------------- |
+| `4001`     | User rejected the request | Show a retry option. Do not treat as an application error. |
+| `-32002`   | Request already pending   | Wait for the user to respond in MetaMask before retrying.  |
 
 <br/>