A tax preparer receives a client’s list of wallet addresses and is asked to reconstruct a complete year of cryptocurrency activity for Form 8949 and Schedule D. The client has used Rabby Wallet across multiple EVM chains—Ethereum, Polygon, Arbitrum, and others—for DeFi swaps, token purchases, NFT sales, and staking rewards. The address history exists on chain, readable by anyone, but extracting it into a format suitable for tax calculation requires methodical work. Rabby Wallet itself does not generate an official tax export, but the wallet’s transparency and transaction visibility create a usable starting point for professionals who understand what data exists and how to retrieve it systematically.

The challenge is not whether transaction records exist; all on-chain activity is immutable and observable. The challenge is organizing those records into a coherent report that reflects the client’s actual cost basis, realized gains and losses, and holdings at year-end. A self-custodial wallet like Rabby puts that responsibility on the account holder and their advisor. The wallet does not maintain custody of funds, apply tax rules, or calculate gain and loss automatically. It does provide transaction interpretation and balance visibility that can serve as the foundation for accurate tax reporting. Understanding how to extract, validate, and structure that data is essential for any tax professional working with crypto clients.

Understanding Rabby Wallet’s role in transaction sourcing

Rabby Wallet is a self-custodial, open-source cryptocurrency and NFT wallet optimized for Ethereum and EVM-compatible networks. As a browser extension available on Chrome, Brave, Edge, and other Chromium-based browsers, it provides users direct visibility into their on-chain activity without relying on a centralized custodian to maintain transaction records. When a client uses Rabby to interact with DeFi protocols, approve token transfers, or conduct NFT trades, every action generates a transaction recorded on the blockchain itself. The wallet’s interface displays historical activity, current balances, and transaction details, but it is not a tax-reporting tool. For a tax professional, that distinction is critical: Rabby shows what happened, but the preparer must interpret it and calculate the tax consequence.

The wallet’s transaction interpretation feature displays expected balance changes before signing, which helps users understand what a transaction will do. For tax purposes, this same clarity is essential. A swap that appears as a single transaction on the wallet interface often involves multiple components: approval, pool interaction, slippage, and fee deduction. The actual tax events may include a taxable exchange at fair market value, a gain or loss realized at that moment, and a separate record of the resulting token holdings. Rabby’s ability to show the transaction in detail—inputs, outputs, gas cost, and counterparty—supports accurate reconstruction, but the preparer must still map each event to the correct tax treatment.

The wallet is free to use, though blockchain transactions incur network gas fees paid to the respective networks. Critically, Rabby requires users to download from the official rabby.io domain or verified app stores to avoid fake versions and malware. A compromised wallet or a phishing site claiming to be Rabby could provide false transaction data, undermine the client’s security, or result in theft of funds. For tax work, this means validating the source of the wallet and the data before accepting it as authoritative. A client should be able to demonstrate that they used the legitimate Rabby Wallet, not an imitation.

Extracting transaction history from Rabby for multiple EVM chains

Rabby Wallet supports multiple EVM chains—Ethereum mainnet, Polygon, Arbitrum, Optimism, Base, and others—in a single interface. A single address on Rabby can hold balances and conduct transactions across these networks simultaneously. For tax reporting, this creates both an opportunity and a challenge. The opportunity is that all activity across these chains can be reviewed in one wallet application. The challenge is ensuring that every chain is included in the tax report and that transactions are not accidentally duplicated or misattributed to the wrong blockchain.

The first step in data extraction is to identify all addresses controlled by the client through Rabby. The wallet may have imported a single seed phrase controlling multiple derived addresses, imported hardware wallet accounts, or added watch-only addresses. Tax treatment depends on actual ownership, so only addresses where the client controlled the private key or had signing authority should be included in the tax calculation. A watch-only address added for reference does not generate reportable gain or loss merely because assets were observed; it should be excluded unless the client actually transferred funds to or from it. The preparer should ask the client to provide a complete list of all addresses they consider part of their tax position, then verify which ones appear in Rabby as active accounts.

Once addresses are confirmed, the preparer should export transaction history for each address on each supported blockchain. Rabby does not have a built-in “export to CSV” feature within the wallet application itself, so the primary method is using blockchain explorers. A preparer can visit Etherscan for Ethereum, Polygonscan for Polygon, Arbiscan for Arbitrum, and similar explorers for other chains. By searching for the client’s address on the appropriate explorer, the preparer can view the complete transaction history and often export it to a spreadsheet format. This method is reliable because the explorer is querying the immutable blockchain, not relying on the wallet to report what happened. The downside is that explorers display raw blockchain data, not interpreted information. A token swap might appear as two separate token transfer events, and the explorer will not automatically calculate the fair market value at the time of the swap or determine the cost basis against current holdings.

The preparer should download the transaction data for each address and chain separately, then consolidate into a single timeline. It is common for clients to conduct activity on multiple networks within the same tax year, sometimes on the same day. Sorting the entire dataset by timestamp before performing tax calculations is essential to avoid attributing gains and losses to the wrong tax year or mismatching purchase and sale events.

Mapping Rabby transaction types to tax events

Not every on-chain transaction is a taxable event, and some transactions generate multiple taxable events. A tax professional must interpret raw transaction data through the lens of tax rules. A simple token transfer to another wallet is usually not taxable in itself; it is merely movement of funds already owned. A token swap, by contrast, involves a sale of one asset at its fair market value at the moment of the swap and a purchase of another asset at that same moment. Gas fees paid in the native token (ETH, POL, ARB) are typically capitalized into the cost basis of the asset acquired, or treated as an expense depending on the nature of the transaction and the applicable tax authority’s guidance.

Rabby’s transaction interpretation feature helps identify these events. When the preparer reviews a transaction in Rabby before extracting data, the wallet displays what changed: “You will receive 5 USDC” or “Your balance will decrease by 1 ETH and increase by 100 DAI.” This interpretation is essential for distinguishing between movements, exchanges, and other activity. The preparer should document the event type for each transaction: Is it a purchase (fiat-to-crypto or token-to-token acquisition with known cost basis)? A sale (crypto-to-fiat or token-to-token disposition)? A transfer (no taxable event)? A reward (staking, airdrop, or other receipt of new tokens)? A loss or expense (gas paid, slippage, failed transaction)? Once categorized, each event can be assigned the appropriate cost basis method and fair market value calculation.

Staking rewards, airdrops, and other token distributions received through Rabby-connected addresses are taxable income at the fair market value on the date of receipt. If the client received 10 UNI tokens through an airdrop, that is a purchase of UNI at fair market value on the airdrop date, not a cost-free asset. The preparer must identify the date and the closing price or exchange rate for that token on that specific date. Because cryptocurrency markets trade around the clock across global exchanges, “fair market value” requires a defined standard. Many preparers use the price at midnight UTC, the New York closing time, or the average of prices from major exchanges. The key is consistency: once a method is chosen, apply it uniformly across all transactions.

For DeFi activity visible through Rabby—swaps, liquidity provision, governance participation—the tax treatment can be complex. A swap of Token A for Token B is a sale of A and a purchase of B. If the client provided liquidity to a pool and received LP tokens in return, that is typically a capital purchase at fair market value of the tokens contributed. When the LP tokens are withdrawn, there may be a gain or loss depending on the value of the underlying assets at withdrawal time, plus a separate calculation of any yield or impermanent loss. Some jurisdictions treat liquidity provision as a single taxable exchange; others recognize separate events for initial deposit, yield accrual, and withdrawal. The preparer must apply the client’s jurisdiction’s rules and document the method chosen.

Validating data integrity and avoiding common extraction errors

A transaction downloaded from a blockchain explorer is authoritative for on-chain activity, but it can be incomplete or misunderstood. The preparer should perform several validation checks before using exported data in a tax calculation. First, verify that the transaction list is complete. Check the address on the explorer for the total number of transactions, and confirm that the exported data includes all of them. Some explorers may paginate results or limit exports, and the preparer should not assume the file is complete without checking.

Second, cross-reference Rabby Wallet data with the explorer data. The blockchain wallet should display some of the same transactions visible on the explorer. By sampling a few transactions in both places, the preparer can confirm that they are using the correct address and that there are no discrepancies between what Rabby shows and what the explorer shows. This is a basic sanity check: if Rabby and the explorer disagree on a transaction’s details, the preparer should investigate before proceeding.

Third, reconcile the final balances. After calculating all purchases and sales, the resulting inventory should match the current holdings shown in Rabby Wallet. If the client holds 50 ETH according to Rabby but the preparer’s calculation shows 49 ETH, there is an error in the extraction or reconciliation. Common causes include missing transactions (especially early purchases or transfers), transactions on networks that were overlooked, or duplicate entries. Work backward from the current balance to identify discrepancies. If a transaction was missed, it must be found and included. If there is a duplicate, it must be identified and removed from the export.

Fourth, verify fair market value sources. For major cryptocurrencies like Bitcoin, Ethereum, and stablecoins, prices are widely available from multiple exchanges and data providers. For less liquid or newer tokens, price data may be sparse or unreliable. The preparer should document the source of every price used—for example, “Coinbase closing price at 2024-01-15 20:00 UTC for 1 ETH = $2,234.50″—and retain that documentation. If a token was received from an airdrop or a DeFi protocol reward and no reliable price is available, the preparer should note that limitation and, if required by the jurisdiction’s rules, consult with the client about available evidence or reasonable valuation methods.

Organizing data for client communication and compliance

A client providing a wallet to a preparer for tax work should expect clear communication about what data was extracted, what assumptions were applied, and what information is still needed. The preparer should prepare a summary document that lists all addresses analyzed, all blockchain networks included, the date range covered, and the total number of transactions reviewed. This summary serves as a roadmap for both the preparer and the client to confirm that the scope is complete before tax calculations are finalized.

The organized transaction list should include columns for date, transaction hash (the unique identifier on the blockchain), asset type (ETH, USDC, DAI, etc.), quantity, fair market value at the time, total value in USD or the reporting currency, transaction type (purchase, sale, transfer, fee, etc.), and notes explaining the event. This structure is standard in tax accounting and allows the preparer to sort, filter, and aggregate transactions for tax schedule preparation. If a transaction was difficult to interpret—for example, a complex DeFi interaction that resulted in multiple simultaneous events—the notes column should explain how it was treated and why.

Before finalizing the tax report, the preparer should review the entire transaction history with the client. Many clients assume that their wallet application has already done the tax work, so they may not have reviewed transactions manually or verified that all activity is accounted for. Walking through the list of major transactions—especially large purchases, significant gains, year-end holdings—creates an opportunity to catch missing information, confirm cost basis for purchases that lacked documentation, and identify any transactions the client did not intend to include. This conversation is also an opportunity to educate the client about why certain movements trigger tax events and others do not, setting expectations for future years.

Handling complex or ambiguous transactions in Rabby activity

Some transactions recorded in Rabby or on the blockchain are inherently ambiguous. A failed transaction that consumed gas but did not transfer assets is still a blockchain event and still cost the client money. In most jurisdictions, the gas fee is a deductible business expense or a capitalized cost depending on the nature of the failed transaction. The preparer should identify these events and document the treatment chosen. Similarly, a transaction with unusual complexity—such as a flash loan used for arbitrage, or a contract interaction that resulted in an unexpected token transfer—may require additional research to understand what actually occurred and why.

Flash loans and atomic swaps are increasingly common in DeFi. A flash loan involves borrowing and repaying assets within a single transaction, with the borrowed amount never actually under the user’s control. If a client used a flash loan to facilitate an arbitrage, the preparer should understand that the loan itself is not a taxable event (since it was repaid in the same transaction), but the gain from the arbitrage is taxable. Rabby Wallet’s transaction interpretation can help clarify what the net effect was, but the preparer may need to review the underlying smart contract interaction to be certain.

Another common scenario is received tokens of uncertain origin or value. An airdrop of a new token, a distribution from a governance contract, or a surprise token sent by a third party creates a record in Rabby that the client received something of value. The preparer must determine whether the token can be valued reliably, when it was received, and whether the client took any action to cause or encourage its receipt (which might affect tax treatment). If a token has no trading history or fair market value cannot be established, the preparer should document that limitation and discuss options with the client: treating it as worthless, using a cost basis of zero, requesting revised guidance, or obtaining a professional valuation.

Selecting and documenting the cost basis method

Cryptocurrency tax reporting requires a cost basis method: the rule used to match sales against purchases and determine gain or loss. The most common methods are first-in-first-out (FIFO), last-in-first-out (LIFO), average cost, and specific identification. Different jurisdictions allow different methods, and the choice can significantly affect the tax bill. A preparer must determine which method applies in the client’s jurisdiction and confirm that the method is applied consistently across the tax year.

FIFO is the simplest and most commonly accepted: the oldest purchased tokens are assumed to be sold first. If a client bought 10 ETH on January 1 at $2,000 and 10 ETH on December 1 at $3,000, then sold 15 ETH on December 15, the sale is assumed to be the 10 from January plus 5 from December. The gain is calculated against those specific cost bases. The preparer should apply this method consistently across all token types and all transactions within the tax year.

Specific identification requires the client (or the preparer on their behalf) to explicitly identify which tokens were sold in each transaction. This method offers the most control and can minimize taxes if some token purchases have much higher cost basis than others. However, it requires detailed record-keeping and explicit intent documented at the time of sale. Many cryptocurrency users do not maintain this level of documentation, so the preparer must decide whether to reconstruct specific identification retroactively (which some jurisdictions allow and others do not) or default to FIFO.

Once a method is chosen, the preparer should document it in the tax file and apply it uniformly. If the jurisdiction allows the client to elect a method for the first time in a subsequent year, the preparer should inform the client of that option and any tax consequences of changing methods. For clients managing significant cryptocurrency activity, consistency in method and documentation across years simplifies future audits and reduces the risk of penalties for inconsistency.

Building a sustainable workflow for recurring crypto tax clients

A preparer working with clients who use Rabby Wallet or similar self-custodial wallets should establish a repeatable process. Each year, request that the client provide a complete list of all addresses, confirmation of which addresses are new or no longer active, and notification of any major transactions the preparer should be aware of. Provide a template for the client to fill out, reducing back-and-forth communication.

Maintain a file for each client that records the addresses, blockchain networks covered, and the cost basis method applied. This documentation is essential if the tax return is audited: the preparer must demonstrate that the calculation was systematic and applied consistent rules. Blockchain explorers and wallet data are permanent records, so the preparer can always reconstruct the analysis if needed, but having contemporaneous notes explaining decisions significantly strengthens the position.

Consider investing in a cryptocurrency tax software platform designed for preparers. Tools like CoinTracker, Koinly, or similar services integrate with blockchain explorers and can automate much of the data extraction and reconciliation work. These platforms are not substitutes for professional judgment—they still require the preparer to review transactions, verify cost basis, and apply the correct tax rules—but they reduce manual data entry and support audit trails. Many of these platforms also generate tax reports in standard formats, saving time when preparing Form 8949 or equivalent schedules.

When setting up a new cryptocurrency client, conduct an onboarding call to understand their activity level, asset types, and jurisdiction. Many clients switch to Rabby Wallet or other self-custodial options after years of using exchange accounts, so there may be historical activity outside the wallet that must also be included. Ask whether the client conducted any activity on centralized exchanges, other wallets, or DeFi protocols outside Rabby. If so, request access to those records as well. The goal is to capture the client’s complete cryptocurrency tax position, not just what is visible through one wallet application. To download Rabby Wallet and ensure the client is using the legitimate application, direct them to the official installation page at sites.google.com/rabby-wallet-extension.com/rabby-extension-download, and verify that they have installed it only after confirming the source.