Blockchains and tokens

Wallet-as-a-Service (Palisade) supports multiple blockchain networks. This page describes the features available for each supported chain.

The following table shows feature availability for each blockchain.

The following table shows transaction and signing features for each blockchain.

The following table shows operational features for each blockchain.

Wallet-as-a-Service (Palisade) processes an incoming transaction as confirmed and reflects it in your wallet balance once it reaches the chain-specific threshold below.

For block-based thresholds, the value is the number of additional blocks Palisade waits after the block containing the transaction. Under the usual convention where the containing block is confirmation 1, a threshold of N additional blocks means the transaction has N + 1 confirmations when Palisade processes it.

Some chains expose a finality mechanism instead of requiring Palisade to apply an additional block threshold:

• Solana — Palisade uses the finalized commitment level.
• XRP Ledger — Palisade processes transactions from validated ledgers.
• 1Money — Palisade processes transactions from the latest checkpoint.

This section defines each feature shown in the tables above.

Palisade classifies tokens using the following standard types. Use these types in the API when you specify token operations.

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

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 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. The connector supports both token programs under the single SPL standard type.

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

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 Palisade maps it to ERC20 in the API.

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

Palisade supports native BTC sweeping. Palisade doesn't support Bitcoin token standards such as BRC-20, Ordinals, and Runes for sweeping or other token operations.

Palisade supports these script types: P2PKH, P2WPKH, P2SH, P2WSH, P2TR, and nested SegWit.

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