# Blockchains and tokens

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](/products/wallet/user-interface/wallets/manage-wallets) to learn how to create multi-chain wallets.

## Supported networks

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 | ✓ | ✓ | ✓ | ✓ |


## Transaction and signing capabilities

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 | ✓ | ✓ | ✓ | — | ✓ | ✓ |


## Operational features

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 | ✓ | ✓ | — |


## Feature reference

This section defines each feature shown in the tables above.

### Environment

| 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. |


### Key management

| Feature | Description |
|  --- | --- |
| MPC (CloudSign) | Keys are split across CloudSign devices using Multi-Party Computation. See [Set up and run CloudSign](/products/wallet/user-interface/devices/set-up-and-run-cloudsign). |
| MPC (Mobile) | Keys are split across mobile devices using Multi-Party Computation. See [Adding a device](/products/wallet/user-interface/devices/adding-a-device). |


### Assets

| 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). See [Supported token standards](#supported-token-standards) for the full list of token types supported on each chain. |


### Transaction capabilities

| 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](/products/wallet/user-interface/transactions/raw-signing). |
| WalletConnect | You can connect wallets to decentralized applications (dApps) using the [WalletConnect](https://reown.com/) protocol. This enables swaps, liquidity provision, and other dApp interactions. See [Connections](/products/wallet/user-interface/integrations/open-a-connection). |
| 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. |


### Operations

| Feature | Description |
|  --- | --- |
| Sweeping | Automated consolidation of funds from multiple wallets into a destination wallet. See [Asset sweeping](/products/wallet/user-interface/wallets/asset-sweeping). |
| Fee estimation | Transaction fees can be estimated before submission. |
| Multi-chain | A single wallet address works across multiple EVM-compatible chains. |


## Supported token standards

Palisade classifies tokens using the following standard types. These types are used in the API when specifying token operations.

| Standard | ID | Description |
|  --- | --- | --- |
| NATIVE | 1 | The blockchain's native asset (for example, ETH, SOL, BTC). |
| ERC20 | 2 | EVM fungible tokens. Also covers TRC-20 on Tron and BEP-20 on BNB Smart Chain, which use the same contract interface. |
| ISSUED_CURRENCY | 3 | XRP Ledger trustline-based tokens. |
| ERC721 | 4 | EVM non-fungible tokens (NFTs). |
| SPL | 5 | Solana tokens. Covers both the original SPL Token program and Token-2022 (Token Extensions). |
| CUSTOM | 99 | 1Money proprietary tokens. |


### Token support by chain

The following table summarizes which token standards are available on each blockchain.

| Chain | NATIVE | ERC20 | ISSUED_CURRENCY | ERC721 | SPL | CUSTOM |
|  --- | --- | --- | --- | --- | --- | --- |
| Arbitrum | ✓ | ✓ | — | ✓ | — | — |
| Avalanche | ✓ | ✓ | — | ✓ | — | — |
| Base | ✓ | ✓ | — | ✓ | — | — |
| Bitcoin | ✓ | — | — | — | — | — |
| BNB Smart Chain | ✓ | ✓ | — | ✓ | — | — |
| Ethereum | ✓ | ✓ | — | ✓ | — | — |
| 1Money | ✓ | — | — | — | — | ✓ |
| Polygon | ✓ | ✓ | — | ✓ | — | — |
| Solana | ✓ | — | — | — | ✓ | — |
| Tron | ✓ | ✓ | — | — | — | — |
| XRP Ledger | ✓ | — | ✓ | — | — | — |


### Chain-specific token details

#### EVM chains

**Applies to:** Ethereum, Polygon, Arbitrum, Avalanche, Base, BNB Smart Chain

EVM-compatible chains support the following token standards:

- **NATIVE** — The chain's native gas token (ETH, MATIC, ARB, AVAX, BNB).
- **ERC-20** — Fungible tokens following the ERC-20 standard. BNB Smart Chain uses the BEP-20 standard, which is functionally identical and mapped to `ERC20` in the API.
- **ERC-721** — Non-fungible tokens (NFTs). Supported operations include mint, burn, and transfer.


#### Solana

Solana supports the following token standards:

- **NATIVE** — SOL, the chain's native asset.
- **SPL** — Tokens issued through either the SPL Token program or the Token-2022 (Token Extensions) program. Both token programs are supported at the connector level under the single `SPL` standard type.


Supported token operations: transfer, mint, burn, freeze, thaw, close account, and set authority.

#### Tron

Tron supports the following token standards:

- **NATIVE** — TRX, the chain's native asset.
- **TRC-20** — Fungible tokens following the TRC-20 standard. TRC-20 uses the same contract interface as ERC-20 and is mapped to `ERC20` in the API.


#### Bitcoin

Bitcoin supports **NATIVE** only (BTC). Transactions use the UTXO model.

Supported script types: P2PKH, P2WPKH, P2SH, P2WSH, P2TR, and nested SegWit.

Not supported on Bitcoin
BRC-20, Ordinals, and Runes token standards are not supported.

#### XRP Ledger

XRP Ledger supports the following token standards:

- **NATIVE** — XRP, the ledger's native asset.
- **ISSUED_CURRENCY** — Trustline-based tokens issued on the XRP Ledger. These tokens require a trust line between the holder and the issuer.


Additional supported operations: clawback and AMM (Automated Market Maker) transactions.

#### 1Money

1Money supports the following token standards:

- **NATIVE** — 1MONEY, the chain's native asset.
- **CUSTOM** — Proprietary tokens issued on the 1Money network.


Supported token lifecycle operations: create, mint, burn, freeze, pause, whitelist, blacklist, and authority management.

### Unsupported token standards

Not currently supported
The following token standards are **not** supported by Palisade:

- **ERC-1155** — Multi-token standard (combined fungible and non-fungible tokens in a single contract).
- **BRC-20 / Ordinals / Runes** — Bitcoin-based token standards.
- **Hedera tokens** — The Hedera connector has been deprecated and is no longer available.