Skip to content

Invest Independently confirmed2 publishers 2 min read Published Updated

IRS lets listed crypto trusts stake under rules existing funds must adopt within six months

IRS Revenue Procedure 2026-20 lets exchange-listed crypto trusts stake and keep grantor-trust status, with six months for existing trusts to comply. Holders must receive the rewards in the same token or in cash, while the procedure leaves open how that income is taxed.

The Investor · Invest desk

How we use AI Send a correction

What happened

  • Rev. Proc. 2026-20 replaces Rev. Proc. 2025-31, the procedure that first set out a staking safe harbor for these trusts in November 2025.
  • A qualifying trust may hold only cash and units of one type of digital asset running on a permissionless proof-of-stake network.
  • Only the trust's custodians may control the staking addresses and private keys, and the IRS treats the trust as owning the tokens while they are staked.
  • Trusts generally must make their tokens available for staking but may keep a liquidity reserve unstaked when the trustee or sponsor judges exchange redemption rules require one.

Why it matters

  • decision A sponsor that also runs a staking business has to send its own trust's tokens to an unrelated provider, and the reward split is set at arm's length without it.
  • exposure Sponsors and custodians may only tell the provider when to stake or unstake, so the trust's staking results depend on operations it is barred from controlling.
  • cost Yield per token can differ between two trusts holding the same asset, because each sizes its unstaked reserve by its own reading of exchange redemption rules.

The legal basis for staking inside a grantor trust is a single characterisation. According to crypto.news's account of the procedure, the IRS treats staking as protecting and conserving trust property when it helps reduce the risk that one party or a coordinated group gains majority control over staked assets [11]. A trust meeting every condition can then stake and still count as an investment trust under Section 301.7701-4(c) and as a grantor trust [4]. It must hold both classifications before it starts [5].

Tracing one reward unit shows who gets paid. The custodians stake through one or more providers, and the division of rewards between provider and custodian has to be negotiated at arm's length [9]. What reaches the trust must be units of the token it already holds [12]. Those units, or the cash from selling them, then go to holders within the required timeframe [12].

Rewards therefore do not build up inside the fund, or rather, they sit there only briefly [12]. Newly received rewards are one of the categories a trust may hold unstaked for a time [14]. The others include tokens being sold for expenses or redemptions, tokens contributed for creations and tokens about to be distributed [14], plus liquidation, changes in law and steps to protect the assets [15].

The 2025 text lasted about 11 months [17]. Existing trusts can keep relying on it for six months from the Oct. 6 issue date [1][3], a window that closes around April 6, 2027 [18]. The crypto.news report does not list which conditions are new relative to the 2025 version, so the work each existing trust faces before April cannot be sized from it.

If existing trusts already use unrelated providers and pay rewards out, the six months is contract drafting, and most holdings end up staked under the new terms [3]. If some sponsors stake through affiliates, each has to choose between replacing the provider and losing the safe harbor [9][3]. I think the unrelated-provider rule moves more money than any other condition, because it decides who keeps the provider's cut of every reward [9]. The counter-case is the reserve. A sponsor that reads exchange redemption rules conservatively could leave enough tokens idle that the provider question matters less [13]. Large unstaked reserves described in existing trusts' SEC registration statements after April [6] would show I had the order wrong.

What to watch

  • Updated SEC registration statements from existing staking trusts before about April 6, 2027, showing whether they changed providers or reserve policies.
  • Any IRS guidance on how staking rewards distributed to trust holders are taxed, a question Rev. Proc. 2026-20 leaves outside its scope.
  • Whether any sponsor with an affiliated staking business gives up the safe harbor instead of moving to an unrelated provider.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence62
Adoption
Insufficient
Hype gap+5
Incentives
Insufficient
Confidence60
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Revenue Procedure 2026-20 was issued on Oct. 6 and its safe harbor applies to eligible trusts holding digital assets on permissionless networks that use proof of stake to validate transactions.

    Reported Supported Source: crypto.news, citing Rev. Proc. 2026-202 sources— create a free account to open themView cited source
  2. [2]

    Rev. Proc. 2026-20 replaces Revenue Procedure 2025-31, which introduced the original framework in November 2025.

  3. [3]

    Existing trusts have six months from Oct. 6 to adopt the revised requirements before they can no longer rely on the previous 2025 safe harbor.

Sources

2 independent publishers whose own reporting we read for this story.

  1. crypto.news

    1 article · October 6, 2026

    IRS lets qualifying crypto trusts stake assets without losing tax status
  2. cryptobriefing.com

    1 article · October 6, 2026

    IRS issues guidance on digital asset staking safe harbor for trusts

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Topics

Entities

Loading related stories