Complete List of 2024 Cryptocurrencies Supported by SafePal: Bitcoin, Ethereum, Solana & Beyond

A user with holdings across multiple blockchains faces a recurring problem: managing Bitcoin, Ethereum, Solana, and dozens of token standards across different wallets introduces complexity, increases the surface area for phishing attacks, and creates unnecessary points of failure. The practical appeal of a single non-custodial hardware wallet ecosystem is substantial—one device, one recovery phrase, full offline signing. But the question that determines whether such a wallet is actually useful is straightforward: which cryptocurrencies does it actually support, and how thoroughly?

SafePal wallet has built its value proposition around breadth of support combined with air-gapped security. The S1 hardware device stores private keys completely offline in a secure element chip, communicating exclusively through QR code scanning rather than USB or wireless connectivity. The paired mobile application on Android and iOS displays balances and constructs transactions, but never touches the private keys. This separation means that a user can hold Bitcoin, Ethereum, thousands of ERC-20 and BEP-20 tokens, Solana assets, and numerous other cryptocurrencies from a single ecosystem without exposing signing keys to network-connected devices. Understanding the exact scope of that support—which networks are included, which token standards are recognized, and how custom assets are added—is essential for evaluating whether SafePal addresses your actual holdings.

Bitcoin, Ethereum, and the foundational layer

Bitcoin support is the baseline expectation for any serious cryptocurrency hardware wallet. SafePal Wallet handles Bitcoin across the main network with standard address types including Legacy (P2PKH), Segwit (P2WPKH), and Taproot (P2TR) formats. The wallet generates extended public keys that the mobile app uses to derive addresses and monitor balances without ever exposing the private keys that sign transactions. When a user initiates a Bitcoin transaction through the mobile application, the unsigned transaction is encoded as a QR code, scanned by the S1 device, verified on the hardware screen, and signed offline. Only after confirmation on the physical device does the signed transaction return to the mobile app via QR code for broadcast to the network.

This workflow eliminates the risk that a compromised phone or man-in-the-middle attack can alter a transaction in flight. A user sees the receiving address and amount on the S1’s screen before signing, creating a verification point that most software wallets cannot offer. Bitcoin Lightning Network transactions and complex transaction types such as spending from multisig addresses or timelocked outputs require additional considerations; standard single-signature transactions are well-supported.

Ethereum support extends beyond the main network to include Layer 2 solutions and alternative chains. SafePal Wallet recognizes transactions on Ethereum mainnet, Polygon (formerly Matic), Arbitrum, Optimism, Base, and other EVM-compatible networks. The mobile app displays separate account balances for each network because they use different RPC endpoints and require independent transaction construction. When signing an Ethereum transaction, the S1 device shows the transaction amount in the native token, gas limit, and recipient address on its screen. The advantage here is particularly acute: Ethereum’s native token precision and gas parameters are frequent sources of user error in software wallets. Hardware verification catches mistakes before they are broadcast.

ERC-20 tokens and the Ethereum ecosystem

ERC-20 is the most widely used token standard on Ethereum, covering everything from stablecoins like USDC and USDT to governance tokens such as Uniswap’s UNI and Aave’s AAVE. SafePal Wallet includes a curated list of well-known ERC-20 tokens that appear directly in the mobile application’s asset list. These tokens use the same Ethereum addresses as the native ETH account; they are distinguished by their contract addresses and are tracked separately on the blockchain through transfer events.

The distinction matters operationally. When you hold USDC on Ethereum through SafePal Wallet, the mobile app constructs an ERC-20 transfer transaction that calls the USDC contract’s transfer function. The S1 device signs this transaction and displays it on its screen, but the information it shows is more limited than for native token transfers. Hardware wallets typically display the contract address being called rather than a human-readable token name, because verifying a token’s legitimacy requires access to external data that the air-gapped device cannot reliably obtain. SafePal addresses this through the mobile app: users should verify that they are sending to an Ethereum address they recognize and that the app shows the correct token before scanning the QR code to the hardware device.

Adding custom ERC-20 tokens to SafePal Wallet requires knowing the contract address and inputting it through the mobile app. Once added, the token appears in your asset list and can be sent and received like any built-in token. This flexibility is crucial because new tokens launch constantly, and waiting for SafePal to add them officially could take weeks. However, this flexibility carries a corresponding responsibility: pasting or entering the wrong contract address will create a token entry that appears legitimate in your wallet but may not correspond to the actual asset you intend to hold. Verification through a blockchain explorer before importing a custom contract address is a necessary precaution.

BEP-20 tokens and the Binance Smart Chain ecosystem

Binance Smart Chain (BSC), now rebranded as BNB Chain, operates its own token standard called BEP-20, functionally similar to ERC-20 but deployed on a separate blockchain with its own transaction fees and finality. SafePal Wallet supports BEP-20 tokens including the native BNB coin, wrapped versions of Bitcoin and Ethereum (WBTC and WETH on BSC), and thousands of other tokens launched through the ecosystem. Because BNB Chain is EVM-compatible, the experience of using SafePal on BSC is similar to Ethereum: transaction construction through the mobile app, verification and signing on the hardware device via QR codes.

The operational difference is cost. BNB Chain has historically offered substantially lower transaction fees than Ethereum because it uses a smaller validator set and processes transactions more quickly. A BEP-20 token transfer might cost a few cents in BNB rather than dollars in ETH gas fees. This cost advantage has attracted significant trading volume and made BNB Chain a practical destination for users managing token portfolios on a budget. SafePal’s support for the network and its tokens reflects this importance. The wallet displays BNB balances separately from ETH balances because they exist on different chains, and a user must explicitly choose which network to send from and to when moving funds.

Custom BEP-20 tokens are added through the same process as ERC-20: entering the contract address in the mobile app. The contract address for a BEP-20 token is different from the ERC-20 contract address for a token with the same name, even though they represent the same underlying asset. USDT, for example, exists as both an ERC-20 token on Ethereum and a BEP-20 token on BNB Chain, with distinct contract addresses. Sending USDT from a BEP-20 address to an Ethereum wallet will result in permanent loss because the chains do not interoperate. SafePal’s mobile interface displays the network alongside the token name to reduce this confusion, but the responsibility for specifying the correct destination remains with the user.

Solana and non-EVM ecosystems

Solana represents a fundamentally different blockchain architecture from Ethereum and BNB Chain. Rather than using account-based transaction models with smart contract state stored in a single global ledger, Solana uses a parallel processing design where transaction validators read and modify independent account objects. This affects how SafePal Wallet handles Solana accounts and tokens. The mobile app generates Solana addresses derived from the same recovery phrase as Bitcoin and Ethereum addresses, but Solana addresses use a different format and are incompatible with EVM chains.

Token standards on Solana diverge from ERC-20 and BEP-20 as well. The native token standard is SPL (Solana Program Library), and thousands of tokens are issued through this standard. SafePal Wallet recognizes popular SPL tokens including the USD Coin (USDC) on Solana, SOL-wrapped Bitcoin (soBTC), and governance tokens such as Serum’s SRM. Adding custom SPL tokens requires the token’s mint address, which plays the same role as a contract address on Ethereum. The mobile app displays SPL token balances separately from SOL native token balances, just as it does for ERC-20 tokens on Ethereum.

Solana’s transaction model means that token transfers are not function calls to a smart contract but rather direct modifications to token account objects. When you sign a Solana transaction in SafePal Wallet, you are signing an instruction to modify the blockchain state directly. The hardware wallet’s display of Solana transactions is more granular than Ethereum, showing program addresses and instruction sequences, which can be unfamiliar to users accustomed to Ethereum’s contract-call model. This is not a limitation of SafePal specifically but rather a reflection of Solana’s design. Understanding that Solana operates differently prevents mistakes such as attempting to send a Solana token to an Ethereum address derived from the same recovery phrase, which would result in loss.

Layer 2 solutions, alternative Layer 1 chains, and cross-chain complexity

SafePal Wallet’s support extends to numerous scaling solutions and alternative Layer 1 blockchains. Polygon, which operates as an EVM-compatible sidechain and more recently as a ZK-rollup, is fully supported. Arbitrum and Optimism, which are Ethereum rollups, operate as EVM chains with their own transaction fees and finality rules. Base, Linea, and zkSync are additional EVM rollups supported by the wallet. Each of these networks requires separate configuration in the mobile app because they have distinct RPC endpoints and gas token denominations.

The critical operational point is that addresses on these networks are the same format (Ethereum-style 0x addresses) but the assets are not interchangeable. One USDC on Ethereum is not the same as one USDC on Arbitrum; they are separate instances of the token, and transferring between them requires a bridge. SafePal Wallet does not operate a bridge itself; instead, users must understand which token instance they hold, on which chain, and use an appropriate bridge (such as those offered by Across, Stargate, or the Arbitrum Bridge) to move assets between networks. The mobile app’s display of balances separated by network helps users avoid confusion, but the final responsibility for understanding token instances remains with the user.

Non-EVM blockchains such as Litecoin, Dogecoin, and Cosmos chains are also supported by SafePal. These networks use their own address formats and require independent implementations in the wallet. Litecoin operates a UTXO model similar to Bitcoin with its own script language and transaction types. Cosmos chains use delegated proof-of-stake and operate as independent blockchains coordinated through the Cosmos IBC (Inter-Blockchain Communication) protocol. SafePal’s breadth of support across these ecosystems reflects its positioning as a universal cryptocurrency hardware wallet, though the level of detail displayed for less common chains may be less granular than for Bitcoin and Ethereum.

Adding custom tokens and managing unknown assets

SafePal’s ability to support thousands of cryptocurrencies depends significantly on the custom token feature. When a new token launches or when a user holds a less well-known asset, they can add it manually by entering the contract address or token mint address through the mobile app. This flexibility is valuable because the set of cryptocurrency tokens changes constantly; no wallet can include every token without becoming unmaintainable. However, this flexibility requires discipline from the user.

When adding a custom token, the mobile app typically asks for the contract or mint address and may request additional information such as the token’s name, symbol, and decimal places. If you enter an incorrect address, the wallet will create an entry for that contract, but you will not actually hold the token you intended. This is particularly dangerous because you might think you have received a token transfer when you have actually received a different token (or nothing). A test transfer of a small amount to verify the process is prudent before moving larger quantities. Always verify the contract or mint address through an official source such as the project’s website or a blockchain explorer rather than copying it from social media or an unverified message.

SafePal’s approach to custom tokens means that your wallet can hold virtually any ERC-20, BEP-20, SPL, or comparable token, but your responsibility for accuracy is correspondingly higher. The hardware wallet itself cannot validate whether a contract address is legitimate; it can only sign the transaction you present to it. The mobile app can display balance information if it connects to the correct RPC endpoint, but if the token is extremely new or from a non-standard chain, the app may show a zero balance even if the blockchain contains the token. These scenarios are rare but worth understanding before assuming that your wallet is broken.

Stablecoins, wrapped assets, and cross-chain token instances

Stablecoins—cryptocurrencies designed to maintain a stable value relative to a fiat currency or basket of assets—are among the most actively held tokens. SafePal Wallet supports major stablecoins including USDC, USDT, DAI, BUSD, and others across multiple blockchain instances. USDC, for example, is available as an ERC-20 token on Ethereum, a BEP-20 token on BNB Chain, an SPL token on Solana, and comparable tokens on Arbitrum, Polygon, and numerous other networks. Each instance is a separate token on a separate chain, and the wallet displays them independently.

Wrapped assets complicate the picture further. Wrapped Bitcoin (WBTC) on Ethereum is an ERC-20 token that represents Bitcoin held in custody by a merchant, and it trades on a 1:1 basis with Bitcoin during normal market conditions. However, WBTC is not Bitcoin; it is a claim on Bitcoin held elsewhere, and if the custodian fails or becomes compromised, the WBTC becomes worthless. SafePal Wallet displays WBTC in your Ethereum token list, but the wallet cannot verify the custody or financial soundness of the merchant backing the wrapper. Wrapped assets are useful for accessing Bitcoin’s value in Ethereum’s DeFi ecosystem, but they represent a different risk profile than holding native Bitcoin on the Bitcoin network.

This distinction becomes important when thinking about your overall cryptocurrency allocation. If you hold native Bitcoin in the SafePal Wallet’s Bitcoin account, WBTC in the Ethereum account, and soSOL in the Solana account, you have three separate asset instances that may have different price movements and different custody or smart contract risks. SafePal Wallet displays them separately by design, but understanding what each represents is the user’s responsibility. The mobile app does not annotate wrapped assets with warnings about custody risk or smart contract dependencies, so users must bring that context themselves.

Practical considerations for wallet setup and coin management

Setting up SafePal Wallet to handle multiple cryptocurrencies begins with initializing the S1 hardware device and backing up the recovery phrase. SafePal uses a 24-word BIP39 recovery phrase that generates the master private key for all supported networks. A single recovery phrase can recreate your Bitcoin, Ethereum, Solana, and all other addresses, provided you backup the phrase securely. The hardware device generates the phrase offline, and you should write it on paper, store it in a tamper-evident holder or safe deposit box, and never photograph it or enter it into a digital file.

After backing up the recovery phrase, you pair the hardware device with the mobile app by scanning a QR code on the S1 screen with your phone. The mobile app then displays your Bitcoin, Ethereum, and other account balances, allowing you to add additional networks or tokens as needed. This initial setup is designed to be beginner-friendly, but the flexibility of SafePal to support thousands of cryptocurrencies means that you should approach it methodically. Rather than adding every possible token, focus on the cryptocurrencies you actually hold and plan to use. This reduces clutter in your app interface and decreases the risk of sending tokens to the wrong contract address.

For users managing substantial holdings across multiple chains, spending time to organize your SafePal setup is worthwhile. Create a document (stored offline) listing the specific contracts or mint addresses of tokens you hold, the networks they are on, and the purpose of each holding. When you receive a new token or acquire a position on a new chain, update the document and verify the address before adding it to your wallet. This external reference prevents costly mistakes such as importing a token twice with different contract addresses or confusing USDT on Ethereum with USDT on BNB Chain.