A cryptocurrency user trades tokens, swaps assets, and stakes on decentralized protocols throughout the year, then faces a practical problem: their accountant or tax software requires transaction history in a specific format, with clear timestamps, amounts, cost basis, and counterparty information. Rabby Wallet, a self-custodial blockchain wallet designed for Ethereum and EVM-compatible networks, records every interaction on-chain, but retrieving that data in a form an accountant will accept requires understanding both what the wallet captures and what tax systems expect.
The gap between on-chain activity and tax-compliant reporting is significant. A single token swap on Uniswap generates a transaction record visible on the blockchain, but that record may not include the user’s cost basis for the token sold, the precise moment of fair-market value at settlement, or the correct treatment under applicable tax law. Rabby Wallet’s transaction history display, risk alerts, and balance previews help users understand what they are signing before they approve it. None of those features, however, automatically generate a tax report. The compliance process requires deliberate extraction, verification, and often manual augmentation of exported data.
Tax authorities in most jurisdictions treat cryptocurrency transactions as taxable events. A purchase, sale, swap, staking reward, airdrop, and sometimes even movement between wallets can trigger a reporting obligation. The IRS in the United States, HMRC in the United Kingdom, and comparable agencies in other countries have issued guidance making clear that failure to report these events can result in substantial penalties and interest, regardless of whether the gains were realized in fiat currency.
Rabby Wallet records cryptocurrency management activities on the Ethereum blockchain and EVM-compatible networks, creating an immutable ledger. That ledger, however, is visible only to the wallet user and anyone with access to the relevant blockchain explorers—and blockchain explorers do not organize data by tax lot, cost basis, or jurisdictional treatment. A user who conducted 200 transactions across multiple protocols, networks, and counterparties during a tax year cannot simply provide their accountant with a blockchain address and expect a compliant tax return. The wallet activity must be extracted, organized, and reconciled against the user’s intentions and the applicable tax law.
The audit trail must include not only successful transactions but also failed attempts, partial fills, and reversals. If a token swap was reverted by the user or the protocol, it may still appear on the blockchain until the data is carefully filtered. Staking rewards, delegation changes, and flash loans are separate events with different tax treatments. A comprehensive export from Rabby Wallet becomes the foundation for all downstream compliance work, making the accuracy of that export a direct control on tax risk.
Rabby Wallet’s transaction history is accessible through the wallet interface on browser extension, mobile app (Android), or desktop application. Most commonly, users access the activity log through the desktop or browser extension version, which displays a chronological list of on-chain interactions. The wallet shows the transaction hash, timestamp in UTC, network name, method (swap, transfer, approval, staking, etc.), and a summary of balance changes.
To begin the export process, a user should navigate to the activity or transaction history section within Rabby and ensure all networks used during the tax year are included. Because Rabby can recognize and automatically switch between EVM networks without manual configuration, a user may have conducted transactions on Ethereum mainnet, Arbitrum, Optimism, Polygon, or other chains without deliberately selecting them. This automatic network detection is convenient for operations but requires the user to verify that the export captures activity from all chains, not only the primary Ethereum network.
The wallet interface typically allows filtering by date range, network, and transaction status. A user preparing a year-end export should set the date range to include the full tax year plus any transactions from the prior year that may affect wash-sale calculations or cost-basis averaging. All networks used should be included. Failed transactions should be reviewed separately to determine whether they resulted in any cost (gas fees paid but no token movement) or were successfully reversed.
Once the transaction list is visible, the data can be exported by copying the relevant fields into a spreadsheet or using the wallet’s built-in export feature if available. Manual copying is tedious but forces verification; the user sees each transaction and can flag unusual entries for clarification. More automated exports may miss context that an accountant will require, such as whether a transaction was deliberate or accidental, whether gas fees should be capitalized or expensed, or whether particular transactions were test transactions using small amounts.
Tax software and accountants expect a standardized set of information for each transaction. The first essential field is the transaction date and time, ideally in UTC to avoid ambiguity. Rabby Wallet displays timestamps for all on-chain activity, providing this baseline. The second field is the transaction type: purchase, sale, swap, transfer, staking reward, airdrop, gift, loan repayment, or other. This classification determines the tax treatment and often requires human judgment beyond what the wallet can automatically infer.
The third field is the asset sent: the token name, ticker, quantity in the smallest unit (wei for Ethereum), and fair-market value in a local currency at the time of the transaction. The fourth is the asset received, with the same detail. For a token swap, the wallet shows both the input and output, but the fair-market value for the received asset must be obtained from a price oracle or exchange rate service at the moment of settlement, not at some later time.
The fifth field is the transaction cost: gas fees paid in ETH or the network’s native asset, converted to the reporting currency. Gas fees may be capitalized as part of the cost basis of a purchased asset, or treated as a separate expense, depending on jurisdiction and the user’s accounting method. Rabby displays gas costs in the transaction details, but a user must ensure they are recorded in the same currency as the rest of the report.
Additional fields often required are the counterparty or protocol (Uniswap, Aave, OpenSea, etc.), the transaction hash for blockchain verification, the wallet address or account ID for cross-referencing, and a note or description field. If the transaction was a transfer between the user’s own wallets, that relationship should be documented to avoid double-counting as a sale. If it was a gift, the recipient’s information may be required for gift tax purposes in some jurisdictions.
Popular tax software for cryptocurrency, such as Koinly, CoinTracker, or TokenTax, accepts data imports in CSV, Excel, or API formats. Each platform has specific field requirements and often enforces a particular column order. After exporting from Rabby Wallet, a user should review the software’s import template, then map the wallet export columns to the tax software’s expected format. A mismatch in column headers, date format, or number precision can cause import failures or incorrect calculations.
Many tax software platforms also allow direct API connections to wallets or blockchain explorers, reducing manual export steps. However, such integrations may not be available for all EVM networks or may have limitations on historical data retrieval. A user should verify that their chosen tax software supports the specific EVM chains they used during the tax year—for example, not all platforms have deep support for Arbitrum, Optimism, or Polygon. If an API integration exists, comparing the automatically imported data against the manually exported Rabby history is a critical verification step.
Cost basis calculation is often the most complex part of reconciliation. Rabby Wallet does not track cost basis; it only records on-chain events. If a user purchased tokens on an exchange, transferred them to Rabby, then swapped them, the tax software must align the transfer event (which shows movement but no price) with the prior purchase (which established the cost basis). This alignment requires either linking the exchange export to the wallet export or manually entering historical purchase prices. Missing cost basis data is a leading cause of incorrect tax calculations and subsequent audit risk.
A cryptocurrency user often holds assets across multiple wallets and multiple blockchain networks. Rabby Wallet supports Ethereum and EVM-compatible chains, covering most widely used networks, but it does not natively support Bitcoin or Solana. If a user conducted significant activity on non-EVM networks during the tax year, they must export that history from separate wallet applications and reconcile it into a single tax report.
When you perform a rabby wallet download and begin setting up multiple accounts or wallet addresses within the application, each account’s transaction history must be exported separately and then combined in the tax report. The consolidation process requires careful attention to avoid duplicating transfers between accounts or missing transactions that occurred before migration to Rabby.
A common scenario involves users who migrated from MetaMask or another wallet to Rabby Wallet. The new wallet does not automatically import historical transaction data from MetaMask; it only begins recording activity after installation. A user must export their complete MetaMask history separately, merge it with Rabby activity, then handle the transfer transaction (from MetaMask to Rabby) carefully so it is not counted as a sale or income event. This complexity is why many accountants recommend maintaining a master transaction log in a spreadsheet, updated throughout the year, rather than attempting to reconstruct the entire history at year-end.
Before submitting an exported transaction history to an accountant or tax software, the user should perform several verification steps. First, cross-check the total number of transactions exported against the wallet’s activity count or a blockchain explorer query for the address. A large discrepancy indicates missing or duplicate data.
Second, spot-check a sample of transactions by looking up the transaction hash on the relevant blockchain explorer. Confirm that the timestamp, assets, and amounts match what Rabby Wallet displays. If there are mismatches, the wallet display may be cached incorrectly or the export may have used stale data.
Third, sum the quantity and value of each token purchased versus the quantity and value sold or transferred. The net should align with the user’s current holdings in Rabby Wallet (adjusted for staking, airdrops, or burns). If the math does not reconcile, a transaction has been missed or misclassified.
Fourth, verify that all networks used during the tax year are represented. If Rabby Wallet’s automatic network recognition switched the user between chains without explicit action, some transactions might be on networks the user did not consciously consider. Querying each EVM network for the wallet address using a block explorer is the most reliable way to confirm completeness.
Finally, retain the supporting documentation: the blockchain transaction hash for each entry, the wallet address or addresses involved, any correspondence with the protocol or exchange regarding failed transactions, and contemporaneous notes on the economic intent of each transaction. If a transaction is later questioned in an audit, the ability to reproduce it on the blockchain and explain the business purpose or intent becomes critical.
The goal of exporting Rabby Wallet transaction history is not to produce a tax return directly but to feed accurate, complete data into a professional accounting or tax preparation process. Most accountants and tax professionals have specific requirements for how data should be organized, what fields are essential, and what supporting documentation they expect. Before beginning the export process, a user should contact their accountant and ask for a data template, import format, or checklist.
Some accountants prefer to receive raw blockchain data and perform their own analysis; others expect pre-organized CSV files with specific columns. Some require fair-market value conversions in the reporting currency; others will source current prices independently. Understanding these preferences in advance prevents rework and reduces the risk of missing or malformed data that a tax professional cannot use.
A well-designed cryptocurrency record-keeping system treats the Rabby Wallet export as one input among several. If a user also conducted transactions on centralized exchanges, received airdrops, participated in staking pools, or engaged in margin trading, each of those activities requires documentation from the relevant platform. The tax report is only as complete as the sum of all these exports and the reconciliation between them.
For users managing substantial cryptocurrency holdings or conducting frequent trading, maintaining a master transaction log throughout the year—rather than attempting a complete reconstruction at year-end—is far more efficient and accurate. Each month, a user can export Rabby Wallet activity, validate it, add cost basis information from exchange records or price oracles, and file it away. By the time the tax year ends, the data is already organized, verified, and ready for the accountant. This approach also captures the contemporaneous economic intent behind transactions, which can be important if the transaction is ever questioned.
One frequent error is exporting only transactions where the user received tokens, while omitting transfers where they sent tokens away. In Rabby Wallet, both send and receive activities appear in the transaction history, but some export methods or filters may inadvertently suppress one direction. A comprehensive export must include all transaction types, because sales, transfers, and even failed transactions have tax consequences.
Another mistake is conflating blockchain timestamp with local transaction time. Rabby Wallet displays timestamps in UTC, but a user in a different time zone may inadvertently convert those times or use them inconsistently. This matters because fair-market value prices are often tied to specific times of day, and using the wrong timestamp can select the wrong price for cost basis or gain calculation.
A third error is failing to account for gas fees. When a user swaps tokens on Uniswap, Rabby Wallet shows the swap transaction with its gas cost. But if the export strips out gas fees or if the user does not explicitly record the gas paid, the cost basis of the purchased asset becomes understated and the reported capital gain becomes overstated. This is a common source of disagreement in audits.
A fourth mistake is including test transactions or transactions that were reverted on the blockchain. If a user initiated a transaction, then cancelled it or the protocol reverted it, and the user paid gas fees but received no tokens, that transaction still requires documentation. Omitting it might make the numbers look better in the moment, but if an auditor runs their own blockchain query, the discrepancy becomes obvious and raises suspicion about the completeness of the user’s record.
Finally, users often fail to document the intent or context of unusual transactions. A large, one-time transfer between wallets might be a consolidation for organizational reasons, but without a note, the accountant might interpret it as a sale to an unknown counterparty. Similarly, if a user received an airdrop, the export from Rabby Wallet will show the incoming tokens, but without documentation of the airdrop announcement or the fair-market value at the moment of receipt, the taxable income is unclear. Adding a brief description field to the exported data eliminates most of these ambiguities.
No. Rabby Wallet records on-chain transactions but does not calculate cost basis, fair-market values, or tax liability. The user must export the transaction history and either provide it to a tax professional or import it into tax software designed for cryptocurrency. The exported data is the starting point for tax compliance, not a finished tax document.
Rabby Wallet recognizes many EVM networks automatically, so your activity may span Ethereum, Polygon, Arbitrum, Optimism, and others. When exporting, ensure that your transaction history includes all networks used. Use a block explorer to query your wallet address on each EVM chain you touched during the year to verify that the export is complete.
Many popular tax platforms accept CSV or Excel imports and can connect to blockchain explorers or wallet APIs. Before you rabby wallet download or export your data, contact your tax software or accountant to request their preferred import format and template. This ensures that your exported data will map correctly to their system without manual adjustment.
Gas fees paid for transactions should be recorded as part of the transaction cost. Depending on jurisdiction and accounting method, gas fees can be capitalized as part of the cost basis of a purchased asset or deducted as a transaction expense. Verify with your accountant or tax software how they treat gas fees, then ensure that your Rabby Wallet export includes these amounts separately so they can be allocated correctly.

