Wallet-as-a-Service (Palisade) supports multiple blockchain networks. This page describes the features available for each supported chain.
EVM compatibility
For EVM-compatible chains (Ethereum, Arbitrum, Avalanche, Base, BNB, Polygon), a single wallet address works across all supported networks. See Manage wallets to learn how to create multi-chain wallets.
The following table shows feature availability for each blockchain.
| Chain | Testnet | Mainnet | MPC (CloudSign) | MPC (Mobile) |
|---|---|---|---|---|
| Arbitrum | ✓ | ✓ | ✓ | ✓ |
| Avalanche | ✓ | ✓ | ✓ | ✓ |
| Base | ✓ | ✓ | ✓ | ✓ |
| Bitcoin | ✓ | ✓ | ✓ | Coming soon |
| BNB Smart Chain | ✓ | ✓ | ✓ | ✓ |
| Ethereum | ✓ | ✓ | ✓ | ✓ |
| 1Money | ✓ | — | ✓ | ✓ |
| Polygon | ✓ | ✓ | ✓ | ✓ |
| Solana | ✓ | ✓ | ✓ | ✓ |
| Tron | ✓ | ✓ | ✓ | ✓ |
| XRP Ledger | ✓ | ✓ | ✓ | ✓ |
The following table shows transaction and signing features for each blockchain.
| Chain | Native tokens | Issued tokens | Raw signing | WalletConnect | Plaintext signing | Advanced transactions |
|---|---|---|---|---|---|---|
| Arbitrum | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Avalanche | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Base | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Bitcoin | ✓ | — | — | — | — | — |
| BNB Smart Chain | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Ethereum | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| 1Money | — | ✓ | ✓ | — | ✓ | ✓ |
| Polygon | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Solana | ✓ | ✓ | ✓ | — | ✓ | — |
| Tron | ✓ | ✓ | ✓ | — | ✓ | — |
| XRP Ledger | ✓ | ✓ | ✓ | — | ✓ | ✓ |
The following table shows operational features for each blockchain.
| Chain | Sweeping | Fee estimation | Multi-chain |
|---|---|---|---|
| Arbitrum | ✓ | ✓ | ✓ |
| Avalanche | ✓ | ✓ | ✓ |
| Base | ✓ | ✓ | ✓ |
| Bitcoin | — | — | — |
| BNB Smart Chain | ✓ | ✓ | ✓ |
| Ethereum | ✓ | ✓ | ✓ |
| 1Money | ✓ | ✓ | ✓ |
| Polygon | ✓ | ✓ | ✓ |
| Solana | ✓ | ✓ | — |
| Tron | ✓ | ✓ | — |
| XRP Ledger | ✓ | ✓ | — |
This section defines each feature shown in the tables above.
| Feature | Description |
|---|---|
| Testnet | The chain is available in the sandbox environment for development and testing. |
| Mainnet | The chain is available in the production environment for live transactions. |
| Feature | Description |
|---|---|
| MPC (CloudSign) | Keys are split across CloudSign devices using Multi-Party Computation. See Set up and run CloudSign. |
| MPC (Mobile) | Keys are split across mobile devices using Multi-Party Computation. See Adding a device. |
| Feature | Description |
|---|---|
| Native tokens | The blockchain's native asset is supported (for example, ETH on Ethereum or SOL on Solana). |
| Issued tokens | Tokens issued on the blockchain are supported (for example, ERC-20 tokens like USDC on Ethereum). |
| Feature | Description |
|---|---|
| Raw signing | You can sign custom transaction payloads that you construct. This enables deploying smart contracts, interacting with smart contracts, and performing complex transactions not directly supported by the platform. See Raw signing. |
| WalletConnect | You can connect wallets to decentralized applications (dApps) using the WalletConnect protocol. This enables swaps, liquidity provision, and other dApp interactions. See Connections. |
| Plaintext signing | You can sign arbitrary plaintext data for dApp authentication, proof of funds, or proof of key ownership. |
| Advanced transactions | Blockchain-specific transaction types are available as API endpoints (for example, TrustSet on XRP Ledger). This allows you to execute complex blockchain operations through the Palisade API without building raw transactions. |
| Feature | Description |
|---|---|
| Sweeping | Automated consolidation of funds from multiple wallets into a destination wallet. See Asset sweeping. |
| Fee estimation | Transaction fees can be estimated before submission. |
| Multi-chain | A single wallet address works across multiple EVM-compatible chains. |