Staking Rewards Under US GAAP

CryptoGAAP.com → Reference → Staking Rewards

1. Recognition timing

The dominant model recognizes staking rewards when the holder obtains control of the reward — when it is credited and the holder can transfer or otherwise direct its use. For most proof-of-stake protocols that is when rewards become available to the validator or delegator, assessed protocol by protocol. Where rewards accrue but remain locked or subject to slashing-style clawback until an epoch boundary or withdrawal event, recognition is generally deferred until the contingency lapses, by analogy to basic asset-recognition and contingency concepts (ASC 450 reasoning, applied to gains).

The unsettled edge: continuous block-by-block accrual versus discrete claim events. Entities with material staking operations disclose their policy; auditors care more that the policy is rational, consistently applied, and disclosed than which defensible point is chosen.

2. Measurement

Rewards are measured at the fair value of the tokens received at the recognition date, using ASC 820 principles — the same fair value discipline ASC 350-60 requires for subsequent measurement. That receipt-date fair value becomes the token's cost basis for the ASC 350-60-50-1 disclosure (units, cost basis, fair value) and for any future disposal computation. Subsequently, if the reward token meets the ASC 350-60 scope criteria, it is remeasured at fair value through net income each period like the rest of the position.

For tax, the GAAP receipt-date model happens to parallel IRS Revenue Ruling 2023-14, which includes staking rewards in gross income at fair market value when the taxpayer gains dominion and control — but book and tax timing can still diverge in detail (locked rewards being a common difference), so deferred tax tracking matters.

3. Presentation

Where the income lands depends on what the entity is:

• Validator-as-a-business (staking is an ordinary activity): rewards are typically presented as revenue. Whether the arrangement is in the scope of ASC 606 is debated — a protocol is not obviously a "customer" — and practice includes both ASC 606 framing (for staking-as-a-service contracts with identifiable customers) and other-income framing for protocol-direct rewards. State the basis in the policy note.
• Corporate treasury staking incidental holdings: rewards generally present as other income, outside revenue.
• Delegated and pooled arrangements: gross-versus-net is the open question — does the delegator recognize the gross reward and a fee expense to the operator, or the net amount received? The answer follows the rights in the specific arrangement (who controls the reward at the protocol level), and both presentations appear in current filings. Flagged honestly: this is an area of diversity with no authoritative answer.

Fair value changes on rewards after receipt are an ASC 350-60 remeasurement item, presented separately from the income recognized at receipt — keep the two lines distinct in the workpapers.

4. Liquid staking tokens

Liquid staking tokens (stETH-style) convert the staking position into a transferable claim on the staked asset plus accrued rewards — which makes them a wrapped-token problem, not a staking problem. Under current GAAP they generally fail the ASC 350-60-15-1(b) scope criterion; FASB's tentative April 15, 2026 scope expansion for tokens conveying rights to in-scope crypto assets would capture many of them. See wrapped token accounting for that analysis.

5. Documentation checklist

• Recognition policy: the control point, per protocol, and why.
• Pricing source and time convention for receipt-date fair value (ASC 820 hierarchy level).
• Presentation basis: revenue vs. other income; gross vs. net for delegated arrangements.
• Lockup and slashing exposure at each reporting date, and its recognition effect.
• Book-tax differences against the Revenue Ruling 2023-14 timing.