A developer or trader working with emerging Layer 1 and Layer 2 blockchains faces a practical bottleneck: most wallet interfaces ship with support for established networks only, requiring manual configuration or switching to less familiar applications. Sui and HyperEVM represent two distinct ecosystems—one designed for parallel execution and high throughput, the other focused on EVM compatibility with lower-cost operations—yet they receive limited pre-configuration in standard wallet software. The result is that users wanting to explore these networks must either accept default settings that may not include the correct RPC endpoints or manually add custom networks, a process that introduces room for error if documentation is vague or wallet UI is unfamiliar.

Phantom Wallet, originally built for Solana, has expanded into a comprehensive multi-chain wallet supporting several blockchain networks, and it now offers the flexibility to add Sui and HyperEVM through its network settings. However, the process is not identical to adding a well-known EVM chain, because Sui uses a fundamentally different transaction model and HyperEVM requires specific RPC configuration to function correctly. Understanding which settings matter, which can be left default, and how to verify that a network connection is working prevents wasted transactions, failed swaps, and the frustration of tokens disappearing into a misconfigured address space.

Why Phantom Wallet expanded beyond Solana

When Phantom Wallet launched, Solana was its exclusive focus. That narrowness had advantages: the application could optimize for SPL tokens, Solana’s transaction model, and the program ecosystem without worrying about EVM compatibility, different fee structures, or conflicting standards. As the broader cryptocurrency market matured, users increasingly needed a single application to manage assets across multiple chains rather than maintaining separate wallets for Bitcoin, Ethereum, Polygon, and specialized networks.

Expanding Phantom Wallet into a true multi-chain wallet required fundamental architectural decisions. The wallet retained its non-custodial model—users control their private keys through the Secret Recovery Phrase—but had to support different key derivation paths and address formats. Solana uses Ed25519 signatures and a straightforward linear address model. Ethereum and its descendants use Secp256k1 signatures and account-based accounting. Sui introduces yet another variation, with object-centric storage and a transaction format optimized for parallelization. Rather than building separate applications, Phantom unified these under one interface, allowing users to hold and transact in multiple assets from a single recovery phrase.

The practical result is that a user can download Phantom Wallet, secure their 12-word Secret Recovery Phrase once, and then add networks as needed without re-entering sensitive information or managing separate backup files. This convenience matters for adoption. When a user is curious about Sui’s transaction speed or HyperEVM’s lower fees, the friction of switching wallets often prevents exploration. By supporting these networks natively, Phantom Wallet removes an adoption barrier.

Yet this expansion also means that users must develop new operational habits. A multi-chain wallet is not simply Solana with extra buttons. Different networks have different transaction confirmation times, fee calculation methods, and security assumptions. A user familiar only with Solana’s 400-millisecond slots may be surprised by Ethereum’s 12-second blocks or confused when a Sui transaction settles in a different way. The wallet interface attempts to normalize this experience, but it cannot eliminate the underlying differences.

Understanding Sui’s unique transaction model

Before configuring Sui in Phantom Wallet, it helps to understand why Sui is not simply another EVM network. Sui uses an object-centric programming model rather than account-based storage. Instead of updating a global ledger state, Sui transactions modify specific objects owned by addresses. This design choice allows parallel execution: transactions that touch different objects can be processed simultaneously, whereas EVM chains must serialize many operations. The result is higher throughput per validator and lower latency for simple payments.

This architectural difference affects how wallets display transactions and manage gas. On Ethereum or Polygon, a transaction costs gas based on computational operations, and users typically see a single gas price. Sui separates gas computation from storage costs. The network charges for the bytes an object consumes, and that storage cost is often predictable—a simple token transfer may cost less than an equivalent Ethereum transaction despite similar complexity. Phantom Wallet abstracts much of this calculation, but understanding the distinction helps users make sense of why Sui gas estimates differ from Ethereum’s.

Address derivation also matters. Sui uses Ed25519 signatures by default, like Solana, but Solana and Sui wallets derive addresses from keys differently. A user importing a recovery phrase into both Phantom’s Solana configuration and its Sui configuration will see different addresses. This is correct behavior—the addresses are genuinely separate—but it can be confusing if a user expects one address per wallet across all chains. The security implication is important: a Solana address from the same recovery phrase cannot receive Sui tokens directly without explicitly switching networks in the wallet interface.

When adding Sui to Phantom Wallet, the application typically includes a pre-configured RPC endpoint, so most users do not need to manually enter network details. However, if the public RPC becomes congested or if you want to use a specific node provider, you can customize the endpoint. The key requirement is that the RPC speaks the Sui JSON-RPC API, which differs from Ethereum’s standard Web3 interface. A misconfigured endpoint will either fail to load balance data or display error messages when you attempt transactions.

Adding Sui as a network in Phantom Wallet

The process of adding Sui to Phantom Wallet depends on whether the network is already pre-configured. In most recent versions, Sui is included by default, so users can simply select it from the network dropdown without performing manual setup. If you are using an older version or if Sui is not visible, you can add it manually through the wallet’s settings. The process is: open Phantom, click the network selector dropdown at the top of the interface, and look for a “Add Network” or “Manage Networks” option. From there, you can input the network name (“Sui Mainnet”), RPC endpoint, and other details.

For Sui specifically, the official RPC endpoint is typically provided by Mysten Labs, the development team behind Sui. You can verify the current recommended endpoint by checking the Sui documentation or using a reliable RPC provider such as QuickNode or Ankr, which maintain Sui nodes and publish their endpoints publicly. If you use a custom RPC provider, confirm that it is reputable and has a history of uptime; a slow or unstable RPC can cause transaction delays and wallet sync failures.

Once Sui is added and selected, Phantom Wallet will derive a Sui address from your recovery phrase. This address will be displayed in the wallet interface, and you can copy it to receive tokens or NFTs on the Sui network. The address format is a hexadecimal string prefixed with “0x,” which is standard for Sui. If you have an existing Sui wallet from another application, you can also import its private key or recovery phrase into Phantom by selecting “Import Wallet” during setup, though best practice is to avoid reusing recovery phrases across multiple applications if possible.

Before sending significant funds to your new Sui address, send a small test transaction from a crypto exchange, bridge, or existing wallet to confirm that the address is correct and that you can see the funds arrive. Sui wallets display a transaction hash and status, which you can verify on a Sui block explorer such as Suivision or the official Sui Explorer. Waiting for one small transaction to confirm takes minutes and prevents the costlier mistake of sending a large amount to the wrong address or misconfigured network.

Configuring HyperEVM and validating RPC settings

HyperEVM is less widely known than Sui, but it serves a specific niche: an EVM-compatible chain with lower fees and faster finality, often positioned as an alternative to Polygon or Optimism for developers and users who want Ethereum compatibility without the higher costs. Because HyperEVM is an EVM chain, the process of adding it to Phantom Wallet follows the standard EVM network configuration pattern, but the specific RPC endpoint and chain ID are critical to get right.

To add HyperEVM, open Phantom Wallet and navigate to the network selector. Choose “Add Custom Network” or a similar option. You will then enter the following details: Network Name (e.g., “HyperEVM”), RPC URL, Chain ID, Currency Symbol (typically ETH), and optionally a block explorer URL. The RPC endpoint for HyperEVM depends on which provider you choose. The HyperEVM foundation maintains official endpoints, but third-party providers such as QuickNode, Ankr, and Alchemy may also support the network. The Chain ID for HyperEVM is a numeric identifier that distinguishes it from Ethereum and other EVM chains; using the wrong Chain ID will cause transactions to fail or be rejected.

After entering the RPC endpoint and other details, save the network. Phantom Wallet will attempt to connect to the endpoint and verify basic functionality. If the connection fails, you will see an error message; common causes include a typo in the RPC URL, a provider outage, or the endpoint being deprecated. If you encounter an error, double-check the URL against the official HyperEVM documentation or your RPC provider’s dashboard. Some providers require an API key to be appended to the URL; ensure that any key is correctly included.

Once configured, Phantom Wallet will derive an EVM-compatible address on HyperEVM using the same Secp256k1 key that generates your Ethereum, Polygon, and Base addresses. This means that if you are already using the phantom wallet for Ethereum, your HyperEVM address will be identical to your Ethereum address from the same recovery phrase. This can be convenient for moving funds between chains, but it also means you should be careful not to send HyperEVM tokens to your Ethereum address on Ethereum mainnet, or vice versa, even though they look identical. The address format is the same; the blockchain they reside on is different.

Managing tokens and verifying network connectivity

After adding Sui and HyperEVM to your Phantom Wallet, the next step is ensuring that the wallet correctly displays and manages tokens on these networks. In the wallet’s main interface, you can see your balances across all networks in a unified portfolio view. When you switch to a specific network, Phantom displays only the tokens on that chain. If a token does not appear, you can add it manually by providing the token’s contract address or import a list of known tokens for that network.

On Sui, tokens are called “coin types” and are identified by their module and name, not a contract address in the traditional sense. When you add a custom Sui token to Phantom, you provide the coin type, which looks like a module path. Common tokens on Sui are pre-configured, including SUI (the native token), USDC, USDT, and others. When you add a token to your watchlist or portfolio, Phantom queries the RPC to fetch your current balance and displays it alongside your holdings on other networks.

HyperEVM tokens follow the ERC-20 standard, so adding them to Phantom Wallet works identically to adding tokens on Ethereum or Polygon. You provide the token’s contract address, and Phantom fetches the token’s name, symbol, and your balance. The wallet’s token list includes many popular ERC-20 tokens by default, but if you are using a lesser-known token, you may need to add it manually. Verify the contract address against a trusted source such as the project’s official website or a block explorer to avoid accidentally adding a counterfeit or scam token.

Verifying network connectivity is simple but crucial. When you first load your Sui or HyperEVM portfolio, Phantom should display your balance and recent transactions without errors. If the balance shows as zero but you expect tokens, check that you are on the correct network and that the RPC endpoint is responding. You can test RPC connectivity by checking the block explorer for your address; if the explorer shows tokens but Phantom does not, the issue is likely a temporary RPC sync lag or a caching problem in the wallet. Refreshing the wallet or restarting the browser extension usually resolves this.

Sending and swapping tokens across networks

Once tokens are loaded and verified, sending them is straightforward. In Phantom Wallet, click “Send,” select the token, enter the recipient address, and confirm the transaction. The wallet will estimate the network fee and display it before you sign. On Sui, fees are typically very low—often less than a cent for a simple token transfer. On HyperEVM, fees depend on network congestion, but they are generally lower than Ethereum mainnet. Always verify the recipient address carefully; if you are sending to an exchange or another wallet, confirm that the address is correct and that you are on the right network.

Phantom Wallet also includes a built-in swap feature, allowing you to exchange tokens within the same network or across chains. For instance, you could swap SUI for USDC on the Sui network, or swap ETH for a custom token on HyperEVM. The swap interface integrates with decentralized exchanges and liquidity providers, showing you the quoted output amount, price impact, and fees before you approve. Like any DEX trade, the actual output may differ slightly due to market movement between the time the quote is generated and the transaction settles.

When swapping across chains (for example, Sui to HyperEVM), the process is more complex because it involves a bridge. Phantom Wallet’s cross-chain swap may use an automated bridge service, which adds additional time and fees. Bridges themselves introduce execution risk: if the bridge service is slow or if liquidity is low for your pair, the swap may fail or produce worse pricing than expected. For large amounts, consider breaking the transfer into smaller test swaps first, or use a dedicated bridge application with more transparent fee structures and route information.

Security and recovery phrase management

The foundation of security for any Phantom Wallet configuration is the 12-word Secret Recovery Phrase. This phrase is generated when you first create a wallet, and it allows you to recover all accounts across all networks—Solana, Ethereum, Sui, HyperEVM, and any others you add—from any device running Phantom. The phrase must be stored securely offline, in a form that cannot be photographed, scanned, or accessed remotely. Writing it on paper, storing it in a physical safe, or using a hardware-backed seed storage device are appropriate methods. Never store it in a note-taking app, email, or cloud service, and never enter it on any website or into an unfamiliar application.

Because a single recovery phrase unlocks accounts across multiple blockchains, the security implications are multiplicative. If the phrase is compromised, an attacker can drain your Solana, Ethereum, Sui, and HyperEVM balances without needing separate passwords or phrases. This makes the recovery phrase more valuable to an attacker than a single-chain wallet’s phrase, and it demands even stricter protection. Consider using a passphrase addition (sometimes called a “25th word”) to add an extra layer of security; this is an optional feature in Phantom that extends the recovery phrase and generates different accounts if the base phrase is stolen.

For everyday use, Phantom Wallet also offers optional biometric authentication or PIN protection, which prevents casual access if your device is stolen. However, biometrics and PINs do not protect against a compromised recovery phrase. If your device is lost and the phrase is not secured separately, you will not be able to recover your funds. Conversely, if you lose your device but have the recovery phrase stored safely, you can reinstall Phantom on a new device, enter the phrase, and regain access to all your accounts.

When using Phantom Wallet with Sui, HyperEVM, or any network, avoid granting wallet permissions to unknown or suspicious decentralized applications. When you interact with a dApp, Phantom displays an approval window showing what permissions the app is requesting—for example, the ability to view your balance, initiate transactions, or access your public address. Approve only what is necessary for the dApp’s function. A seemingly innocuous permission to “view balance” is low-risk, but approving “full account access” or “unlimited spending” can expose you to wallet-draining scams if the dApp is malicious or compromised.

Troubleshooting common configuration issues

One frequent issue is an RPC endpoint becoming slow or unresponsive. If you notice that Phantom Wallet is taking longer than usual to load balances, show transaction history, or confirm transactions, the RPC provider may be experiencing congestion or downtime. The solution is to switch to a different RPC endpoint. Open Phantom’s network settings, edit the RPC URL for the affected network, and replace it with an endpoint from a different provider. Keep a short list of reliable RPC providers for each network you use, so you can quickly switch if one fails.

Another common problem is seeing your tokens on a block explorer but not in Phantom Wallet. This usually indicates a sync lag; Phantom Wallet queries the RPC to fetch your balance, and if the RPC is slightly behind the network, new tokens may not appear immediately. Refreshing the wallet, closing and reopening the browser extension, or waiting a few seconds often resolves this. If it persists, verify that you are viewing the correct address on the block explorer and that the tokens are actually on the network you think they are. A token sent to the wrong network address will never appear in Phantom until it is bridged back.

Transaction failures are another potential issue, particularly when sending from HyperEVM or swapping across chains. If a transaction is “pending” for an unusually long time, the RPC may be overloaded or the network may be congested. You can cancel the transaction by opening it in the wallet, finding a “Cancel” or “Replace” option, and submitting a new transaction with a higher gas price. For Sui, where gas is much cheaper, transaction failures are rarer, but if they do occur, they are usually due to an invalid recipient address or insufficient balance.

If you have imported a recovery phrase from another wallet into Phantom and notice that it generates different addresses for the same network, this may indicate a difference in derivation paths. Solana wallets, for example, can use different derivation standards. Phantom follows its own derivation convention, and a phrase imported from another Solana wallet may produce a different address in Phantom. This is not a bug; it is a result of wallet-specific design choices. If you need to access the same account from multiple wallets, check the original wallet’s derivation path setting or consult its documentation for guidance on importing into Phantom.