Wallet Lot Ledger and Form 1099-DA transfer-in match

Prepared by Tensorust LLC, Wallet Lot Ledger · built 2026-11-10 03:48 UTC · method: FIFO within each wallet (Treas. Reg. 1.1012-1(j)); lots carried on transfers between listed wallets

Wallets read

Form 1099-DA transfer-in lines matched to wallet transactions

Form 8949 rows (box H or K, basis not reported to the IRS)

Outbound transfers (what will appear as noncovered proceeds when sold at the broker)

Acquisition lots

Rev. Proc. 2024-28 status (opening inventory on January 1, 2025)

Exceptions (unsupported items the preparer must resolve)

Method memo

1. What this is. A records workpaper: chain history for the listed wallets rebuilt into acquisition lots, with the units that left each wallet matched to the broker's Form 1099-DA transfer-in lines. It is not tax advice. The signing preparer decides every position.
2. Why the broker left basis blank. Under the Instructions for Form 1099-DA, a digital asset "transferred in to the broker providing custodial services" is a noncovered security. The broker reports gross proceeds (box 1f), checks box 9, and reports the units transferred in (box 12a) and the transfer-in date (box 12b). It is not required to report basis (box 1g), acquisition date (box 1d) or gain. Customer-provided acquisition information may be used by the broker "solely for lot-selection purposes and not for reporting basis or acquisition dates." This is not transitional: TD 10000 deferred section 6045A transfer statements for digital assets to a future rulemaking that has not been proposed, so transferred-in units stay noncovered regardless of acquisition year.
3. What the taxpayer must do with it. Report each sale on Form 8949 with box H (short-term, basis not reported to the IRS) or box K (long-term, basis not reported), the supported basis in column (e), nothing in column (f) or (g) unless an adjustment applies. A blank broker basis box does not mean the basis is zero: the taxpayer still reports supported basis. Return software that imports the broker file literally may treat a noncovered lot's blank basis as zero; these rows exist to overwrite that.
4. Lot method. First-in, first-out within each wallet, as Treas. Reg. 1.1012-1(j) requires for acquisitions and dispositions on or after January 1, 2025 (the universal pool ended). Earlier history is kept per wallet as well so the Jan 1 2025 opening inventory is itself traced. Transfers between two listed wallets of the same taxpayer carry their lots (acquisition date and unit cost) rather than creating new ones. Network fees paid in the sent asset consume lots pro rata and are shown separately; gas paid on token transfers, approvals, swaps and failed transactions consumes native-asset lots as its own fee-only event and is not capitalized into any token's basis (preparer's election).
5. What an inbound lot means. The chain shows when units arrived in a wallet and from where, not why. A lot is opened at each arrival: a contract output (swap, claim, unwrap) is an acquisition on that date; an arrival from another listed wallet carries its lots; an arrival from a labelled exchange wallet is marked "exchange withdrawal" and its cost is a receipt-date placeholder, because the purchase happened inside the exchange (its trade history holds the real cost and date, and with that export the lots are carried through); any other inbound transfer is priced at the receipt-date market value and left for the preparer to characterize (purchase, gift, income, or a transfer from a wallet not listed).
6. Prices. Native assets and tokens at their canonical contract carry the USD daily close for the UTC acquisition date from Coinbase Exchange public candles (SYMBOL-USD). Other tokens are priced by contract address at the transaction time from the DefiLlama coins API, then the CoinGecko contract price (public history covers the last 365 days). USD stablecoins at their canonical contract are at par. A token that only shares a symbol with a known asset is marked unverified and never priced by its name; spoofed token transfers (address poisoning) are dropped and counted. Where no public price exists the lot is left unpriced and listed on the exceptions page rather than guessed. The price source is written on every row.
7. Destination detection. An outbound transfer is marked as a broker transfer when the destination is a publicly labelled exchange hot wallet, when the destination's first outgoing transfers go to one (a fresh deposit address being swept), or, on Bitcoin, when the destination is later spent in a many-input consolidation. The signal used is named on the row. The authoritative tie is the broker's own box 12a units and box 12b date, which is what the match uses.
8. Matching rule. A 1099-DA line matches the outbound transfer of the same asset whose sent units are within 2% of box 12a and whose chain timestamp is 0 to 4 days before box 12b (brokers credit after confirmations). Exact units to a detected broker destination is "high" confidence. Unmatched lines are listed with the reason; nothing is forced.
9. Rev. Proc. 2024-28. The safe-harbor allocation deadlines have passed (specific unit allocation by the earlier of the first 2025 disposition or the 2025 return due date including extensions, October 15, 2026 for calendar-year individuals; global allocation had to be in the books before January 1, 2025). Section 4 leaves open factual attribution: a taxpayer who can tie units of basis to specific units does not need the safe harbor. The status page shows, per wallet and asset, whether every unit held on January 1, 2025 traces to a specific acquisition transaction in that wallet.
10. Exceptions are the product's honesty. Units sent beyond visible acquisitions, unpriced assets, coinjoin spends, bridges and contract interactions are flagged, not resolved silently. The transaction types Notice 2024-57 excuses brokers from reporting for now (wrapping and unwrapping, liquidity provider, staking, lending of digital assets, short sales, notional principal contracts) are flagged where visible; their tax treatment is the preparer's call and is not classified here.
11. Sources. Public chain data read-only (mempool.space, Routescan, Blockscout, Etherscan API v2, Solana JSON-RPC); Coinbase Exchange, DefiLlama and CoinGecko public price endpoints. Nothing was signed, moved or custodied. Citations: Instructions for Form 1099-DA (irs.gov/instructions/i1099da); Rev. Proc. 2024-28; TD 10000 preamble (89 FR 56480); Notice 2024-57; Notice 2026-20; Treas. Reg. 1.1012-1(j).

Data sources used in this run: Routescan (Ethereum) etherscan-compatible API: txlist, tokentx, txlistinternal; failed transactions excluded; 15 spoofed token transfers ignored (address poisoning: the wallet neither held the token nor sent the transaction); Coinbase Exchange public daily candles (native assets and canonical contracts); DefiLlama coins API by contract at the transaction time; CoinGecko public contract prices (365-day window); canonical USD stablecoins at par

Records product, not tax advice. Read-only public chain data; nothing was moved or signed. Tensorust LLC, New York.