Not tax advice. This article explains technical workflows only. Crypto tax law varies by jurisdiction and changes frequently. Consult a qualified CPA or tax professional for advice specific to your situation.
It's April and you need to file. Here's what Zelcore gives you to work with — and what it doesn't.
Zelcore is a self-custody wallet supporting 80+ blockchains. That breadth is its strength. It's also why tax season requires a bit of preparation: as of April 2026, Zelcore does not offer a native transaction history CSV export. There is no download button, no built-in tax report. What Zelcore does give you is full ownership of your addresses — and every transaction you've ever made is sitting on-chain, readable by any address-aware tool.
This guide walks you through the practical workflow: collect your addresses, import them into a multi-chain tax tool, classify each event correctly, and generate the output your filing software needs.
Before you start
What you'll need:
- Every public wallet address you used in Zelcore during the tax year (one per chain, per account)
- Approximate dates of your first and last transactions per chain
- Any exchange accounts you connected to Zelcore or used separately
- Access to a crypto tax platform (see below)
Estimated time: 30–90 minutes depending on how many chains and accounts you hold. If you've been actively swapping crypto assets in Zelcore, budget extra time — swaps are the most tax-heavy event class and each one requires its own cost-basis entry.
If you haven't already mapped your full portfolio, review tracking your multi-chain portfolio in Zelcore first — that workflow shows how to locate every address across your Zelcore accounts before you start pulling data.
Step 1 — Collect your public addresses
In Zelcore, navigate to each coin you hold and copy the receive address. You need one address per chain per account — not per asset. For example, your Ethereum address covers all ERC-20 tokens held at that address.
Common chains to check:
- Bitcoin, Litecoin, Bitcoin Cash (UTXO chains — one address per account, though HD wallets generate many)
- Ethereum and all EVM chains: Polygon, Arbitrum, Avalanche, BNB Smart Chain, Optimism
- Solana, Cardano, Cosmos, and any other Layer 1s you've used
For HD wallets (Bitcoin in particular), you may have hundreds of derived addresses. Most tax tools handle this by accepting an extended public key (xpub/zpub) rather than individual addresses. Check whether Zelcore exposes this — if not, you may need to export individual addresses or use a block explorer to enumerate them.
Keep a running list: chain, address, first transaction date.
Step 2 — Choose a tax tool and import
Since Zelcore has no native export, you'll use a third-party platform that reads directly from the blockchain. All of the following support wallet-address import across the chains Zelcore covers:
- Koinly — broad chain support, clear UI, good for most jurisdictions
- CoinTracker — strong DeFi detection
- CoinLedger (formerly CryptoTrader.Tax) — 150+ platform integrations, 10,000+ cryptocurrencies, official TurboTax partnership, supports ETH, SOL, Polygon, Arbitrum, Avalanche, Cardano, and Cosmos
- TokenTax — full-service option with CPA support
- Blockpit — preferred in Germany and Austria
For each tool, the import flow is the same: add a new wallet → select the blockchain → paste your public address → let the tool sync. Most platforms pull historical data automatically once the address is confirmed.
Repeat for every address on your list. If you used centralized exchanges alongside Zelcore, import those via API or CSV export from the exchange — the tax tool will merge everything into one ledger.
Step 3 — Classify each event type
Once imported, your tax tool will categorize transactions automatically. Review every entry — automated classification makes mistakes, especially on DeFi interactions and internal transfers.
| Event | Tax treatment (general) |
|---|---|
| Receive from external party (payment, compensation) | Income at FMV on receipt |
| Send to your own address | Not taxable — label as "transfer" |
| Buy (fiat → crypto) | Establishes cost basis; not taxable at purchase |
| Sell (crypto → fiat) | Taxable disposal |
| Swap (crypto → crypto) | Taxable disposal in the US, UK, and most major jurisdictions (IRS FAQ Q-16) |
| Staking reward | Ordinary income at receipt per IRS position — note: this treatment is contested (see Jarrett v. United States); the legal landscape is unsettled |
| Airdrop (US) | Ordinary income at FMV on receipt per Rev. Rul. 2019-24 |
| Airdrop (UK) | If received with no service rendered, may not be income at receipt — disposal triggers CGT (HMRC CRYPTO21250). Airdrops for services are income. |
| Gas fees | Deductible: add to cost basis on acquisitions, subtract from proceeds on disposals |
| Bridge (same asset, different chain) | Generally an internal transfer — label accordingly |
| Wrap (e.g., BTC → WBTC) | Tax treatment unsettled in the US; consult a CPA |
UK note: UK individuals must use the Section 104 Pool method (TCGA 1992 S104–S106A) with same-day and 30-day bed-and-breakfasting rules. FIFO and LIFO do not apply to UK individuals. Staking rewards are taxable as miscellaneous income at receipt (HMRC CRYPTO21200).
US note: IRS Notice 2014-21 classifies cryptocurrency as property. Cost-basis methods available to US taxpayers include FIFO, LIFO, HIFO, and Specific Identification (IRS FAQ Q-38/39). Your tax tool or CPA should confirm which method applies to your situation.
Step 4 — Review and export your report
After classification, run a reconciliation check in your tax tool. Most platforms flag:
- Missing cost basis (usually means a transaction before the tool's data range)
- Unmatched sends/receives (often internal transfers that weren't labeled)
Fix these before exporting. Once clean, export the tax report format your filing software requires: IRS Form 8949 and Schedule D for US filers, Capital Gains Summary for UK Self Assessment, or the equivalent for your jurisdiction.
Most major tools integrate directly with TurboTax, H&R Block, or allow PDF/CSV export for manual entry.
If something goes wrong
Problem: Tax tool shows a "sale" on a transfer between your own wallets. This happens when the tool sees an outgoing send from wallet A and an incoming receive at wallet B, but doesn't know they're both yours. Fix: tag both transactions as "transfer" and link them. Most tools have a merge or transfer-match feature.
Problem: Missing transactions from a chain. Check that you imported the correct address format for that chain. Some chains (Cosmos, Cardano) require specific address types. If transactions still don't appear, use a block explorer to verify the address has on-chain activity, then re-sync.
Problem: Staking rewards show unusual amounts. If you used auto-compounding staking, each compound event may be a separate taxable income entry. Review with your CPA — the volume of micro-events can affect reporting strategy.
Problem: You have more chains than the tax tool supports. Check the platform's supported chain list before committing. If a chain is missing, export a CSV from the chain's block explorer and import it manually. The format varies by tool.
Final checklist
- All Zelcore addresses collected (one per chain per account)
- xpub/zpub used for Bitcoin if available
- Exchange accounts imported alongside wallet addresses
- Every send-to-self labeled as transfer
- Swaps reviewed for correct cost-basis reset on acquired side
- Staking rewards classified as income (verify treatment with CPA)
- Airdrops classified per your jurisdiction's rules
- Gas fees applied correctly to acquisitions and disposals
- Wraps and bridges flagged for CPA review
- Report exported in the format required by your filing software
Not tax advice. Every jurisdiction treats crypto differently, and the rules around staking, airdrops, and DeFi interactions continue to evolve. This guide covers technical workflows only. For anything that affects your actual tax return, work with a qualified CPA who has experience with digital assets.
