Crypto Estate Planning Under the New IRS Digital Asset Rules 2026

Davit Cho · Crypto Tax Researcher · Founder, LegalMoneyTalk · CEO, JejuPanaTek
Independent research on IRS digital asset rules, 1099-DA reporting, and cross-border crypto tax compliance.

THE SHIFT

Crypto inheritance just stopped being a legal grey zone.

In 2026, the IRS finalized digital asset estate rules. Step-up basis still applies — but only if the assets are documented, custodied, and reported correctly. Trust-held crypto sits in a 1099-DA reporting gap that most estate attorneys have not yet adapted to.

TL;DR

• Step-up basis at death still applies to crypto held directly or in revocable trusts.
• Irrevocable trust crypto is outside the estate — no step-up, but no estate tax either.
• The 2026 federal estate exemption is $13.99M per individual ($27.98M married).
• 1099-DA broker reporting does not extend to most trust-held wallets — a documented gap.
• Without proof of fair market value at death, heirs default to original basis (worst case).

What changed in 2026

For years, crypto inheritance ran on assumption. Heirs received wallet keys, sold the assets, and reported gains using whatever cost basis they could reconstruct — or the deceased's original basis when nothing else was available. The IRS rarely audited because there was no broker report to compare against.

That ended on January 1, 2026. With Form 1099-DA reporting now active and the per-wallet basis rule from Rev. Proc. 2024-28 in effect, the IRS has structured visibility into individual crypto holdings for the first time. But trusts — the primary vehicle for estate planning — sit largely outside this reporting net. The result is a rule set where direct holdings are tracked tightly, trust holdings are tracked weakly, and the gap between them is now the most contested area in crypto estate planning.

How step-up basis works for crypto

Step-up basis is the rule that resets an asset's cost basis to its fair market value on the date of death. If a decedent bought 10 BTC at $10,000 each ($100,000 total) and the BTC was worth $80,000 each at death ($800,000), the heir's new basis is $800,000. If the heir sells immediately, taxable gain is zero. If they sell six months later at $90,000 per BTC, taxable gain is $100,000 — not $800,000.

This rule applies to crypto held in three structures: directly in the decedent's name, in a revocable living trust, or in a joint account where the decedent had ownership. It does not apply to crypto in irrevocable trusts (which are no longer part of the estate), in retirement accounts (which use different rules), or to crypto gifted before death (which carries the original basis forward).

The documentation requirement is the practical problem. Step-up basis is not automatic. The heir must establish fair market value at the date of death using contemporaneous price records — typically the closing price on a major exchange (Coinbase, Kraken, Binance.US) on the date of death, screenshotted or downloaded with timestamp. Without that record, the IRS can require the heir to prove the deceased's original basis instead, which often means defaulting to a much lower number and a much higher tax bill.

Revocable vs. irrevocable trust: the core decision

The choice between a revocable and an irrevocable trust is the single most consequential decision in crypto estate planning. They are not variations of the same tool — they produce opposite tax outcomes.

A revocable living trust keeps the grantor in control. The crypto remains part of the taxable estate at death, which means estate tax may apply if the estate exceeds the $13.99M exemption — but the heir gets full step-up basis. For most crypto holders below the exemption threshold, this is the simpler and more tax-efficient structure. The trust avoids probate, the basis resets, and no estate tax is owed.

An irrevocable trust removes control. Once crypto is transferred in, the grantor cannot retrieve it or change beneficiaries. The assets leave the taxable estate entirely — useful for estates above the $13.99M exemption — but the heir does not receive step-up basis. They inherit the original cost basis the grantor had when the assets were transferred into the trust. For long-held, deeply appreciated crypto, this can wipe out the tax efficiency the trust was meant to provide.

The decision rule: If your total estate is under $13.99M (single) or $27.98M (married), use a revocable trust. The estate tax does not apply, and you preserve step-up basis. If you are above the exemption and crypto appreciation is the primary driver pushing you above it, irrevocable trust strategies become defensible — but should be paired with a tax attorney's review, not a template.

The 1099-DA reporting gap for trust-held crypto

Form 1099-DA — the new digital asset broker report that started in 2026 — is built around individual taxpayer identification. When a US person opens a crypto account at Coinbase, Kraken, or Gemini, the broker collects their SSN, tracks their basis per wallet, and reports gains and losses to the IRS at year end. The reconciliation is automatic.

Trust-held crypto breaks this model. A revocable trust typically uses the grantor's SSN, so 1099-DA reporting still flows to the individual return — no gap. But irrevocable trusts use a separate Employer Identification Number (EIN), and most US crypto exchanges in 2026 have not built operational support for trust-titled accounts. The practical result is that many irrevocable trust holdings sit in self-custody wallets, with no broker reporting at all, and tax filings depend entirely on the trustee's own recordkeeping.

This is not a loophole — it is a documentation burden. The IRS still expects the trust to file Form 1041 annually and report any disposition. But without 1099-DA reconciliation, the trustee carries the full evidentiary load: per-lot basis records, transaction CSVs, on-chain transaction hashes, and FMV documentation at every taxable event. If the trustee fails to maintain these records, the IRS default position on audit is that the trust cannot prove basis — which means 100% of disposition proceeds may be treated as gain.

If you are establishing an irrevocable trust holding crypto in 2026, your trustee selection matters more than the legal structure. A trustee who does not understand wallet-level recordkeeping will lose money the structure was designed to save.

The decision framework

For most crypto holders, the framework reduces to four scenarios based on estate size and intent:

Scenario 1 — Estate under $13.99M, single beneficiary clarity: Use a revocable living trust. Crypto stays in your control during life, transfers without probate at death, heir receives full step-up basis, no estate tax. This covers the majority of US crypto holders.

Scenario 2 — Estate under $13.99M, multiple beneficiaries with different needs: Use a revocable trust with sub-trust provisions for each beneficiary. Same step-up benefit, but allows different distribution rules (lump sum vs. staggered, age-conditional, or charitable carve-outs).

Scenario 3 — Estate above $13.99M, crypto held under 5 years: Mixed strategy. Direct holdings or a revocable trust for crypto with low embedded gain (where step-up matters less), irrevocable trust for crypto with high appreciation if you want to remove it from the estate. Requires a tax attorney to model both paths.

Scenario 4 — Estate above $13.99M, crypto held over 5 years with deep appreciation: The hardest case. Irrevocable trusts remove estate tax exposure but kill step-up basis. Charitable remainder trusts (CRTs) and grantor retained annuity trusts (GRATs) become relevant — but only with specialized counsel. Do not use templates.

What to do this month

If you have crypto and no estate plan, the priority is not which trust to create — it is documentation. Without records, every structure fails on audit.

Step 1 — Create a wallet inventory. List every wallet, exchange account, and self-custody address. For each, record current balance, cost basis, acquisition date, and current location of private keys. Store this with your estate documents, not on a connected device.

Step 2 — Establish a key access plan. Step-up basis means nothing if your heirs cannot access the wallets. Use a multi-sig setup, a hardware wallet with sealed seed phrase in a safe deposit box, or a custodial service with documented inheritance procedures. Avoid sharing seed phrases in plain text.

Step 3 — Decide on revocable trust now. If your estate is under $13.99M and you do not have a revocable living trust, this is the action with the highest tax leverage per hour of effort. Cost: $1,500-$5,000 with an estate attorney. Benefit: probate avoidance plus preserved step-up basis.

Step 4 — Schedule a specialist review only if above the exemption. If your total estate is above $13.99M, this article is the starting point, not the answer. Find an estate attorney who has handled at least three crypto-inclusive estates. Ask specifically about their experience with EIN-titled trust wallets and 1099-DA reporting on Form 1041.

BOTTOM LINE

Step-up basis is the most valuable tax rule in US crypto inheritance. The 2026 IRS rules made it harder to claim by accident — and easier to lose by neglect.

For estates under the federal exemption, a revocable trust plus wallet-level documentation captures the full benefit. For estates above the exemption, the trade-off between estate tax and step-up basis is real and case-specific. Either way, the records you keep this year determine what your heirs receive next decade.

FAQ

Does step-up basis apply to crypto held in a self-custody wallet?

Yes, if the wallet is titled in the decedent's name (or a revocable trust the decedent controlled). The structure of custody — exchange account, hardware wallet, multi-sig — does not change the tax treatment. What matters is who owned the wallet legally and whether the heir can document fair market value at the date of death.

If I gift crypto to my children before death, do they still get step-up basis?

No. Gifts during life carry the donor's original cost basis forward (carryover basis). If you bought 1 BTC at $5,000 and gift it to your child when it is worth $80,000, your child's basis is still $5,000. Step-up basis only applies at death. For deeply appreciated crypto, holding until death is generally more tax-efficient than gifting during life — provided the estate stays under the exemption.

Does the 2026 federal estate exemption ($13.99M) include crypto at fair market value?

Yes. The IRS values crypto in the estate at fair market value on the date of death (or the alternate valuation date six months later, if elected). Bitcoin at $80,000 is counted as $80,000 per coin, the same as cash or publicly traded securities. Volatility before death is irrelevant for the estate calculation.

What happens if my heirs cannot access the wallet after my death?

The crypto remains part of the estate for tax purposes, but the heirs cannot realize it. They may still owe estate tax on the FMV at death even if the assets are unrecoverable. This is why key access planning matters as much as legal structure. The IRS does not refund estate tax on unrecoverable assets.

Can a foreign trust hold US crypto for estate planning?

Technically yes, but the rules are punitive. Foreign trusts holding US assets trigger Form 3520 and Form 3520-A reporting, throwback tax rules on accumulated income, and loss of step-up basis for US beneficiaries. For US persons, foreign trusts are rarely the right tool for crypto estate planning. Domestic structures are simpler and more tax-efficient.

Related Reading

Per-Wallet Cost Basis

1099-DA Mismatch Defense

About Davit Cho

Official IRS Resources

• IRS Digital Assets Hub
• Form 706 — United States Estate Tax Return
• Form 1041 — Trust Income Tax Return
• Form 1099-DA — Digital Asset Broker Reporting

Editorial perspective by Davit Cho. This article is for educational purposes only and does not constitute legal, tax, or financial advice. Estate planning involves jurisdiction-specific rules and individual circumstances; consult a licensed estate attorney and a CPA with crypto experience before making decisions. Tax law and IRS guidance change frequently — verify current rules with primary sources before acting.

When Your 1099-DA Doesn't Match: A Crypto Holder's Defense Playbook

CRYPTO TAX · IRS COMPLIANCE · DISPUTE

Davit Cho — Crypto Tax Researcher · CEO at JejuPanaTek (2012–) · Patent Holder #10-1998821 · Founder of LegalMoneyTalk

Published: April 30, 2026 · 13 min read · 100% Independent · Ad-Free

CRYPTO TAX · IRS COMPLIANCE

Your 1099-DA arrived. The numbers don't match your records. You have 72 hours before this becomes harder.

The IRS already received the same form. Their automated reconciliation engine already compared the broker's numbers against any return you've filed. If you do nothing, the broker's numbers become the default truth — and you spend the next 18 months explaining why your version is right. If you act in the next three days, the dispute becomes paperwork. After that, it becomes a defense.

📌 BOTTOM LINE — IN 60 SECONDS

• Don't ignore the form. The IRS got an identical copy and already cross-checked it.
• 4 mismatch types exist: wrong basis, wrong proceeds, missing transfers, duplicate reporting. Each has a different fix.
• 72-hour window is real. Verify in 24h, document in 48h, dispute or file with adjustment in 72h.
• Form 8949 has codes for this. Code B for basis, Code T for transfers, Code O for other — and you must use them, not just override numbers silently.
• Your goal is a paper trail, not perfection. A documented good-faith dispute is bulletproof. An undocumented "I just put the right numbers" is audit bait.

A 1099-DA That Doesn't Match Is Not a Mistake to Erase — It's a Negotiation You Just Entered

Most crypto holders, when they see a 1099-DA with the wrong cost basis or wrong proceeds, react in one of two ways. Either they panic and pay tax on the broker's number even though it's wrong. Or they ignore the broker's number entirely and quietly file Schedule D with their own correct figures, hoping nobody notices the gap.

Both reactions lose. The first overpays. The second creates a reconciliation flag that the IRS examiner system will catch automatically — because the broker filed the same form with the IRS, and the matching engine runs every return against every 1099-DA it received.

The correct frame: a mismatched 1099-DA is the start of a documented dispute. The IRS does not expect every broker form to be perfect. They expect taxpayers to either accept it, dispute it, or file an adjustment that's clearly explained on Form 8949. The third path is the one that wins — and it has rules.

The Four Types of 1099-DA Mismatches (And Why Each Needs a Different Fix)

Type 1 — Wrong Cost Basis

The broker reports a cost basis lower (or sometimes higher) than your actual basis. This is the most common mismatch in 2026 because brokers don't have your full transfer history — they only know what was deposited into their platform, not what you originally paid for it elsewhere. Fix: File Form 8949 with Column (e) showing the broker's reported basis, Column (g) showing your adjustment, and Code B in Column (f). Your dispute paper trail is the chain of records proving your real basis (purchase invoice, original exchange CSV, on-chain transfer hash).

Type 2 — Wrong Proceeds

The broker reports gross proceeds higher than what you actually received. Common cause: the broker's price feed used a different reference price than the actual execution price, or fees weren't netted properly. Fix: File Form 8949 with the broker's proceeds in Column (d), your adjustment in Column (g), and Code O in Column (f). Attach a statement explaining the proceeds discrepancy and reference your trade confirmation showing the actual execution price.

Type 3 — Missing Transfer Information

You transferred crypto into the broker from a self-custody wallet or another exchange. The broker had no idea where it came from, so they reported a basis of zero — or worse, they used the deposit-day market price as the basis. Fix: File Form 8949 with Code T in Column (f) and your real basis in Column (g). Provide the original acquisition record (the wallet, exchange, or transaction that established your original basis) along with the on-chain transfer evidence linking the two.

Type 4 — Duplicate Reporting

Two brokers reported the same disposition. Most common case: you transferred crypto between exchanges and one of them treated the outbound transfer as a sale. Or a broker double-reported because of an internal accounting reset. Fix: Identify the duplicate, file Form 8949 reporting the genuine transaction once, and attach a statement identifying the duplicate 1099-DA and explaining why it was a non-taxable transfer rather than a disposition. Keep both 1099-DAs in your audit file.

Critical rule:

For every mismatch, the broker's reported number goes on Form 8949 first. Your correct number does not replace it. Your correct number appears as an adjustment in Column (g) with the appropriate code in Column (f). This is the difference between "documented dispute" and "silent override" — and the IRS reconciliation engine treats them as completely different events.

The 72-Hour Response Timeline

Hour 0–24: Verify the Mismatch Exists

Pull the actual 1099-DA from the broker's tax center (don't rely on a forwarded email screenshot). Open your own per-lot ledger. Compare every transaction line by line — date, asset, units, basis, proceeds. Note every discrepancy. Most "mismatches" turn out to be one of three things: (a) genuine broker error, (b) a different lot-selection method between you and the broker, or (c) a transfer the broker treated incorrectly. Identifying which one matters because the fix differs.

Hour 24–48: Document the Source of Truth

For every disputed line, gather the underlying records that prove your version: original exchange CSV showing the purchase, on-chain transaction hash for the transfer, trade confirmation showing the execution price, wallet snapshot at the relevant date. Save them in a single timestamped folder. The folder is your defense — not the spreadsheet you build from it. Examiners ask for sources, not summaries.

Hour 48–72: Decide — Dispute With the Broker or Adjust on Form 8949

If the deadline allows and the error is clearly the broker's (e.g., wrong proceeds price), submit a written correction request to the broker's tax department asking for a corrected 1099-DA. Most major brokers (Coinbase, Kraken, Gemini) have a formal correction process. If the broker won't issue a correction, or if the deadline is tight, proceed to file your return with Form 8949 adjustments using the appropriate codes. Both paths are legitimate. The path you don't take is "silently file with my numbers and hope."

Beyond 72 Hours: Why Speed Matters

Once you file the return, your dispute path narrows. Pre-filing, you can request a corrected 1099-DA. Post-filing, you're in amendment territory (Form 1040-X) which is more visible to examiners and harder to win quickly. The 72-hour window is not a legal deadline — it's the practical window where you still have all the dispute paths available before filing forces you into a single one.

Form 8949 Adjustment Codes: B, T, O — Use Them Correctly or Trigger an Audit

Form 8949 Column (f) accepts a one- or two-letter code that tells the IRS examiner what kind of adjustment you're making. The codes most relevant to crypto 1099-DA disputes are these three.

Code B — Basis Reported Incorrectly

Use Code B when the broker's reported cost basis (Column e) is wrong and you are correcting it via Column (g). This is the workhorse code for crypto disputes because basis errors dominate the mismatch landscape. The IRS examiner sees Code B and knows: "the taxpayer agrees with the proceeds but disputes the basis." That's a routine adjustment, not a red flag — provided your supporting records are clean.

Code T — Form 1099-DA Reports Incorrect Type or Information

Use Code T when the form misclassifies the transaction — most commonly when an inbound transfer was reported as if it were a purchase, or an outbound transfer was reported as if it were a sale. Code T is the proper signal for "this isn't actually a taxable event the way the broker reported it." Pair it with a clear adjustment statement so the examiner doesn't have to guess what was reclassified.

Code O — Other Adjustments (Including Proceeds Errors)

Code O is the catch-all when neither B nor T fits — typically used for proceeds discrepancies, fee netting issues, or wash-sale-adjacent fact patterns specific to crypto. Code O carries slightly more examiner attention than B because it's less common, so always attach a written statement explaining what was adjusted and why. Without the statement, Code O looks ambiguous and invites a follow-up letter.

The unbreakable rule:

Never silently override broker numbers without a code. Filing Schedule D with "your" basis when a 1099-DA shows a different basis, with no Code B and no adjustment, is the exact pattern that triggers the IRS automated mismatch letter (CP2000). The mismatch letter is recoverable, but it costs you 6–12 months and a documentation back-and-forth that the Code B path avoids entirely.

The Audit Defense File: Six Folders That End the Dispute

If you do every other step right but lose the documentation, you lose the dispute. If you keep clean documentation, every other step becomes survivable — even if you make a small error somewhere. The audit defense file is the single most important deliverable in the whole process. Six folders, organized in this order:

• Folder 1 — Broker 1099-DA. The original PDF or downloaded file from the broker's tax center. Keep the unedited version exactly as received.
• Folder 2 — My Ledger. Your per-wallet, per-lot ledger reflecting your actual basis and proceeds for the disputed transactions.
• Folder 3 — Source CSVs. The original transaction exports from every relevant exchange and wallet. Raw, unmodified files.
• Folder 4 — Dispute Letter. If you submitted a correction request to the broker, the request and any reply.
• Folder 5 — Corrected 1099-DA. If the broker issued a correction, the corrected form (and proof of the original).
• Folder 6 — Form 8949 Worksheets. The line-by-line worksheet showing how each adjustment was calculated, with code, amount, and source reference.

When the IRS sends a CP2000 mismatch letter (and they will, for any unflagged adjustment), you respond by referencing this folder structure. Most CP2000s are resolved with a single-page reply when the file is clean. Without the file, the same letter becomes a months-long discovery process where you reconstruct what should have been documented at the time.

BOTTOM LINE

A mismatched 1099-DA is not a problem to hide. It's a process to document.

The IRS expects errors. They don't expect cover-ups. The taxpayers who lose are the ones who silently file with their own numbers, hoping the mismatch doesn't trigger anything. The taxpayers who win are the ones who treat the mismatch as a documented dispute from minute one — verify the numbers, gather the records, file Form 8949 with the right code, and keep the six-folder file ready. The win isn't perfection. It's the paper trail.

Quick FAQ

Q: Can I just file Schedule D with my correct numbers and ignore the broker's 1099-DA?
No. The IRS receives the same 1099-DA the broker sent you, and their automated reconciliation engine compares it against your Schedule D. A silent mismatch generates a CP2000 letter automatically. Filing the broker's number on Form 8949 with a Code B (or T or O) adjustment is the documented path that avoids the letter.

Q: How do I request a corrected 1099-DA from a broker like Coinbase or Kraken?
Each major broker has a tax-specific support channel. Submit a written correction request that identifies the specific transaction (date, asset, units), states the broker's reported value, your value, and the source records that support your version. Keep a copy of the request and any reply. If the broker refuses or doesn't respond before your filing deadline, proceed with Form 8949 adjustment instead.

Q: What if the basis is missing entirely on the 1099-DA because I transferred crypto in?
This is Type 3 (Missing Transfer Information). Use Code T on Form 8949 and supply your real basis in Column (g) using your acquisition records — original exchange CSV, on-chain transaction hash showing the original purchase, or wallet record. Code T tells the IRS the broker didn't have visibility into the transfer, which is a legitimate, common situation in 2026.

Q: What's the penalty if I don't dispute and just pay tax on the broker's wrong number?
No legal penalty — but you've voluntarily overpaid tax on phantom gains. You can file an amended return (Form 1040-X) within three years to claim the refund. The dispute process is far cleaner before filing than after.

Q: Can the IRS audit me purely because of a 1099-DA mismatch?
The first response is not an audit — it's a CP2000 mismatch notice, which is automated. A CP2000 is resolvable through written reply with documentation in the vast majority of cases. An actual audit is a separate, escalated process that's rare unless the documentation reply is missing or contradictory. This is precisely why the six-folder defense file matters.

Related Reading

Per-Wallet Cost Basis Migration

Powell FOMC & Tax Window

About Davit Cho

Official IRS Resources

• Form 8949 instructions (adjustment codes)
• Form 1099-DA instructions
• Understanding your CP2000 notice
• IRS Digital Assets hub

Editorial perspective by Davit Cho. LegalMoneyTalk is an independent ad-free research publication. This article is for educational purposes and reflects general analysis of IRS guidance and Form 8949 instructions as of April 2026. It does not constitute tax, legal, or investment advice. Consult a crypto-specialized CPA or tax attorney for your specific situation.

Why Search-Invisible Content Wins AI Traffic in 2026

EDITORIAL · CONTENT STRATEGY · GEO

Davit Cho — Crypto Tax Researcher · CEO at JejuPanaTek (2012–) · Patent Holder #10-1998821 · Founder of LegalMoneyTalk

Published: April 30, 2026 · 11 min read · 100% Independent · Ad-Free

A NOTE FROM THE EDITOR

Some posts have zero search traffic — yet they keep pulling AI traffic. Why?

A page can sit on the third page of Google for its target keyword and still get cited daily by ChatGPT, Perplexity, and Google AI Overview. It looks impossible if you think AI searches the way humans do. It doesn't. AI doesn't type three words into a box. It takes one user question and shatters it into a dozen sharp sub-queries running in parallel. And then it picks the page that answers one of those sub-queries with surgical precision — even if that page was invisible in normal search.

📌 BOTTOM LINE — IN 60 SECONDS

• AI doesn't search by keyword. It decomposes a user question into 5–15 specific sub-queries and runs them in parallel.
• Pages can win AI traffic with zero search ranking. What matters is whether one paragraph precisely answers one sub-query.
• The Search Console signal is visible. Unusually long, condition-laden queries appearing in your reports are AI crawler traces — not human searches.
• Three principles win: embed sub-queries verbatim, write self-contained paragraphs, use conditional structure ("If X → then Y").
• The game changed: stop optimizing for ranking. Start optimizing for paragraph-level extraction.

The Anomaly: Posts With Zero Search Traffic, Yet AI Citations

Look at any active blog with detailed long-form content and you'll find them. Pages that never rank on Google. Pages where Search Console shows almost no organic clicks. Pages that, by every conventional SEO metric, are dead weight.

And yet — when you check ChatGPT Browse, Perplexity, or Google's AI Overview, those exact pages keep appearing as cited sources. Sometimes daily. The page is invisible to humans typing keywords into Google, but visible to AI engines synthesizing answers.

This isn't a bug. It's the new structure.

Conventional SEO assumed one game: rank high enough on a short keyword to get clicks. AI citation runs a different game entirely — and the two games reward different content shapes. Once you understand the second game, the "search-invisible but AI-cited" pattern stops looking strange and starts looking predictable.

How AI Actually Searches (It's Nothing Like Humans)

When a human user types a question into Google, they type 2–4 words. "1099-DA filing." One short keyword, one search, one ranked list of results, one click.

When the same user asks ChatGPT, "I sold BTC across three wallets in 2026 — do I owe tax differently now?" the AI does not type that whole sentence into Google. Internally, it does something the user never sees: it breaks the question down into a set of specific, condition-laden sub-queries and runs all of them in parallel.

For that one user question, the AI's internal sub-queries might look like this:

AI INTERNAL SUB-QUERY EXPANSION

→ per-wallet cost basis 2026 IRS rule

→ Rev Proc 2024-28 safe harbor election deadline

→ 1099-DA Schedule D reconciliation mismatch

→ FIFO default per-wallet allocation

→ cross-wallet BTC sale audit defense

→ Dec 31 2025 snapshot documentation

→ specific identification election BTC multiple wallets

→ IRS digital asset broker reporting timeline

No human types queries like that. They are too long, too specific, too conditional. But for an AI engine, they are exactly the right shape — because each one targets a single piece of factual content that can be extracted, verified against other sub-queries, and assembled into a coherent answer.

The AI is not asking, "what page ranks best for 'crypto tax'?" The AI is asking, "what paragraph somewhere on the internet most precisely answers this exact sub-question?" Those are completely different evaluation criteria, and they reward completely different content.

The Search Console Signal: Spotting AI Crawler Traces

If you run Google Search Console on any active blog, open the Performance report and sort queries by length. Most of your queries will be short — 2 to 4 words, recognizably typed by humans. But scroll down and you'll start seeing queries that look strange.

Long, oddly structured strings. Multiple conditions stacked together. Highly specific noun phrases joined with abstract connectors. Things like:

• "rev proc 2024-28 path c default per-wallet documentation requirement"
• "how does 30 year treasury yield breakthrough affect bitcoin tax loss harvesting timing"
• "can you elect specific identification after filing 2025 return crypto"
• "FOMC dissent vote impact crypto market sell the news pattern history"

Ask yourself the simple test: does this look like something a human would type?

If the answer is no, you are looking at AI crawler traces. The AI engine generated that sub-query internally, ran it against the search index, found your page, and pulled a paragraph from it for citation. The "impression" appears in Search Console because Google logged the query — but the "click" never comes, because there was no human on the other end. The AI absorbed your content and moved on.

The diagnostic question:

For each unusual long-tail query in your Search Console: "Could a human plausibly type this exact string?" If no, it's an AI sub-query. The page that ranked for it is doing AI work — even if no human ever clicks.

How AI Extracts: Paragraphs, Not Articles

Here is the second insight that flips conventional SEO thinking on its head: AI engines almost never cite an entire article. They cite a paragraph. Sometimes a single sentence. Occasionally a list item.

When Perplexity says "according to LegalMoneyTalk," it's not pointing at the whole 2,000-word essay. It's pointing at the one paragraph inside that essay that contained a self-contained, verifiable answer to the sub-query the AI was running. The other 1,950 words were ignored.

This means a paragraph that wins AI citation has a specific shape:

• Self-contained. The paragraph stands on its own. You don't need to read the article around it to understand the answer. Pronouns are minimized. Antecedents are explicit.
• Conclusion before reasoning. The first sentence states the answer. The next sentences justify it. AI engines extract from the top down — if the conclusion isn't in the first 1–2 sentences, the paragraph gets passed over for one that's clearer.
• Concrete enough to be verified. Specific numbers, named regulations, exact dates, real entities. Vague paragraphs ("many holders may want to consider…") fail because they cannot be cross-checked against other sub-queries.
• Includes the exception. The strongest cite-worthy paragraphs note the case where their rule does not apply. AI engines reward this because exceptions are how they verify a source's reliability.

A 2,000-word post written as one continuous flowing argument loses to a 600-word post built as eight tightly self-contained paragraphs — even if the longer post is "better" by traditional editorial standards.

The Three Principles of AI-Citable Writing

Principle 1 — Embed sub-queries verbatim in your headers and FAQ

Whatever sub-query you imagine the AI generating, put that exact phrase as an H2, H3, or FAQ question. Not a paraphrase — the literal phrase. AI engines match string-similarity heavily on headings and FAQ blocks. A header that reads "Can you elect specific identification after filing your 2025 return?" wins citations that "Lot-selection elections after the fact" never will, even though they mean the same thing.

Principle 2 — Write paragraphs that work as orphans

Every paragraph should be liftable. If the AI engine extracts paragraph 7 from your article and shows it to a reader who has never seen the rest of the page, can that reader still understand the answer? If not, the paragraph is too dependent on context. Rewrite it to repeat the key noun ("the safe harbor election" instead of "it"), state the conclusion in sentence one, and end with the qualifier or exception.

Principle 3 — Use conditional structure ("If X → then Y")

AI sub-queries are themselves conditional in structure. They look like "what happens when [condition A] and [condition B]?" Content that mirrors this structure — explicit if/then statements, status-based decision branches, "by filing status" sections — matches AI sub-queries with much higher precision. Replace narrative paragraphs ("usually it depends on…") with explicit decision branches ("if you filed without an election → you defaulted into Path C; if you filed with one → keep the statement on file").

How to Retrofit Your Existing Posts (90 Minutes)

You don't need to rewrite your archive. You need to make targeted surgical edits to your top 10 posts. The retrofit process per post takes about 9 minutes:

1. (2 min) Identify likely sub-queries. For each post, list 5–8 specific questions the post implicitly answers. Write them as full sentences with conditions, not keywords.
2. (2 min) Convert 2–3 of them into H3 headers inside the post — verbatim phrasing, not paraphrase.
3. (3 min) Add a 4-question FAQ block at the bottom using the remaining sub-queries as the questions. Each answer 2–4 sentences, self-contained.
4. (2 min) Audit the first sentence of every paragraph. Each should state the conclusion of that paragraph. Rewrite any opening sentence that buries the lede.

Ten posts retrofitted this way, over a single 90-minute block, will outperform an entire month of new content for AI citation purposes. The reason: AI engines re-crawl and re-index continuously, and structural improvements to existing pages compound across every sub-query the engine runs against your domain.

BOTTOM LINE

Stop optimizing for ranking. Start optimizing for paragraph extraction.

The pages that win AI traffic in 2026 are not the pages that rank highest. They are the pages with the highest density of self-contained, verifiable, condition-shaped paragraphs that match the sub-queries AI engines generate internally. Search-invisible doesn't mean AI-invisible. Sometimes it means the opposite — that the page was written with surgical precision instead of broad-keyword targeting. The Search Console anomalies you see now are the new signal. Read them. They are telling you exactly what AI engines want, in their own voice.

Quick FAQ

Q: How do I know if a Search Console query came from AI vs a human?
The simplest test is plausibility: could a human realistically type this exact string into a search box? If the query is over 8 words long, contains stacked conditions, or uses overly formal noun phrases, it's almost certainly an AI sub-query — particularly if it has impressions but zero clicks.

Q: Does this mean traditional SEO is dead?
No — Google organic still drives the majority of discovery for most niches. But traditional SEO and AI citation are now two different games rewarding different content shapes. The good news: structurally clean, paragraph-based writing wins both. Keyword-stuffed thin content loses both.

Q: Should I write shorter posts to make AI extraction easier?
Length isn't the issue — paragraph independence is. A 3,000-word post built as 30 self-contained paragraphs wins more AI citations than a 600-word post built as one flowing argument. Write as long as the topic deserves, but make every paragraph liftable.

Q: How long until retrofitted posts show measurable AI traffic?
Search Console signal (long-tail AI queries appearing) typically shows within 2–4 weeks of structural updates. Direct AI citation (Perplexity, ChatGPT Browse showing your URL) is harder to attribute but generally follows within 4–8 weeks for well-structured content on a domain with existing authority.

Related Reading

The GEO Era

Reader-First Framework

About Davit Cho

Editorial perspective by Davit Cho. LegalMoneyTalk is an independent ad-free research publication. This article reflects observed search behavior and content patterns from operating LegalMoneyTalk through 2025–2026 and does not constitute marketing or technical SEO advice for specific platforms.

Per-Wallet Cost Basis Migration: The IRS Guide Most Crypto Holders Got Wrong in 2026

CRYPTO TAX · IRS COMPLIANCE

Davit Cho — Crypto Tax Researcher · CEO at JejuPanaTek (2012–) · Patent Holder #10-1998821 · Founder of LegalMoneyTalk

Published: April 30, 2026 · 12 min read · 100% Independent · Ad-Free

CRYPTO TAX · IRS COMPLIANCE

On January 1, 2026, the IRS quietly ended an era. Most crypto holders are still migrating like it never happened.

Universal cost basis — the convenient pool that let you mix coins across every wallet and exchange — is dead. In its place: per-wallet, per-account, per-lot tracking, enforced by the new 1099-DA reporting regime. The bad news: if you didn't make a safe harbor election by your 2025 return, the IRS chose your method for you. The good news: there's still time to document it correctly. Here's how.

📌 BOTTOM LINE — IN 60 SECONDS

• Universal cost basis ended Jan 1, 2026. You must now track cost basis per wallet, per account, per lot.
• Rev. Proc. 2024-28 required a safe harbor election with your 2025 return — Global Allocation, Specific Unit Allocation, or default.
• If you did nothing, the IRS treats you as defaulting into FIFO per-wallet for 2026 onward.
• 1099-DA arrives in 2026. Brokers report per-account. Mismatches with your filings flag audits.
• The migration isn't optional. Document a Dec 31, 2025 snapshot, allocate every lot, save every CSV. This article is your audit-proof workflow.

What Just Changed (And Why Most Holders Missed It)

For years, most crypto holders treated cost basis as one big pool. Bitcoin bought on Coinbase in 2018, BTC moved to a Ledger in 2021, BTC sent to a Kraken account in 2023 — all averaged together, all FIFO'd against the oldest lot regardless of where it actually sat. The IRS tolerated this because there was no realistic alternative. Brokers didn't report. Wallets didn't talk to each other. Pooling was the only thing that worked.

That tolerance ended on January 1, 2026.

Three things changed at once:

1. Per-wallet basis became mandatory. Under the final regulations implementing IRC §1012(c), cost basis must now be tracked separately for each wallet, account, or address you control. The "universal pool" is no longer recognized for transactions on or after Jan 1, 2026.

2. Brokers began reporting on Form 1099-DA. Centralized exchanges (Coinbase, Kraken, Gemini, etc.) now issue 1099-DA forms reporting your gross proceeds per account starting with 2026 transactions. The IRS will match these against your Schedule D. Mismatches are audit triggers.

3. Rev. Proc. 2024-28 imposed a one-time election deadline. Every taxpayer holding crypto on Jan 1, 2026 had to choose how to migrate their pre-2026 unused basis into the new per-wallet world — and that choice had to be documented with their 2025 return.

Most retail holders missed item three entirely. Tax software defaulted them. CPAs without crypto specialization let it slide. The result: thousands of returns filed with no documented allocation, leaving the holder exposed when 2026 1099-DAs start arriving with numbers that don't reconcile.

The Safe Harbor Election: Three Paths You Already Took (Knowingly or Not)

Rev. Proc. 2024-28 gave taxpayers three options for migrating pre-2026 unused cost basis into the per-wallet system. Whether you actively chose one or not, you ended up in one of these three paths.

Path A — Specific Unit Allocation (the strategic choice)

You assigned each pre-2026 unused unit of crypto to a specific wallet, by lot, by acquisition date. Highest-cost lots can be placed in wallets you plan to sell from soon (minimizing future gain). Lowest-cost lots can be placed in long-term hold wallets. This requires a written allocation statement attached to the 2025 return and full per-lot documentation. Best for: holders with multiple wallets and meaningful basis spread.

Path B — Global Allocation (the simple choice)

You allocated pre-2026 unused basis across wallets using a reasonable, consistent method (typically pro-rata by quantity). Less flexibility, less optimization, but vastly less paperwork. Still requires the election statement on the 2025 return. Best for: holders with one or two wallets and low complexity.

Path C — No Election (the default trap)

You filed your 2025 return without any allocation statement. The IRS treats this as defaulting into per-wallet FIFO from Jan 1, 2026 forward, with pre-2026 basis attached to whichever wallet held the units on Dec 31, 2025. This is where most holders ended up by accident. It's not catastrophic — but you've lost optimization flexibility, and your documentation burden is now higher, not lower, because you have to prove the Dec 31 snapshot from external records.

Critical clarification:

Even if you ended up in Path C by default, you are not exempt from documenting per-wallet basis going forward. The IRS just chose your starting allocation for you. Every transaction from Jan 1, 2026 onward still requires per-wallet, per-lot tracking on your end.

The 4-Step Migration Workflow

Whether you elected Path A, B, or defaulted into C, the operational workflow is the same. Skipping any step is what creates audit exposure later.

Step 1 — Inventory Every Wallet, Every Lot

List every place you hold crypto: centralized exchanges (Coinbase, Kraken, Binance.US, Gemini, etc.), self-custody hot wallets (MetaMask, Phantom, Rabby), hardware wallets (Ledger, Trezor), and any DeFi positions (staked, LP'd, lent). For each, pull the complete transaction history as a CSV. The IRS expects you to have this — not "approximately" but actually.

Step 2 — Snapshot December 31, 2025

Document the exact units held in each wallet at end-of-day Dec 31, 2025 UTC. This snapshot is your migration baseline. Without it, you cannot prove what was where on Jan 1, 2026 — and you cannot defend any per-wallet allocation later. If you didn't take the snapshot in real time, reconstruct it now from exchange CSVs and on-chain records before more time passes.

Step 3 — Allocate Per Your Safe Harbor Election

Apply the allocation method consistent with your election (or default). For each wallet, the result is a starting per-lot ledger: lot ID, acquisition date, original cost basis, units. This becomes the source of truth for every 2026 disposition.

Step 4 — Document for Audit

Save the inventory CSVs, the Dec 31 snapshot, the election statement (if filed), the allocation worksheet, and the resulting per-lot ledger together in one folder. Time-stamp it. The audit defense isn't the math — it's proving the math was done in good faith with contemporaneous records.

What "Audit-Proof" Actually Means

When the 2026 1099-DA forms hit IRS systems, an automated reconciliation runs against every Schedule D. If your reported gain on a sale doesn't match the broker's reported proceeds minus the basis you claim, the system flags it. From there, an examiner asks one question: "Show me how you calculated that basis."

A defensible answer requires six pieces of evidence:

• Wallet inventory — every account/wallet you held on Dec 31, 2025.
• Dec 31, 2025 snapshot — units per wallet at the migration date.
• Election statement — the actual document attached to the 2025 return (or proof of default).
• Per-lot allocation ledger — the resulting basis per lot per wallet on Jan 1, 2026.
• Source records — original exchange CSVs, on-chain transaction hashes, transfer records.
• Migration timestamp — when you did the work, ideally before any 2026 disposition.

Miss any one and the rest get weaker. Have all six and a 2026 audit becomes a paperwork exchange, not a battle.

What To Do Now (By Filing Status)

If you've already filed your 2025 return with an election: verify the election statement is in your records. Pull a copy from your tax software. Confirm the allocation method is documented and consistent with the per-lot ledger you're using for 2026 transactions.

If you've already filed without an election: you defaulted into per-wallet FIFO. This is recoverable but tighter. Reconstruct the Dec 31, 2025 snapshot now and lock in your per-wallet starting basis from external records. You cannot retroactively elect Path A or B, but you can still make every 2026 disposition cleanly defensible.

If you haven't filed yet (extension or late filer): you still have the election available. Don't file a bare return. Either consult a crypto-specialized CPA or, at minimum, attach a clear allocation statement before filing. Path A and Path B both require the statement to be in the filed return — not added later.

If you held crypto on Dec 31, 2025 but didn't sell anything in 2025: you still need the migration done. The election was about the migration baseline, not about a triggering sale. Holders who think "I didn't sell, so it doesn't apply to me" are the most exposed group when their first 2026 disposition flows through 1099-DA.

BOTTOM LINE

The migration already happened. The question is whether you documented it.

Per-wallet cost basis isn't coming — it's been the law since Jan 1, 2026. The 1099-DA reconciliation isn't theoretical — it's running. The safe harbor election deadline didn't get extended — it passed with your 2025 return. None of this is fixable by ignoring it. But all of it is still defensible if you do the inventory, the snapshot, the allocation, and the documentation now, before your first 2026 disposition gets flagged.

Quick FAQ

Q: Does this apply to NFTs and stablecoins?
Yes. Per-wallet basis applies to all digital assets defined under IRC §6045(g)(3)(D), including NFTs and stablecoins. The 1099-DA reporting scope is broad.

Q: What about DeFi wallets the IRS can't see?
Self-custody is not invisibility. You're still legally required to track per-wallet basis. The 1099-DA only covers broker-reported activity, but your Schedule D must include all dispositions across all wallets, broker or not.

Q: Can I switch from FIFO default to Specific ID later?
For lot-selection method on 2026 dispositions, yes — you can use Specific Identification on a per-disposition basis if you document the lots before the sale. But the safe harbor migration election (Path A vs B vs C) is locked once your 2025 return is filed.

Q: What's the penalty for getting it wrong?
Underreporting penalties apply if your basis is overstated. The bigger risk is reasonable-cause defense: without documented migration records, you can't show you tried in good faith — which removes a key audit defense.

Related Reading

Powell FOMC & Tax Window

Reader-First Framework

About Davit Cho

Official IRS Resources

• Rev. Proc. 2024-28 (full text)
• IRS Digital Assets hub
• Form 1099-DA instructions

Editorial perspective by Davit Cho. LegalMoneyTalk is an independent ad-free research publication. This article is for educational purposes and reflects general analysis of IRS guidance as of April 2026. It does not constitute tax, legal, or investment advice. Consult a crypto-specialized CPA or tax attorney for your specific situation.

The GEO Era: Why Hidden SEO Pages Are Dead and What AI Engines Cite in 2026

EDITORIAL · CONTENT STRATEGY

Davit Cho — Crypto Tax Researcher · CEO at JejuPanaTek (2012–) · Patent Holder #10-1998821 · Founder of LegalMoneyTalk

Published: April 30, 2026 · 10 min read · 100% Independent · Ad-Free

A NOTE FROM THE EDITOR

Generative engines don't cite hidden pages. They cite structured authority.

The playbook just changed. The hidden URL stuffed with AI keyword pages — the trick that worked from 2020 to 2024 — is dead. What replaces it isn't a clever SEO hack. It's a structural shift in what content survives, what gets cited, and what compounds. Here's what that shift looks like, and why it's already happening faster than most marketers realize.

📌 BOTTOM LINE — IN 60 SECONDS

• Hidden SEO pages are dead. Google's Helpful Content Update buried them. AI search refuses to cite them.
• What AI cites instead: structured GNB navigation, pillar pages, schema markup, brand-consistent depth.
• The new model: AI generates drafts at speed; humans architect the structure and own the quality.
• What you're really building: not "a blog" — an asset that compounds in two engines (Google + AI citation).
• The shift is faster than most marketers think. B2C budgets are already moving from influencer ads to authority-blog sponsorships.

The Old Playbook Just Died (Quietly)

From 2020 to 2024, the SEO playbook was simple. You spun up hidden URLs, stuffed them with AI-generated keyword pages, kept them disconnected from your brand's main domain, and let Google rank them on long-tail queries. The pages didn't need to be good. They needed to exist.

Then three things happened in succession.

Google's Helpful Content Update. Not just an algorithm tweak — a philosophical declaration. Pages that exist solely to rank, with no consistent author, no brand signal, no E-E-A-T scaffolding, started losing traffic by 60–90% almost overnight. Hidden URL strategies began collapsing in 2023, and the deletion accelerated through 2024 and 2025.

Generative search arrived. ChatGPT browse, Perplexity, Claude, Google's AI Overview. These engines don't behave like Google's old crawler. They synthesize answers from a small set of cited sources — and they're brutally selective about what those sources look like.

The marketing budget shifted. B2C marketers, watching their hidden-page traffic die while authority blogs kept growing, quietly started reallocating influencer ad budgets to WordPress sponsored posts on established sites. A 24-hour Instagram story for $5,000 versus a permanent placement on a domain-authority blog for the same price. The math wasn't subtle.

The playbook didn't die because someone announced it was dead. It died because the foundation it stood on — Google's tolerance for thin, disconnected content — was removed.

What AI Engines Actually Cite

If you've ever watched Perplexity answer a question, you've noticed something. Five citations under each response. Sometimes ten. Almost never twenty. The AI is not surveying the entire web. It's selecting a small handful of trusted sources and synthesizing from them.

Look at what the cited sources have in common:

• Clear navigation structure (GNB). The site's main menu tells the AI what the site is about. A blog with no top-level menu is a blog with no claimed expertise.
• Pillar pages with depth. Long-form anchor pages for major topic areas, with sub-articles linking back. The AI uses these to identify "this site is the authority on X."
• Schema markup signaling entity authority. Person schema, Organization schema, Article schema — these aren't decoration. They're the AI's primary input for understanding who wrote what and why it matters.
• Author-first E-E-A-T signals. A real person, with real credentials, writing across a coherent topic — visible across every page, not buried in a single About section.
• Brand-consistent depth. If your homepage is professional but your "/blog/keyword-stuffed-page-37" reads like 2019 SEO content, the AI doesn't trust the site. It trusts the weakest visible page.

None of this is hidden. None of it is gamed. It's the exact opposite of the old playbook — and that's the point.

The Real Shift: Two Engines, One Asset

Here's the part most marketers miss. We've spent fifteen years optimizing for one engine: Google. Now there are two.

Google still matters. Organic search still drives the majority of discovery for most niches. But a second engine has emerged — the AI citation layer — and it operates on a different logic. Google rewards ranking. AI citation rewards trustworthiness. They overlap, but they're not identical.

The crucial insight: both engines reward the same kind of content asset. Pillar pages with schema markup. Clear authorship. GNB-integrated topic clusters. Brand-consistent voice across the site. Build for one, you build for both. Build for neither, you build for nothing.

This is why the "hidden URL spam factory" approach broke. It optimized for ranking on a single engine, with no foundational structure. Now there are two engines, both demanding structure, and a content factory has nothing to offer either of them.

The marketers ahead of this shift aren't building "more content." They're building fewer, better, more structurally connected content assets — and they're letting those assets compound across both engines simultaneously.

Brand Asset vs. Exposure Page: The Compounding Difference

An exposure page is built to be seen once. It chases a keyword, gets a click, and decays. A brand asset is built to be cited repeatedly — by Google, by AI engines, by other writers, by your future self linking back to it.

The difference compounds. One exposure page in 2024 is invisible in 2026. One brand asset published in 2024 is still being cited by Perplexity, ChatGPT, and Google AI Overview today — and quietly pulling in backlinks from writers who needed a credible source.

The compounding test:

If your post disappeared tomorrow, would anyone notice? Would any AI engine lose a source? Would any reader bookmark it? If the answer is no on all three, you built an exposure page — not an asset.

What This Means For You in 2026

If you're running a blog, a brand, or a content operation, here's the operational shift:

1. Audit your hidden pages. Anything not linked from your GNB is invisible to AI citation engines. Either promote it into structure or retire it.
2. Build pillar pages. Pick 3–5 topic hubs. Each hub gets one definitive page that links down to 10–30 supporting posts. AI engines cite the hub.
3. Add schema everywhere. Article, Person, Organization, FAQ. AI engines parse schema before they read prose.
4. Let AI draft. You design. Speed matters, but structure compounds. The human role moves from typing to architecting.
5. Stop measuring impressions. Start measuring citations. Search "your name" in ChatGPT and Perplexity monthly. That's the new ranking signal.

BOTTOM LINE

The shift is not coming. It's already here.

Hidden SEO pages were a 2020–2024 tactic. In 2026, AI engines cite structured authority — pillar pages, schema, brand consistency, named experts. If you're still building pages to be found once, you're building on sand. Build assets that compound.

Related Reading

Reader-First Framework Powell FOMC Result About Davit Cho

Editorial perspective by Davit Cho. LegalMoneyTalk is an independent ad-free research publication. This article reflects personal observation of the 2024–2026 shift in search behavior and does not constitute marketing or legal advice.