Tax Rules · September 17, 2026 · 13 min read · By CryptoTaxCalc Team

Wallet-by-Wallet Cost Basis 2026: The IRS Rule Rewriting Your Records

Final IRS regulations now make brokers track crypto basis per wallet, not as one global pool. Here's what changes for multi-wallet and self-custody users, how transfer statements decide your basis, and how seven countries run the same calculation differently.

Image: Illustrative purposes. Rules cited from the final Treasury regulations under IRC §6045 (December 2024), Form 1099-DA instructions, HMRC Cryptoassets Manual, CRA Folio S5-F3-C1, ATO guidance, NTA guidance and Indian Income Tax Act §115BBH.

A few weeks ago I wrote about a guy in Dallas who paid roughly $975 in tax he never actually owed. His mistake was moving his own ETH between three of his own wallets. The coins came back to the exchange with no cost-basis paperwork, the tax form treated the gap as $0 basis, and the IRS read $0 as "100% profit."

That piece was about your side of the problem — the records you lose when coins travel. This one is the regulator's side, because the plumbing underneath it just changed. In December 2024 the Treasury published final regulations under Internal Revenue Code Section 6045 — the same law that gave stocks broker-reported basis back in 2011. Starting with digital assets acquired on or after January 1, 2025, with reporting phased across the 2025, 2026 and 2027 tax years by asset category, brokers must track and report cost basis on a wallet-by-wallet basis. I called the old problem the phantom-tax trap; this is the rule aimed at it.

Honestly, it's the biggest shift in US crypto record-keeping since Notice 2014-21 declared crypto property. Here's what the rule says, how "per-wallet" differs from the universal pooling tax software uses today, why transfer statements are the whole ballgame, and how six other countries run the same math.

1. What the final rule actually says

The short version: digital-asset brokers — exchanges, hosted wallet providers, payment processors that effectuate trades, plus a few platforms the definitions sweep in — must report not just proceeds but basis, gain or loss, and holding period on Form 1099-DA. Proceeds reporting started with the 2025 tax year; basis reporting rolls in behind it.

The architecture is borrowed wholesale from the securities industry. After 2008, the IRS phased broker basis reporting in for stocks (2011), mutual funds (2012), and options and bonds (2014). Covered shares carried basis between firms on standardized transfer statements; anything undocumented was flagged non-covered. Crypto now gets the same plumbing, fifteen years late, with one harder feature: crypto routinely moves through wallets no broker controls.

The key pieces, stated carefully because the phase-in is staggered and parts of the rule remain in litigation:

• Wallet-by-wallet is the default. A broker keeps a basis ledger per wallet — each account, hosted wallet, or address is its own silo. When units leave a wallet in a partial transfer, basis gets allocated to the outbound coins under the broker's ordering rule, typically FIFO inside that wallet.
• The universal wallet election exists. After heavy industry pushback on the original proposal, the final regulations let a broker pool all of a customer's wallets it services — the "universal wallet" method — when the eligibility conditions are met and the customer elects it. That gets closer to the one-big-pot matching tax software does today, but only for wallets the broker can actually see and document.
• Inbound assets live or die by the transfer statement. Coins arriving from another broker with a compliant statement carry over their basis and acquisition date. Coins arriving without one — the classic case being deposits back from your own hardware wallet — have no basis the receiving broker is permitted to report. The field shows as unknown, and downstream it behaves like $0.
• Dates are staggered. The regime applies to assets acquired on or after January 1, 2025, but different reporting pieces come online across the 2025, 2026 and 2027 calendar years for different categories. The provisions covering transfers to unhosted (self-custody) wallets are the most contested — Coin Center and others sued over privacy — and that slice has been pushed latest. Check the current IRS schedule before you rely on any single date.

So "2026 rule" means the filing season when taxpayers first see the new basis fields populate on 1099-DA — not a switch that flips for every coin on January 1.

2. Universal pooling vs per-wallet tracking: same coins, two answers

To see why the wallet boundary matters, you have to understand what decent tax software has quietly done for years. It builds you a universal pool: one giant bucket of Bitcoin containing every lot you ever bought on every exchange and every receipt at every address, sorted by date. When you sell, FIFO reaches across the entire bucket; HIFO grabs the most expensive coin anywhere in it; specific identification lets you point at a precise lot. Which wallet the coin sat in is just a label — every wallet is yours, so the pot is one pot. I worked through the FIFO, HIFO and specific-ID mechanics in the cost-basis methods guide.

The broker's new per-wallet ledger cannot do that. Each wallet is a separate silo, and matching runs only inside the silo. A sale on Kraken cannot be matched against a lot bought on Coinbase unless that lot physically traveled to Kraken carrying a transfer statement. From the receiving broker's seat, an anonymous inbound deposit is a brand-new asset with no history — not the same coin it remembers selling you two years ago.

Here's the thing: it's the same coin, same owner, same tax law — only the paperwork differs. Worked example:

• April 2025: buy 1 BTC on Coinbase for $30,000. Coinbase's wallet ledger: Lot A, basis $30,000.
• June 2025: send that BTC to MetaMask, then to a Ledger. A self-transfer — not taxable, and your holding period keeps running.
• March 2026: send 0.5 BTC from the Ledger back to Coinbase and sell it at $90,000. Proceeds: $45,000.

A $15,000 swing in reported gain, decided by whether a document followed the tokens. Your true legal gain is $30,000 in every row, and you're entitled to report that on Form 8949. The problem: the IRS holds a form saying $45,000, and you're contradicting an information return with your own spreadsheet — exactly the situation that generates automated notices.

A word for the HIFO camp: specific identification is not dead. You can still identify exact units on your own return when your records meet the IRS standard — per-unit acquisition date, basis, fair market value, proceeds and sale date. What changed is what the broker prints on the government copy: wallet-level ordering unless the universal election applies and the broker actually holds the data. Coins on a Ledger are invisible to any broker's election.

3. The transfer statement: basis now travels with paperwork

The transfer statement is the engine of the new regime. When a broker moves a covered asset to another broker, it must furnish a statement — the securities analog is due within fifteen days — carrying at minimum:

• the sending and receiving parties and the destination wallet or account;
• the date, time and number of units transferred;
• per-unit basis and the original acquisition date, so long-term versus short-term status survives the trip;
• fair market value at the time of transfer for units that arrived as income (staking rewards, airdrops, hard forks).

Chain statements together and basis follows the coin hop by hop — Coinbase to Kraken, Kraken to a prime broker, on to the buyer. Every firm reports the same number and every Form 8949 ties out, no phantom gain. It's the deliberate fix for the exchange-to-exchange black hole in the wallet-transfer tax guide: brokers can now hand basis across the gap like stockbrokers have since 2011.

Partial transfers have allocation rules. Move 0.3 BTC out of a wallet holding 1.2 across four lots, and the broker assigns basis to the outbound coins using wallet-level ordering — oldest first by default. The rest keep the unused basis. That allocation at the transfer point is the number the IRS sees years later when the coin sells.

The catch is one word: broker. Statements exist only when both ends of the trip are reporting firms. A Ledger Nano does nothing but sign blockchain transactions. It will never issue a transfer statement, and no regulation can compel a piece of hardware to.

4. Why self-custody stays the basis black hole

Here's the thing the "not your keys, not your coins" crowd dislikes hearing: self-custody and broker-reported basis are structurally incompatible. The entire per-wallet system assumes an institution keeps books at every hop. Your hardware wallet represents nothing but a key pair.

So the round trip that keeps crypto accountants employed looks like this: exchange → cold storage, years pass, cold storage → exchange. The outbound half is visible; the inbound half arrives from an address the receiving broker doesn't recognize, with no statement attached, and gets booked with unknown basis. Bridges and wrapped tokens make it worse — bridge ETH to a rollup and bring back a bridged token and even the address lineage is severed.

Regulators tried to plug this by eventually requiring brokers to log transfers to unhosted wallets, including addresses. That's the provision privacy advocates sued over, delayed furthest into the phase-in, and its final shape remains uncertain. Even intact, an outbound log is not inbound basis: the broker getting coins back in 2029 still has no document showing what you paid in 2023.

The burden for the self-custodied part of your stack therefore stays exactly where it was: on you. Broker-to-broker life gets cleaner; coins you held yourself get almost nothing. The contrast sharpens — exchange-held coins will reach the IRS with tidy basis while self-custodied coins arrive with blanks, and the blank is what the computer reads as zero.

5. How seven countries handle cost basis

The American wallet-level regime is an outlier. Most tax authorities don't ask which wallet held a coin at all. They define basis by asset, pool everything you own of that asset across all of your wallets, and leave the wallet map for you to reconstruct if asked. The comparison:

The UK is the purest "wallets don't exist" system — one Section 104 pool per asset across every exchange and device, with same-day and 30-day matching applied before the pool average. Moving coins between your own wallets changes nothing in the math; HMRC only expects you to identify the units if asked. Canada runs the same instinct as adjusted cost base: one running average per coin, HIFO unavailable, the 50% inclusion rate doing the real work. Japan forces moving-average or total-average pools and taxes them as miscellaneous income; Germany applies FIFO lot by lot but the one-year exemption usually dominates; Australia accepts FIFO, weighted average or consistent specific ID, with the 12-month discount as the prize; India prescribes almost no method, leaving the flat 30% tax and 1% TDS to do the work.

Notice the direction of travel in the US: brokers must now track something narrower — wallet-level lineage — than the asset-level pools other countries compute. The two coexist cleanly while records are complete and diverge the instant a coin detours through self-custody. If you file stateside, model the real bill on the US crypto tax calculator; don't assume the broker's form did the work for coins you held yourself.

6. What to actually do: rebuild your wallet graph

I'd turn this into a weekend project — the same drill for anyone who lived through the phantom-tax problem. Four steps.

1. Inventory every wallet. Every exchange account (including dead ones), every browser and mobile hot wallet, every hardware device, chain and bridge you've used. Note addresses plus first and last use dates. This is the wallet graph — the map all transfer matching hangs on.
2. Export all the CSVs now. Exchanges prune history, accounts close, and 2017-era self-custody pioneers were famously lax with spreadsheets. Pull trade, deposit, withdrawal and reward files from every source, plus explorer or tracker exports for self-custody. Then merge them: the free batch importer on this site reads multiple CSVs entirely in your browser (nothing is uploaded), tolerates different column layouts, and lets you tag self-transfers so a move never gets counted as a sale. That merge is what converts per-wallet fragments into one universal ledger.
3. Submit historical basis to brokers before you sell. Most large exchanges run a basis-import or "update cost basis" workflow — feed them old records while you still have account access, not in April after a 1099-DA arrives with a blank basis column. Coins bought before 2025 sit outside the covered regime, but documenting them also protects post-2025 coins that later flow back in.
4. Preserve transfer evidence. For every self-custody move, keep the transaction hash, date and time, USD fair market value, and a label identifying the destination as yours — "Ledger #2," "MetaMask–Arbitrum." Explorer links and screenshots are fine. Three years from now that folder is what upgrades the broker's blank from $0 to your real number.

Then reconcile. When the 1099-DA arrives, match every line to your own ledger before filing. Where the broker shows unknown basis and yours is documented, Form 8949 is built for the correction — broker proceeds, your basis, adjustment code, short explanation. The dispute mechanics are in the 1099-DA basis-repair guide.

7. Where 1099-DA meets the CP2000 machine

The 2026 filing season — reports covering tax year 2025 — is the first time many Americans will receive a Form 1099-DA at all, led by gross proceeds. Basis, holding period and gain-or-loss fields then populate in phases as covered assets work their way through sales and the later effective dates arrive.

The IRS doesn't read these forms by hand. The Automated Underreporter Program compares each 1099-DA against Schedule D and Form 8949 by computer. Your return says $30,000 gain; the form says $45,000. Months later a CP2000 notice lands proposing tax on the difference, plus interest and occasionally penalties — automatically, with no agent reviewing your Ledger receipts.

You can beat that notice — taxpayers do, by responding in the window with purchase records, transfer statements, transaction hashes and transfer evidence. But winning depends on records gathered years in advance. The era of shrugging and saying "the exchange has my history" is ending: it has the history of its own wallet, and under the new rules that's all it may report without paperwork from you.

Bottom line

The wallet-by-wallet regime doesn't change what you owe. It changes what the government already thinks you owe before you file. Coins that travel broker to broker with transfer statements will report cleanly, the way covered stock shares have for fifteen years. Coins that detour through self-custody show up with blank basis unless your own evidence fills the gap — and in the US a blank is how a $30,000 gain gets mailed to you as $45,000. Elsewhere, from the UK's Section 104 pool to India's flat 30%, the wallet boundary barely exists in law, which is cold comfort if you're the one who has to prove the numbers.

Build the wallet map. Merge the CSVs. Keep the tx hashes. The tax law is the same as it ever was — the paperwork just finally caught up to how crypto actually moves.

General information, not tax advice. The Section 6045 regulations are phasing in across 2025–2027 and the unhosted-wallet provisions remain subject to litigation and possible IRS relief. For large balances, cross-border filings or disputed 1099-DA figures, work with a qualified crypto tax professional.

FAQ