Wallet Selection
Local Signer MCP can expose more than one wallet, and the client should choose the intended one explicitly.
Last updated
Local Signer MCP can expose more than one wallet, and the client should choose the intended one explicitly.
Prefer explicit wallet selection when the client supports it.
Use the most specific identifier available:
walletId when the client already knows the configured local wallet
from when the flow is EVM-based and the sender address is enough to select the wallet
explicit wallet-family hints when the request is chain-specific
For EVM, use walletId first, then from when the sender address is enough to select the wallet.
For Solana, Tron, Algorand, Stacks, Soroban / Stellar, and Sui, use the configured wallet entry for that family.
When more than one wallet exists, use walletId instead of guessing.
For EVM, the signer resolves credentials in this order:
walletId on the transaction, if provided
from on the transaction, if provided
LOCAL_SIGNER_EVM_WALLET_<walletId>_PRIVATE_KEY / LOCAL_SIGNER_EVM_WALLET_<walletId>_RPC_URL
LOCAL_SIGNER_EVM_PRIVATE_KEY_<chainSymbol> / LOCAL_SIGNER_EVM_RPC_URL_<chainSymbol>
LOCAL_SIGNER_EVM_PRIVATE_KEY_<chainId> / LOCAL_SIGNER_EVM_RPC_URL_<chainId>
LOCAL_SIGNER_EVM_PRIVATE_KEY / LOCAL_SIGNER_EVM_RPC_URL
Never infer a wallet selection that would point to an unexpected account when the request can be resolved explicitly.
Last updated