IRS Form 1099-DA Cost-Basis Rules Take Effect: Why Depositing Cold-Wallet Crypto to US Exchanges Now Risks a Zero-Basis Trap

The operational danger in the United States’ 2026 crypto reporting rollout is a missing link between a sale and its acquisition history. A brokerage can know exactly how much cryptocurrency it sold for a customer while lacking the records needed to establish that customer’s taxable profit. For investors moving years-old holdings out of self-custody, preparing that history before liquidation is now a central tax-control task.

The phrase zero-basis trap describes a reporting and substantiation failure, not a rule that confiscates the basis of deposited assets. Transferring holdings between wallets or accounts owned by the same taxpayer generally does not create income; digital assets spent on transfer services require separate consideration. The transfer itself does not establish a new purchase price. IRS digital-asset transaction FAQs, question 81.

As of October 13, 2026, two different reporting years matter. Reportable 2025 sales generated the first gross-proceeds Forms 1099-DA furnished and filed in 2026. Reportable 2026 sales fall within the next phase, including mandatory basis reporting for covered assets, with the corresponding annual forms arriving in 2027. Applicable exemptions and optional reporting methods still matter; the rollout does not mean every blockchain movement produces an information return. IRS digital-assets guidance.

For a taxpayer preparing to liquidate cold-storage holdings, the immediate question is therefore practical: can every unit being sold be connected to a defensible acquisition date, adjusted basis, and transfer history? An exchange deposit confirmation answers where the units arrived. It does not necessarily answer what the investor paid for them.

Section 80603 of the Infrastructure Investment and Jobs Act, Pub. L. 117-58, expanded Internal Revenue Code Section 6045’s broker-reporting framework and added digital assets to the specified-security provisions. Treasury Decision 10000, published July 9, 2024, at 89 FR 56480, implements the custodial-broker regime. Its terminology serves tax information reporting; calling a token a covered or noncovered security here does not determine its classification under securities law. TD 10000.

For ordinary investment purchases, covered status generally requires acquisition after December 31, 2025, in the reporting broker’s custodial account and continued custody there until disposition. Older holdings and transferred-in assets are noncovered. Consequently, an asset purchased in 2026 elsewhere and later deposited is not made covered simply by its recent purchase date. This is a limit on mandatory broker basis reporting, not the taxpayer’s ability to substantiate basis. 2026 Form 1099-DA instructions.

That distinction applies when considering a transfer to a US brokerage such as Coinbase, Kraken, or Gemini. The relevant account and transaction records need examination; a familiar platform name is no substitute for that review. Likewise, Ledger, Trezor, and MetaMask identify ways of holding or accessing assets, not the acquisition history attached to those assets. A wallet address can contain units bought at many prices over several years.

The form’s fields should be read together:

For noncovered sales, brokers may check Box 9 and omit basis, or voluntarily provide it. The instructions explicitly require a blank Box 1g when basis is not reported; zero belongs there only when actual basis is zero. Unknown basis and zero basis are different facts. 2026 Form 1099-DA instructions.

Consider a hypothetical investor who purchased one bitcoin for $28,000 in 2023, moved it into self-custody, and deposited it into a US brokerage in September 2026. Assume the investor sells it for $80,000, holds it as a capital asset, and has no relevant fees or basis adjustments. The economic and tax calculation is $80,000 minus $28,000: a $52,000 long-term gain. The broker’s inability to supply the purchase record does not change that arithmetic.

An import process that substitutes zero for missing basis would instead calculate $80,000 of gain. That would overstate gain by $28,000; it would not automatically mean $28,000 of additional tax. The tax difference depends on the taxpayer’s circumstances. Conversely, omitting the sale because the brokerage has incomplete acquisition data leaves the proceeds unreconciled. Both mistakes arise from letting a data gap dictate the return.

A useful accounting system therefore needs an explicit unresolved-basis status. It should distinguish records awaiting evidence from assets whose basis has actually been established as zero. An exception report that lists missing purchases is more useful than a gain report that silently turns every unmatched deposit into a windfall.

Wallet-level accounting is a separate obligation from broker reporting. Treasury Regulation § 1.1012-1(j), adopted in TD 10000, applies the identification rules within wallets or accounts, with applicability beginning January 1, 2025. The final-rule explanation rejects universal pooling across wallets. The 2026 broker basis phase is therefore not the starting date for taxpayers’ wallet-by-wallet tracking. TD 10000, discussion of basis identification.

Suppose a taxpayer has one bitcoin with $20,000 basis in Wallet A and another with $60,000 basis in Wallet B. Selling the unit in Wallet A cannot be supported by simply choosing Wallet B’s higher basis from a consolidated portfolio screen. A consolidated dashboard remains useful for portfolio management, but its tax ledger must preserve the wallet or account from which units actually leave.

When units move, the receiving ledger should retain their acquisition history. For example, transferring half of a single one-bitcoin lot with $30,000 basis would carry $15,000 of that lot’s basis with the half transferred, assuming no relevant adjustments. The sending ledger must also reduce its remaining quantity and basis. Recording the incoming half as a fresh purchase at its deposit-day market value would create an unsupported step-up; leaving the entire original basis behind would duplicate it. These are illustrative bookkeeping consequences of preserving unit-level history, not additional tax elections.

For investors who previously used universal accounting, Revenue Procedure 2024-28 established a transition safe harbor for allocating unused basis to remaining units as of January 1, 2025. Its reasonable-allocation, documentation, and timing conditions matter. It does not authorize a taxpayer in October 2026 to invent a favorable opening allocation after seeing subsequent gains. Preserve the original transition workpapers, acquisition dates, allocation method, and evidence that the applicable requirements were met. Revenue Procedure 2024-28.

Specific identification also has a timing requirement. Ordinarily, identification for broker-held units is communicated to the broker by the transaction’s date and time, using an acceptable identifier or standing instruction. Without adequate identification, FIFO generally applies within the relevant holdings, using the taxpayer’s acquisition chronology rather than merely the order of exchange deposits. IRS digital-asset transaction FAQs, questions 82–85.

A material 2026 development changes how that requirement can be satisfied. Notice 2026-20 extends Notice 2025-7’s temporary relief through December 31, 2026. Eligible taxpayers may identify broker-held units in contemporaneous books and records, or record a sufficiently specific standing order before the transaction. The relief does not extend to self-custodied units and does not change the broker’s information-reporting rules. The notice expressly anticipates that a broker’s reported acquisition date and basis may differ from the taxpayer’s valid identification. Notice 2026-20.

This makes the date of a tax-software setting consequential. A standing instruction recorded before a sale can document what the investor intended to dispose of. A setting selected months later merely because it reduces the displayed tax bill is not equivalent evidence. Where the taxpayer relies on the relief, retain the instruction, its creation time, the applicable account, and the resulting lot assignments alongside the eventual brokerage statement.

DeFi requires another distinction between reporting coverage and underlying taxation. Notice 2024-57 postpones Section 6045 reporting for six defined transaction groups pending further guidance: wrapping and unwrapping; liquidity-provider deposits and redemptions involving automated market makers; staking transactions; transactions described as digital-asset lending; transactions described as short sales; and notional principal contracts. These descriptions define the relief’s scope, not definitive tax treatment. Rewards and other compensation require separate analysis; the notice is not a blanket exemption for everything occurring within a DeFi protocol. Notice 2024-57.

Revenue Ruling 2023-14 holds that a cash-method taxpayer includes staking rewards in gross income at fair market value when the taxpayer obtains dominion and control. That is more precise than assuming every displayed or technically credited reward is immediately available. The ruling also addresses staking through an exchange. Revenue Ruling 2023-14. An ordinary exchange of one materially different digital asset for another can produce taxable gain or loss even without a broker form; withdrawing dollars to a bank is not a prerequisite. IRS digital-assets guidance.

For operations teams, this means that a rewards ledger and a sales ledger need to connect. A reward entry should preserve the recognition date, units, dollar valuation, and supporting price data. If those units later enter a brokerage, the deposit record should link back to that entry. Otherwise, a system may correctly capture the initial income but lose the information needed to compute the later disposition.

Broker transition relief must also be dated carefully. Notice 2024-56’s general good-faith relief from Sections 6721 and 6722 penalties concerns 2025 transactions reported in 2026. Its original backup-withholding provisions under Section 3406 included broader 2025 relief and conditional later relief. Describing this as blanket good-faith protection for all 2026 transactions confuses the transaction year with the filing year. Notice 2024-56.

Notice 2025-33 subsequently extended the general digital-asset-sale backup-withholding relief through calendar 2026 and modified certain 2027 provisions. It did not convert the original 2025 information-return good-faith provision into a general waiver for every 2026 reporting error. Neither notice eliminates customers’ income-tax obligations. Reporting penalties, withholding duties, and the investor’s tax liability are distinct questions. Notice 2025-33.

A practical preparation process can be organized around five controls:

1. Build an acquisition inventory before transferring. For each lot, retain quantity, acquisition date and time, dollar cost, relevant adjustments, source account, and supporting purchase records. Include pre-2026 assets rather than assuming the receiving brokerage will reconstruct them.
2. Link the evidence across systems. Connect exchange trade confirmations and purchase receipts to withdrawal records, public transaction IDs, receiving addresses, and brokerage deposits. Bank statements can corroborate funding, but a bank transfer alone does not establish which token was purchased or at what price. A blockchain transaction ID establishes movement, not necessarily dollar acquisition cost.
3. Preserve timely lot instructions. Record the units selected for a disposition or transfer, the applicable standing order, and any broker confirmation. If relying on Notice 2026-20, retain the contemporaneous internal record supporting that reliance.
4. Reconcile quantities as well as dollars. Review opening units, purchases, rewards, transfers, sales, and closing units by wallet or account. Investigate unmatched movements and duplicate imports before accepting the software’s gain calculation. Keep transfer fees separately identifiable.
5. Prepare a statement-to-return bridge. Match reported proceeds to disposal records, explain missing or differing basis, distinguish corrected forms from originals, and retain the final calculation used on the return. For a fund, assign someone to review and resolve exceptions before the filing package is approved.

Form 8949 routing deserves particular attention. The digital-asset categories are H in Part I for short-term transactions reported without basis to the IRS and K in Part II for corresponding long-term transactions. G and J cover reported-basis transactions; I and L address digital-asset transactions without a corresponding information return. The familiar B/E shorthand belongs to the other reporting categories and should not be copied mechanically into a Form 1099-DA workflow. Use the applicable tax-year form and instructions when filing. IRS Form 8949 instructions.

For a noncovered sale whose basis was not reported, the taxpayer generally enters the correct basis in column (e). Correcting basis that was reported to the IRS follows different adjustment instructions. In the hypothetical $80,000 sale, the working papers should bridge that proceeds figure to the documented $28,000 basis and $52,000 gain, then to the appropriate Form 8949 and Schedule D totals. IRS Form 8949 instructions, basis corrections.

Finally, the CP2000 risk should be explained without inventing an enforcement algorithm. The IRS says its Automated Underreporter system compares third-party information with returns, followed by tax-examiner review of potential discrepancies. A CP2000 proposes changes; it is not itself a bill. The cited guidance does not establish that checking Box 9 automatically produces a notice or causes the IRS to reject otherwise substantiated basis. IRS Topic 652.

The defensible risk assessment is narrower: if proceeds appear in third-party reporting while the return omits the sale or fails to account for its basis, the resulting discrepancy can leave taxable gain overstated. This is an operational inference, not a prediction that every cold-wallet deposit will trigger enforcement.

If a notice arrives, review its payer, tax year, proceeds, and proposed changes against the filed return. Respond by the stated deadline and provide a focused explanation of any disagreement with supporting records. Follow the notice’s response procedure; an amended return is not automatically required merely because a CP2000 arrived. The IRS provides separate instructions when additional changes warrant Form 1040-X. IRS CP2000 response guidance.

A useful response packet would let a reviewer follow one continuous chain: original acquisition, intervening transfers, eventual sale, and the amount already reported. For the hypothetical investor, that means the purchase confirmation, the records connecting the purchased bitcoin to cold storage and the brokerage, the sale statement, and the return reconciliation. A folder of unexplained blockchain screenshots would make that task harder than a short indexed schedule with the underlying evidence attached.

Investors preparing transfers now can reduce that future burden by treating missing acquisition records as an exception to resolve before liquidation. The decisive control is continuity: every sale should remain connected to the units actually disposed of and the evidence supporting their basis, even when the brokerage’s own reporting is incomplete.