Supported Networks - mpcvault

Networks

Network	Network Type	Features
Ethereum & EVM	`NETWORK_TYPE_EVM`	Native tokens, ERC-20, ERC-721, custom contract calls and deployment, message and typed-data signing
Bitcoin	`NETWORK_TYPE_BITCOIN`	Native BTC
Solana	`NETWORK_TYPE_SOLANA`	Native SOL, SPL tokens, custom program transactions, message signing
Sonic SVM	`NETWORK_TYPE_SOLANA`	Native SOL, SPL tokens, custom program transactions
Aptos	`NETWORK_TYPE_APTOS`	Native APT, Coins, custom Move entry-function calls, message signing
Movement	`NETWORK_TYPE_APTOS`	Native MOVE, Coins, custom Move entry-function calls
Sui	`NETWORK_TYPE_SUI`	Native SUI, Coins, custom Move calls and programmable transaction blocks, message signing
TRON	`NETWORK_TYPE_TRON`	TRX, TRC-10, TRC-20
TON	`NETWORK_TYPE_TON`	Native GRAM (prev. TON), Jettons, custom contract messages, message signing
Stellar	`NETWORK_TYPE_STELLAR`	Native XLM, issued assets, trustlines, custom Classic transactions and Soroban contract interactions

Aptos and Movement share NETWORK_TYPE_APTOS and use the same Aptos transaction payloads. Set chainId to "1" for Aptos mainnet or "126" for Movement mainnet.
Solana and Sonic SVM share NETWORK_TYPE_SOLANA. Select the network using the transaction payload field: solanaSend* for Solana or sonicSvmSend* for Sonic SVM (for example, sonicSvmSendCustom). These payloads ignore chainId.

EVM Chain IDs

All EVM-compatible networks use NETWORK_TYPE_EVM. The table below lists the mainnet chain IDs for built-in EVM networks. Use these IDs in EVM transaction payloads.

Chain ID	Network
`1`	Ethereum
`137`	Polygon
`56`	BNB Smart Chain
`42161`	Arbitrum One
`10`	Optimism
`8453`	Base
`43114`	Avalanche C-Chain
`999`	HyperEVM
`9745`	Plasma
`1514`	DATA Network (prev. Story)
`1983`	Krown Network
`4663`	Robinhood Chain

Custom EVM networks can be added via the MPCVault Dashboard. See Add a Custom EVM Network for instructions.

Custom Transactions

If your application needs to deploy EVM contracts, approve token spending, or interact with DeFi and NFT protocols, you can use custom transactions. Choose the payload field for your network below. Supported operations vary by network and protocol.

Network	Payload field	What you can do
Ethereum & EVM	`evmSendCustom`	Call contracts with encoded function data in `input`, optionally sending native tokens with the call. To deploy a contract, leave `to` empty and set `input` to the deployment bytecode.
Solana / Sonic SVM	`solanaSendCustom` / `sonicSvmSendCustom`	Call on-chain programs and combine multiple instructions in a transaction. Supports legacy and v0 transactions, with up to 5 transactions per request.
Aptos / Movement	`aptosSendCustom`	Call Move entry functions with a function name, type arguments, and arguments. Accepts JSON or a BCS-encoded `TransactionPayload`; `chainId` selects Aptos or Movement.
Sui	`suiSendCustom`	Call Move functions and combine actions in a programmable transaction block (PTB), such as splitting a coin and using it in a swap within the same transaction.
TON	`tonSendCustom`	Send one or more messages to contracts, each with a recipient, amount, and message body. Optional initialization data supports contract deployment.
Stellar	`stellarSendCustom`	Supports Classic transactions, which can combine multiple operations, and Soroban smart contract transactions. Uses XDR `TransactionEnvelope` format.

Custom transactions follow the vault’s approval policy. See CreateSigningRequest for payload fields, encoding requirements, and examples.