Getting slashed is painful enough on its own. The follow-up question — can you deduct it? — has an answer that is honest but unsatisfying: probably not straightforwardly, and it depends on facts and legal questions that aren't fully settled.

This article explains the statutory framework under IRC §165, walks through the theory that CPAs most commonly apply (§165(c)(2)), and explains the two obstacles that make this more complicated than it first appears: the TCJA's suspension of miscellaneous itemized deductions, and the unresolved question of whether solo ETH staking qualifies as a trade or business. Where the law is unsettled, we say so. This is a topic where the answer matters financially and the legal ground is genuinely soft.

Educational disclaimer — read before continuing.

This article is educational and informational. It is not legal or tax advice and does not constitute a tax position for your return. The deductibility of staking losses under IRC §165 is an unsettled area of US tax law. No IRS revenue ruling, published agency guidance, or controlling federal court decision directly addresses slashing or inactivity-leak penalties as of this writing. The analysis below reflects CPA consensus and available statutory interpretation — not settled authority. Do not claim a §165 deduction for slashing losses without consulting a qualified tax professional and reviewing the specific facts of your situation. This is particularly important for tax year 2025 filings, where the TCJA's suspension of certain deductions has material practical effect.

What slashing actually does to your validator

When the Ethereum protocol slashes a validator — for a double-vote, a surround vote, or other slashable offense — it removes ETH directly from the validator's beacon-chain balance. The removal is immediate and on-chain: it appears in the consensus-layer record as a negative balance change at a specific epoch. The validator's effective balance drops, a portion is burned, and a portion is distributed to the reporting validator as an incentive payment.

An inactivity-leak penalty works differently but produces the same accounting result: ETH is removed from the validator balance over time during an extended period when the chain fails to finalize. Attestation penalties, which are smaller still, similarly reduce the validator's balance for missed or incorrect attestation duties.

From an accounting standpoint, each of these events reduces the value of an asset (or position) you hold. The tax question is whether that reduction is a deductible loss — and if so, how.

One thing slashing is not is a realized loss from a sale or exchange. The validator never sells the slashed ETH. The ETH is removed by the protocol. That distinction matters for the capital-loss analysis, as we'll explain below.

The IRC §165 framework

IRC §165(a) is the general rule: losses "actually sustained during the taxable year" and not compensated by insurance or otherwise are deductible — subject to anything else in the Code that limits or prohibits the deduction.

The important word is "subject to." For individuals (as opposed to corporations), §165(a) deductions flow through a limiting provision: §165(c). Under §165(c), an individual can deduct losses only if the loss falls into one of three categories:

1. §165(c)(1): A loss incurred in a trade or business.
2. §165(c)(2): A loss incurred in any transaction entered into for profit, though not connected with a trade or business.
3. §165(c)(3): A loss arising from a casualty or theft — but under TCJA, this category is now limited to losses from federally declared disasters (see IRC §165(h)(5)).

For most ETH solo stakers, the framework looks like this: you are running validators to earn staking income. That is either (a) a trade or business under §162, or (b) a transaction entered into for profit — the §165(c)(2) bucket. (The casualty/theft route, §165(c)(3), almost certainly does not apply to slashing because §165(h)(5) limits that category to federally declared disaster losses. Slashing is not a casualty or theft in the traditional sense, and even if it were, the personal-casualty-loss limitation blocks it.)

The threshold question — trade or business vs. transaction-for-profit — turns out to be decisive, for reasons that have nothing to do with §165 and everything to do with the TCJA.

The CPA-consensus theory: §165(c)(2) ordinary loss

The default framing among CPAs who advise stakers on this question is the §165(c)(2) approach: solo ETH staking is a "transaction entered into for profit," and a slash is a loss "actually sustained" in that transaction, fixed by an identifiable on-chain event.

Here is the reasoning in plain terms. You activated a validator to earn staking rewards — a clearly profit-motivated activity. The protocol slashed your validator and removed ETH from your balance. That removal is identifiable (the slash event appears on-chain at a specific epoch), it is completed (the ETH is gone; no further action is needed to crystallize the loss), and it is not compensated by insurance or any third party. Under Treas. Reg. §1.165-1, a deductible loss must be "evidenced by closed and completed transactions, fixed by identifiable events, and actually sustained during the taxable year." A slash event satisfies all three criteria.

Under the §165(c)(2) theory, the slash would produce an ordinary loss — not a capital loss. Capital losses require a sale or exchange, or the complete worthlessness of a security (§165(g)). A slash is neither: no sale occurs, and partial balance reductions don't satisfy §165(g)'s "wholly worthless" + "security" requirements. So if the loss is deductible at all under §165, the ordinary-loss path is the most coherent route.

This is the CPA-consensus default. It is not established authority. There is no IRS revenue ruling addressing slashing under §165. There is no published Chief Counsel Advice memo. IRS Notice 2014-21 — the primary agency guidance on virtual currency — is entirely silent on penalty treatment; it was issued in 2014 and addresses mining, not proof-of-stake validator mechanics. The §165(c)(2) theory is the best available statutory reading, not a position the IRS has validated.

The TCJA obstacle: §67(g) and the suspension of miscellaneous itemized deductions

Here is where things get practically difficult for tax years 2018 through 2025.

Under pre-TCJA law, §165(c)(2) losses were deductible as itemized deductions on Schedule A, subject to the 2% of adjusted gross income floor that applied to miscellaneous itemized deductions (IRC §67(a)). The TCJA added §67(g), which suspends all miscellaneous itemized deductions for individual taxpayers for tax years 2018 through 2025. This includes deductions that were previously available under the 2%-floor regime.

The question for stakers is whether §165(c)(2) slashing losses fall into the category of deductions suspended by §67(g). The answer is almost certainly yes — absent trade-or-business status under §162.

Here is the chain: §165(c)(2) losses are itemized deductions. The IRS has historically treated §165(c)(2) "for profit" transaction losses as miscellaneous itemized deductions subject to the 2% floor (see Treas. Reg. §1.67-1T). §67(g) suspends miscellaneous itemized deductions through 2025. Therefore, a §165(c)(2) slashing loss likely cannot be deducted by an individual on a 2018–2025 return, unless the activity rises to the level of a §162 trade or business — in which case §165(c)(1) applies instead, and those losses are not miscellaneous itemized deductions.

This is the crux. The practical question for most solo stakers in the 2025 filing year is: the §165(c)(2) theory may be legally coherent, but §67(g) likely blocks the deduction at the itemized-deduction stage. The TCJA's suspension of miscellaneous itemized deductions runs through the end of 2025. Whether it is extended beyond 2025 is a legislative question that remains open.

(For tax year 2026 and later, the §67(g) suspension is currently scheduled to expire — meaning the 2%-floor miscellaneous-deduction regime would return. If it does, §165(c)(2) losses would again be deductible as itemized deductions, subject to the 2% floor. But this depends on Congress, and Congress has repeatedly deferred decisions about expiring TCJA provisions.)

The §162 trade-or-business question — and why it matters enormously

The one path around §67(g) is §162 trade-or-business status. If solo ETH staking constitutes a "trade or business" under IRC §162, then slashing losses would be deductible under §165(c)(1) — not as a miscellaneous itemized deduction subject to §67(g)'s suspension, but as an ordinary trade-or-business loss, deductible above the line.

This is the cleanest statutory path. But it opens a different, significant problem.

Whether solo ETH staking rises to the level of a §162 trade or business is unsettled. The trade-or-business standard under §162 requires that the activity be conducted with continuity, regularity, and a profit motive — and courts have further required that the taxpayer's involvement be sufficiently active to constitute a business rather than merely a passive investment. For a solo validator operator who monitors validators, maintains node software, manages validator keys, and responds to performance alerts, a §162 argument is not obviously wrong. But it has never been tested in a context specific to ETH staking. The IRS has not issued guidance, and there is no published authority.

The reason the §162 question matters beyond §165 is self-employment tax (SE tax). If solo ETH staking is a §162 trade or business, staking income is subject to SE tax (currently 15.3% on net self-employment income up to the Social Security wage base, and 2.9% Medicare on amounts above it). That is a material additional tax liability — potentially larger than the value of the §165 loss deduction. A staker who claims §162 status to unlock a §165(c)(1) deduction for slashing losses may simultaneously be acknowledging SE-tax exposure on all their staking income.

This is a counsel-gated question. We do not assert that solo ETH staking is or is not a §162 trade or business. The consequences of getting this wrong in either direction are material: claiming §162 status when the IRS disagrees could expose you to SE-tax liability you didn't plan for; rejecting §162 status could leave you unable to deduct slashing losses in years where the §67(g) suspension blocks the §165(c)(2) path.

A penalty is not a realized loss: the distinction that matters

One framing that sometimes appears in staking-tax discussions is treating a slash as a "realization event" — as if the slash converts the slashed ETH into a recognized capital loss at the current FMV. This is not how §165 works.

Capital losses under the Code require a sale or exchange (for most assets) or the complete worthlessness of a security under §165(g). A slash event is neither. The validator did not sell ETH. There was no counterparty, no sale proceeds, no disposition. The ETH was removed by the protocol mechanics.

§165(g) does not save the capital-loss theory because §165(g) requires (a) a security and (b) complete worthlessness. A partial balance reduction from slashing satisfies neither criterion.

This distinction has a practical consequence: a slashing loss, if it is deductible at all, produces an ordinary loss under §165(c) — not a capital loss that offsets capital gains from ETH sales. The character matters for netting purposes.

How inactivity-leak and attestation penalties are different

Slashing penalties are discrete events: a single epoch, a fixed amount removed from the validator balance, attributable to a specific offense. Inactivity-leak penalties are different in character.

During an inactivity leak, the beacon chain fails to finalize, and validators suffer ongoing per-epoch balance reductions until finalization resumes. Each epoch's reduction is small (often a few hundred gwei per validator); the cumulative effect over a prolonged leak period can be material.

The §165 analysis applies to inactivity-leak penalties in principle — each period's reduction is an identifiable, completed event — but many practitioners treat inactivity-leak penalties operationally as a reduction to gross income rather than a separate deductible loss: because validators recognize staking income per-epoch (or at withdrawal), the leak simply reduces what was recognized, rather than requiring an independent §165 analysis. This framing is cleaner operationally and avoids the loss-characterization problem. Whether it is legally equivalent to the §165(c)(2) route depends on your recognition policy and timing — another question for counsel to review.

Attestation penalties (missed or incorrect attestations, small per-epoch reductions) are similar to inactivity leaks in character and are generally treated the same way in CPA practice.

What TrueStake does

TrueStake's data layer records each penalty event — slashing, inactivity-leak, attestation penalty — as a negative TaxableIncomeRecord with a wei amount and a timestamp fixed at the penalty event's UTC time. This approach is consistent with the CPA practice of recognizing the loss at the time of the identifiable on-chain event.

For slashing events specifically, TrueStake raises a SLASHING_S165_CARRYOVER finding that surfaces the question to you and your CPA. The system does not automatically compute a §165 loss carryover, and it does not make an automatic deductibility determination. The finding says: a slash occurred, here is the amount, here is the FMV at the event time, and this requires a §165 analysis with your tax professional.

This is deliberate. The deductibility question involves facts (is your staking a §162 trade or business?), legal unsettledness (there is no direct IRS guidance on slashing under §165), and timing (the §67(g) TCJA suspension has real practical effect through 2025). A system that automatically claimed a §165 deduction would be asserting a position the law has not resolved. A system that surfaces the finding and defers to counsel is doing the right thing.

What would change this analysis

The §165 analysis for slashing could shift materially if any of the following occur:

• The IRS issues a revenue ruling, Chief Counsel Advice memo, or other published guidance addressing slashing or inactivity-leak penalties under §165.
• Congress extends or modifies the §67(g) TCJA suspension — either extending it past 2025 (keeping the miscellaneous-itemized-deduction block in place) or allowing it to expire (restoring the 2%-floor regime).
• A federal court rules on the loss characterization of a blockchain-protocol penalty event.
• Pending legislation (such as S.2207 or the Digital Asset PARITY Act) is enacted, changing income recognition for staking rewards in ways that interact with the loss analysis.
• IRS guidance addresses whether solo ETH staking constitutes a §162 trade or business — which would resolve the §165(c)(1) vs. §165(c)(2) question and clarify the §67(g) obstacle.

We track legislative and regulatory developments quarterly in our research library and will update this article when material changes occur.

The bottom line

The honest summary:

There is a coherent statutory theory — §165(c)(2) ordinary loss for a transaction entered into for profit — that supports treating slashing as a deductible loss. CPAs working with stakers treat this as the default framework.

There is a significant practical obstacle — the TCJA's §67(g) suspension of miscellaneous itemized deductions, which likely blocks the §165(c)(2) deduction for individual filers through the 2025 tax year absent trade-or-business status.

The workaround — §162 trade-or-business status — is itself unsettled and carries material SE-tax implications that may outweigh the benefit of the §165 deduction.

No IRS guidance directly addresses this. You are operating in an area where the statutory framework exists but the IRS has not validated any specific reading for PoS validator penalty events.

What to do: document every slash event at the on-chain level — epoch, amount in wei, FMV at the event time. TrueStake records this automatically. Bring that documentation to a qualified tax professional before your 2025 filing. The question of whether to claim a deduction, and under which provision, requires a professional applying your specific facts to the law as it currently stands.

That is not a dodge — it is the accurate answer. The law is genuinely unsettled here, and the cost of getting it wrong in either direction is real.

Primary sources cited: IRC §165 (26 U.S.C. §165); IRC §67(g) (26 U.S.C. §67(g)); IRC §162 (26 U.S.C. §162); Treas. Reg. §1.165-1; IRS Notice 2014-21 (Mar. 2014); Rev. Rul. 2023-14 (Aug. 2023). Research basis: TrueStake tax research library file us-04-slashing-irc-165.md (status: counsel-required, last reviewed 2026-05-15). This article is educational and informational only — it is not legal or tax advice. The deductibility of staking losses under IRC §165 is an unsettled area of US tax law. Consult a qualified tax professional for guidance specific to your situation.