A user holding cryptocurrency across multiple blockchains faces a practical administrative problem at tax time. Solana, Ethereum, Bitcoin, Polygon, and other networks each generate transaction records, but no single authority aggregates them. When a Phantom wallet user swaps tokens, receives airdrops, stakes assets, or bridges funds between networks, each event may create a taxable event under relevant jurisdictions. The wallet itself stores only the cryptographic credentials to authorize transactions; the actual transaction history lives on distributed ledgers. Retrieving, organizing, and reconciling that history in time for tax filing requires deliberate planning.

Most cryptocurrency tax software accepts transaction data in standardized formats—CSV files, blockchain APIs, or integration through wallet interfaces. Phantom’s design as a self-custodial wallet gives the user complete ownership of account recovery phrases and private keys, which means Phantom cannot retrieve lost wallets or export historical data on the user’s behalf. Instead, tax preparation requires exporting transaction records directly from the blockchains supporting the accounts, cross-referencing trades within Phantom, and then importing that consolidated data into tax software. Understanding where the data originates, what information Phantom can surface, and how to fill gaps is essential for compliance.

What Phantom records and what you must record yourself

Phantom’s portfolio view shows the current balance of cryptocurrency assets and NFTs across supported blockchains, but the wallet does not retain a centralized ledger of historical transactions. When you send, receive, or token swap through the wallet interface, Phantom signs the transaction using your private keys and broadcasts it to the respective blockchain—Solana, Ethereum, Polygon, Base, Bitcoin, Sui, or HyperEVM. Once recorded on that blockchain, the transaction is immutable and visible to anyone querying that network. Phantom can display transaction details for events you have performed in the current session, but it does not maintain a permanent internal archive of all activity across all networks you have ever used.

The consequence is that accurate tax reporting depends on extracting data from blockchain explorers, transaction APIs, or integrated services that specialize in historical record retrieval. If you created accounts on Solana and Ethereum within the same Phantom wallet, you need to pull transaction records from both chains separately. Similarly, if you have used Phantom across iOS, Android, and browser extension versions, the same wallet can exist on multiple devices—and transactions initiated from any device are recorded on the blockchain, not stored locally within a single device’s Phantom installation.

Phantom’s ability to connect to decentralized applications (dapps) for trading, lending, and liquidity provision complicates the picture further. When you swap tokens directly through Phantom’s integrated swap feature, the wallet records the transaction hash and can sometimes display the input and output amounts. However, when you connect Phantom to an external dapp such as a decentralized exchange (DEX), lending protocol, or yield farm, Phantom is signing your transaction but not independently logging the details. The dapp itself may maintain better records, but Phantom’s internal history will show only the blockchain confirmation, not necessarily the context or counterparty involved.

For tax purposes, this distinction matters. A straightforward send or receive is usually clear from blockchain data. A token swap shows two transfers—one out, one in—but may require reference to the swap instruction or DEX event log to confirm the exact rate, fees, and any slippage incurred. Staking rewards, airdropped tokens, yield farming APY, and other complex events are even less transparent from chain data alone. You may need to reference the yield protocol, exchange FAQ, or original announcement to establish the fair market value and timing of acquisition for tax reporting.

Organizing Phantom transactions by blockchain and account

The first practical step is to identify every blockchain and account you have used with Phantom. If your Phantom wallet was created with a Secret Recovery Phrase, the same phrase generates a different account address on each blockchain network—Solana, Ethereum, Polygon, and so on. You can derive multiple accounts from the same seed phrase within Phantom by using the account creation feature, which means a single recovery phrase could have Solana accounts numbered 1 through 5, Bitcoin addresses, and Ethereum accounts simultaneously active.

Document each account address you control, organized by blockchain. For Solana, your address begins with a letter or number and is typically 44 characters long. For Ethereum and Polygon, addresses are 42 characters beginning with “0x”. Bitcoin addresses vary in format depending on whether they are legacy, segwit, or native segwit. Sui uses bech32 format. Having a list of accounts prevents accidental omission and helps you cross-check that you have retrieved all relevant transaction history before filing.

Once you have your account list, export transaction history from a blockchain explorer or API service for each account and network. Services such as Solscan (for Solana), Etherscan (for Ethereum and most EVM chains), and Blockchain.com (for Bitcoin) allow you to paste an account address and download a CSV file of all transactions. Some explorers offer direct CSV export; others require you to copy transaction data and paste it into a spreadsheet. If you have performed thousands of transactions, direct API access through a tax-focused service may be faster and more reliable than manual export.

The goal is to create a master spreadsheet or import into tax software with columns for date, transaction hash, sender address, recipient address, token or asset moved, amount, and blockchain network. This gives you the raw material to identify which transactions are taxable events—sales, swaps, airdrops, mining rewards, staking income, or other gains.

Identifying taxable events within token swaps and complex transactions

A straightforward send of one asset to another address is usually not a taxable event if you are simply moving your own funds between wallets. A send to someone else represents a donation (potentially taxable in some jurisdictions) or a payment, with no capital gain unless the asset has appreciated since acquisition. A receive is typically not taxable at the time of receipt, though you must record the fair market value at that moment and the transaction date for later capital gains calculations.

A token swap, by contrast, is a taxable event in most jurisdictions. When you exchange one asset for another through Phantom’s integrated swap or through a DEX, you are disposing of the asset you sent and acquiring the asset you received. For tax purposes, you must calculate the fair market value of both the asset sent and the asset received on the date of the swap, determine your cost basis (the price you originally paid for the asset you sent), and calculate the capital gain or loss. If you sold at a profit, you owe tax on that gain. If you sold at a loss, you may be able to claim a capital loss.

Airdropped tokens are treated as ordinary income in most jurisdictions at the fair market value on the date of receipt. A staking reward earned through Phantom or an external staking protocol is also ordinary income. If you received 100 SOL in staking rewards when SOL was worth $150 per token, your ordinary income was $15,000, and your cost basis for those 100 SOL is $150 each. Later, if you sell that SOL for $200, your capital gain is $50 per token, or $5,000 total.

Some complex transactions blur these categories. A deposit into a liquidity pool, withdrawal from a liquidity pool, or redemption of wrapped or derivative tokens requires careful analysis. Phantom’s portfolio view may show your LP tokens or staking derivatives, but the tax treatment depends on the specific protocol. A loss of temporary price exposure (impermanent loss) may not be deductible. A redemption of wrapped tokens may trigger capital gains on the underlying asset. Consulting tax software documentation or a tax professional for your jurisdiction helps clarify how to categorize these events correctly.

Filling gaps between Phantom’s view and blockchain reality

Blockchain explorers show transfers and function calls, but they do not always display the economic context. For example, if you swapped 1 SOL for USDC through a DEX, the explorer shows two transfers: SOL leaving your address and USDC arriving at your address. The explorer may not show the price at which that exchange occurred or which DEX routed the trade. Phantom’s transaction history or swap interface usually displays the expected output and any fees, but if you are reviewing tax data months later, you may need to reconstruct that information.

Similarly, complex contract interactions—bridging assets between blockchains, wrapping or unwrapping tokens, or using advanced strategies like arbitrage or leverage—may show up as multiple transactions across different networks. A bridge from Ethereum to Solana might involve a burn on Ethereum and a mint on Solana, appearing as two separate transactions to a casual observer. Phantom’s UI may show these as a single operation, but a tax software import might see them as two events. You must reconcile these to ensure the software does not double-count a gain or loss.

The fair market value of each asset at the time of transaction is also your responsibility. If you swapped a less-common token for a major asset like ETH or SOL, blockchain explorers can help you identify the date and cross-reference a historical price from a major exchange or price oracle. If you swapped between two obscure tokens, you may need to check the liquidity pool ratio or historical price data from the dapp itself to estimate fair market value. Some tax software can pull historical prices automatically for major assets; for lesser-known tokens, you may need to enter the price manually or find contemporaneous quotes.

One critical area where Phantom’s view and blockchain data can diverge is gas fees and transaction costs. If you sent assets on Ethereum or Polygon, you paid gas fees that reduced your overall balance but do not show as a separate line item in a simple transaction export. Those fees may be deductible as transaction costs or capital loss, depending on your jurisdiction and tax treatment. Blockchain explorers usually show the gas fee in the transaction details, but tax software may require you to manually add them to the transaction record.

Integration with tax software and the export workflow

Most mainstream cryptocurrency tax software—including Koinly, CoinTracker, Zenledger, and TaxBit—accepts CSV imports of transaction history. The typical workflow is to export your transaction data from blockchain explorers, clean and standardize the format to match the tax software’s expected input, and then import the file. Many tax software platforms also accept direct API connections to blockchain explorers or wallet services, which can automate the export process if you choose to integrate them.

The advantage of using a tax software platform over a spreadsheet is that the software can match trades, calculate cost basis using your chosen accounting method (FIFO, LIFO, or average cost), and generate reports that align with your country’s tax filing requirements. A US filer using FIFO accounting, for example, will sell the oldest units first; using average cost will instead average the purchase price of all units held. The choice affects the capital gain or loss reported. Tax software lets you select these methods and recalculate if you need to adjust your approach.

When you import transaction data, begin with a small test. Import a month or two of data and verify that the software correctly categorized each transaction type, matched buy and sell orders, and calculated gains as expected. Check that the import recognized token names and prices correctly; if a lesser-known token was misidentified, correct it before importing the entire history. Once you have verified the process, import the full dataset. Then review the summary report for anomalies—a very large gain on a single trade, a missing transaction you know occurred, or a duplicate entry. These manual reviews catch errors before tax filing.

If you used Phantom to cryptocurrency management across multiple wallets or devices, ensure that the tax software is not double-counting activity. If you moved funds between two of your own Phantom wallets or imported a recovery phrase into Phantom on a new device, these are internal transfers that should not be taxable events. Tax software that pulls from multiple wallet addresses or sources might misinterpret such transfers as income or trades, so you need to mark them as transfers or exclude them from taxable income.

Documentation and audit readiness

Tax authorities in the US, UK, and many other jurisdictions can request documentation of cryptocurrency transactions. A clean record showing transaction hash, date, amount, fair market value at the time, and the source of that valuation provides evidence that you made a good-faith attempt at accurate reporting. If you calculated capital gains using historical price data from a major exchange, document which source you used. If you estimated the value of an airdrop based on initial DEX offerings or price feeds, document your methodology.

Keep a separate backup of your transaction exports and tax software output. If you need to download phantom extension again or recover your wallet using your Secret Recovery Phrase, you may not have immediate access to historical transaction records from that point forward. A local copy of exported CSV files and your tax software report ensures you can reconstruct your reporting in case of device loss, browser data clearing, or other incidents.

A systematic approach also simplifies future years. If you establish a routine—exporting transactions quarterly, updating your tax software as you go, and reconciling before year-end—you avoid the rushed scramble to retrieve months of forgotten transactions in March or April. Phantom’s ability to manage crypto assets across multiple blockchains is a strength for portfolio diversification, but it also fragments your transaction history across several networks. Treating tax reporting as an ongoing process rather than a year-end task prevents errors and reduces audit risk.

Common pitfalls and how to avoid them

One frequent mistake is underestimating the number of taxable events. Users often remember large trades but forget small swaps, received tokens, or yield farming transactions. A comprehensive export from blockchain explorers catches these because it includes every on-chain activity, not just the trades you consider significant. If you cannot recall a transaction when reviewing the list, check the transaction hash on a blockchain explorer to understand what happened and why.

Another pitfall is assuming that because you lost money on an overall portfolio basis, you have no capital gains to report. A user might have bought 10 ETH at $3,000, sold 5 at $2,500 (realizing a loss), bought 5 more at $2,000, and sold them at $2,800 (realizing a gain). Even though the overall portfolio is down, the second sale produced a taxable capital gain that must be reported. Each transaction is evaluated individually; unrealized losses on assets you still hold do not offset realized gains on assets you sold.

Using Phantom on multiple devices without reconciling accounts creates another risk. If you have imported your recovery phrase into Phantom on both an iPhone and a browser extension, both instances control the same accounts and can see transactions initiated from either device. However, if you export transaction history from Phantom on the iPhone and from the browser separately, you might not be aware that one export is missing a swap you initiated from the other device. The blockchain always shows the complete picture, so exporting directly from blockchain explorers rather than relying solely on Phantom’s local history avoids this.

Finally, tax law for cryptocurrency varies significantly by jurisdiction and changes frequently. A transaction treated as a sale in the US may be treated as a currency conversion in another country. Staking rewards might be taxed immediately in one jurisdiction and deferred until sold in another. Some jurisdictions have specific guidance for NFTs, airdrops, and DeFi yield; others do not. Before finalizing your tax report, verify the current rules in your jurisdiction or consult a tax professional who specializes in cryptocurrency. Phantom’s role is to give you control over your crypto assets; your responsibility is ensuring you report them correctly to the authorities that tax you.