Phantom Wallet Token Standard Support: SPL vs ERC-20 vs BRC-20 and Why Some Assets Won’t Display

A user has installed Phantom as a multi-chain wallet, funded an Ethereum account with tokens, and created a Solana address. Yet when they send SPL tokens to what they thought was the correct Solana address, or receive an ERC-20 token on Ethereum, the asset either appears immediately or vanishes into a silent failure. The difference often comes down to token standards—the technical specifications that define how tokens are created, transferred, and recognized on each blockchain. Phantom supports multiple standards across multiple networks, but not every token uses a standard the wallet understands, and not every network receives the same treatment.

This distinction matters because token standards are not interchangeable across chains, and a wallet’s support for one network does not automatically grant support for every token variant on that network. A token standard like SPL on Solana, ERC-20 on Ethereum, or BRC-20 on Bitcoin represents a contract format, data structure, and set of operational rules. When a token does not conform to a standard Phantom recognizes, the wallet may receive the transaction without being able to decode or display the balance. The result is that a user can send funds to an address and lose visibility of them entirely—not because the transaction failed, but because the wallet cannot interpret what it received.

How token standards define what a wallet can see

A token standard is a technical specification that establishes how a particular blockchain treats tokens as programmable assets. On Solana, the SPL (Solana Program Library) standard defines token creation, account ownership, minting, and transfer logic. On Ethereum, ERC-20 tokens follow a similar functional set but use Ethereum’s smart contract interface and gas model. BRC-20, newer and more experimental, attempts to enable comparable token functionality on Bitcoin through Ordinals and inscriptions. Each standard encodes assumptions about who can approve transfers, how balances are stored, what happens during a transaction, and what metadata a wallet can retrieve.

Phantom must recognize these standards to translate them into user-readable information. When a transaction arrives on a Solana account, Phantom queries the token program to understand the transfer. If the program matches a known SPL standard, the wallet updates the balance display and updates the NFT inventory if applicable. If the token uses a non-standard or newly invented variant, Phantom may still receive the transaction at the blockchain level—the cryptography and consensus still function—but the wallet cannot reliably determine what the transaction means or what it should display to the user. The funds technically exist on the chain, but they are invisible to the interface.

This is why a Phantom Ethereum wallet might receive an ERC-20 token successfully, while an ERC-1155 or other non-ERC-20 token standard may not appear in the main token list. Ethereum supports multiple standards because it is a smart contract platform, and developers can create token systems that follow different rules. Phantom is built to recognize the most common standard on each network, but supporting every possible variant would require the wallet to maintain code and parsing logic for dozens of specifications, many of which are used by few projects.

The practical implication is that before sending assets to a Phantom address, a user should verify not only the network but also the token standard. A wallet address on Ethereum is technically able to receive any smart contract interaction, but Phantom’s interface will only display balances and allow transfers for tokens it has been built to handle. The same address could receive an ERC-721 NFT, an ERC-1155, an ERC-20, or a custom token, yet only some would be visible in the interface without manual import.

SPL tokens and Solana’s unified approach

Solana’s approach to token standards is more uniform than Ethereum’s because the blockchain itself has a single, dominant token standard. Nearly all Solana tokens follow SPL, which specifies how token mints, accounts, and transfers work. Phantom’s support for Solana is therefore more predictable: if a token is minted on Solana and follows the SPL specification, Phantom should recognize it. The wallet indexes tokens by mint address, a unique identifier that points to the token’s definition and supply rules.

However, even SPL tokens can present edge cases. Some tokens have low liquidity or are brand new, and Phantom’s token list may not include them automatically. A user can add such tokens manually by importing the mint address, which tells the wallet to look for and display balances of that specific token. This manual import does not require the token to be a different standard; it is simply Phantom’s way of allowing users to add tokens that the wallet has not indexed yet. The distinction is important: the token is still SPL, still valid on the blockchain, still transferable, but Phantom did not pre-load it into the standard list.

Wrapped tokens also present a consideration. A wrapped token is one that exists natively on another chain—such as Wrapped Ethereum on Solana—and is backed by a custodian or bridge. Phantom supports major wrapped assets, but the wrapping mechanism itself is still SPL. From the wallet’s perspective, Wrapped Ethereum is an SPL token like any other, and the technical risk comes from the bridge’s design and operation, not from the wallet’s ability to recognize it.

ERC-20 and the diversity of Ethereum token standards

Ethereum’s flexibility as a smart contract platform created room for multiple token standards to coexist. ERC-20 became the dominant standard for fungible tokens and is what most users mean when they refer to “Ethereum tokens.” A Phantom Ethereum wallet will recognize and display ERC-20 tokens by default. However, Ethereum also supports ERC-721 for non-fungible tokens, ERC-1155 for semi-fungible assets, and dozens of lesser-used variations including ERC-223, ERC-777, and others. Each has slightly different transfer mechanics, callback hooks, or data structures.

Phantom’s NFT tools specifically support ERC-721 and ERC-1155 standards, allowing users to view, send, and list NFTs. But a token that follows ERC-223 or a custom variant will not display in Phantom’s token list in the same way an ERC-20 will. Some custom tokens include additional logic—such as transaction fees to a developer wallet, or voting power tied to the token—that deviates from the ERC-20 specification. Phantom does not prevent interaction with these tokens; rather, the wallet displays what it can verify and remains conservative about what it claims to show.

A related issue is that Ethereum token contracts can be phishing traps or scams. A project can deploy an ERC-20 contract with a name similar to a legitimate token, and if a user imports that contract by address, they may send valuable tokens to it and be unable to recover them. Phantom’s scam warnings attempt to flag known phishing tokens and suspicious contracts, but the warning system depends on community reporting and detection. An unknown or very new token remains a risk even if it is technically a valid ERC-20. A user should always verify the contract address from an official source before importing or sending to an unknown token.

BRC-20 and Bitcoin’s emerging token layer

BRC-20 is a newer and more experimental token standard that operates on Bitcoin through Ordinals and inscriptions. Rather than using Bitcoin’s native scripting to create tokens, BRC-20 encodes token operations in Ordinal inscriptions—data stored on individual satoshis in the Bitcoin blockchain. This approach is radically different from SPL or ERC-20, because Bitcoin’s base layer has never natively supported custom tokens. BRC-20 is essentially a convention that application developers have agreed to follow, but it is not enforced by Bitcoin’s consensus rules.

Phantom’s Bitcoin wallet support is still evolving. When Phantom Bitcoin wallet functionality is available, it provides the ability to send and receive native Bitcoin and interact with compatible token standards. However, BRC-20 support may lag behind Ethereum and Solana support because the standard is newer and ecosystem adoption is less settled. Some projects and exchanges recognize BRC-20 tokens, while others consider them experimental or do not support them at all. A user who holds a BRC-20 token and wants to verify its balance in Phantom should first confirm whether Phantom’s current version recognizes the specific token, as support is likely to be more limited than for established standards.

The practical difference is that BRC-20 tokens are indexable—someone can scan the Bitcoin blockchain and read inscriptions to track balances—but they do not benefit from Bitcoin’s built-in security for token operations the way ERC-20 tokens benefit from Ethereum’s smart contract environment. A BRC-20 token transfer depends on the application recognizing and parsing the inscription correctly. If Phantom has not been designed to parse that particular token’s inscription format, the transaction may succeed at the Bitcoin level but be invisible to the Phantom interface.

Why some tokens disappear and how to recover visibility

A user sends a token to their Phantom address and it vanishes from the interface. The most common scenario is a token standard mismatch. If a user received an ERC-1155 on their Ethereum address, Phantom will not display it in the regular token list because ERC-1155 is not the standard fungible token format. If a user sent an SPL token to a Phantom Solana address but the token is not in Phantom’s pre-loaded list, the wallet may not have indexed it yet. In both cases, the assets are on the blockchain and remain the user’s property—they are just invisible in this particular wallet interface.

Recovery requires first identifying what token standard was involved. Check the transaction on a blockchain explorer such as Solscan for Solana or Etherscan for Ethereum. The explorer will show the token contract or program and its standard. For Solana, find the mint address and add it manually in Phantom. For Ethereum, find the contract address and use Phantom’s token import feature to add the ERC-20 contract. For ERC-721 or ERC-1155 tokens, the NFT import feature is the equivalent path. Once imported, Phantom should recognize the token and display the balance.

If the token still does not appear, verify that it is held in the correct account. Phantom supports account management, and tokens may be distributed across multiple accounts within a single wallet. Navigating to the account management section and switching between accounts can reveal where a token has been received. Additionally, check whether the token contract itself is valid. If it is a brand-new token with no trading history or recognition by legitimate sources, it may be a scam or test contract, and recovery may not be possible even if the blockchain transaction is valid.

Multi-chain support and the importance of address and standard verification

Phantom functions as a multi-chain wallet, supporting Solana, Ethereum, Base, Polygon, Bitcoin, and others. This flexibility is valuable because a user can manage assets across networks without running multiple wallets or trusting centralized exchanges. However, it also increases the likelihood of error. Each network has different token standards, different fee models, and different recovery mechanisms. A user must verify not only the destination address but also the network and the token standard before sending.

The wallet provides transaction previews, a feature that displays the proposed transaction before signing. Using this feature reduces the risk of sending to the wrong address or network, but it does not protect against choosing the wrong token standard. If a user intends to send an ERC-20 but mistakenly selects an ERC-1155, or tries to send an SPL token to an Ethereum address, the preview should flag the mismatch—but this depends on the wallet recognizing the standard. Users who understand token standards are better equipped to avoid these errors.

Users can verify their setup and understand Phantom’s multi-chain capabilities by visiting the Phantom Wallet download page and setup process, which provides documentation on supported networks and standards. After installation on Chrome, Brave, Firefox, iOS, or Android, new users should familiarize themselves with account creation, recovery phrase backup, and the token import process before moving significant assets. Self-custody means the user is responsible for protecting recovery phrases and verifying transactions, so understanding how the wallet handles different token standards is an essential part of that responsibility.

Scam tokens and the limits of automatic detection

Phantom’s scam warnings provide an additional layer of protection by flagging known malicious contracts and phishing tokens. However, this system is reactive: it depends on sufficient users reporting a token as harmful, and on Phantom’s team or community adding it to a blocklist. A token that is brand new, has a small number of holders, or uses sophisticated obfuscation may evade automatic detection for a time. A user should treat scam warnings as a helpful signal but not as a complete guarantee of safety.

The risk is particularly high when a token appears to be a well-known project but is actually a copycat. A scammer can deploy an ERC-20 contract with a name and symbol that closely matches a legitimate token, and if a user imports the wrong contract address, they may send their own tokens into the scam contract and be unable to retrieve them. This is not a failure of Phantom’s technical architecture; it is a fundamental property of blockchain transactions. Once signed and broadcast, a transaction cannot be reversed, even if the recipient is a malicious contract. Phantom emphasizes this self-custody responsibility: the wallet cannot reverse transactions or recover lost assets.

Token standard support as a feature that evolves

Phantom’s support for different token standards continues to evolve. As new blockchains are integrated and as token standards themselves develop, the wallet must be updated to recognize them. Base, Polygon, and other EVM-compatible (Ethereum Virtual Machine compatible) chains share ERC-20 and similar standards, so adding support for a new EVM chain is more straightforward than supporting an entirely new blockchain with its own token standard. Solana integration is mature because SPL is singular and well-established. Bitcoin’s token layer through BRC-20 and other Ordinal-based standards is still being refined, so support may grow over time.

Users should check the wallet’s documentation and release notes to understand what token standards are currently supported on each network. A feature request for a token standard that Phantom does not yet recognize may be submitted through community channels, but users should not assume that a feature will be added quickly or at all. The decision to support a new standard involves security review, testing, and a judgment about the standard’s adoption and legitimacy. Some experimental token standards may never be incorporated if they remain niche or if they present security or usability risks.