Revenue recognition for crypto transactions follows the same 5-step model that governs all revenue under ASC 606 (Revenue from Contracts with Customers) — but crypto introduces unique complexities: volatile transaction prices denominated in digital assets, performance obligations tied to token utility, and classification questions around staking and mining rewards. The framework determines when and how much revenue an entity reports from token sales, crypto-denominated services, mining operations, and crypto payments received for goods and services.
How Does ASC 606 Apply to Crypto Transactions?
ASC 606 applies whenever an entity transfers goods, services, or digital assets to a customer in exchange for consideration — including consideration received in cryptocurrency. As a foundational accounting standard for digital assets, its 5-step model provides the universal framework for determining revenue timing and amount.
Identify the contract
A contract exists when parties have approved the arrangement, rights and payment terms are identifiable, the arrangement has commercial substance, and collection is probable. Smart contracts, SAFTs, and token purchase agreements qualify when these criteria are met.
Identify performance obligations
Each distinct promise to transfer a good or service is a separate performance obligation. A token sale may include: delivery of the token, ongoing platform access, future feature development, or governance rights — each potentially a separate obligation.
Determine the transaction price
The transaction price is the amount of consideration the entity expects to receive. When consideration is in crypto, the fair value of the crypto received at contract inception determines the transaction price. Variable consideration (price-contingent releases, milestone payments) requires estimation.
Allocate the transaction price
When multiple performance obligations exist, the transaction price is allocated to each obligation based on relative standalone selling prices. A token bundled with 12 months of platform access requires allocation between the token delivery and the service period.
Recognize revenue
Revenue is recognized when (or as) each performance obligation is satisfied — either at a point in time (token delivery with no ongoing obligation) or over time (platform access, service contracts, hosting arrangements).
What Are Performance Obligations in Crypto Revenue?
Performance obligations in crypto revenue depend on the nature of the promise made to the customer. Token sales often bundle multiple promises — the token itself, platform functionality, governance participation, and future development — each requiring analysis to determine whether it constitutes a distinct performance obligation.
Common crypto performance obligations:
- Token delivery (point-in-time) — Delivering fungible tokens with no ongoing obligations. Revenue recognized upon transfer to the buyer’s wallet.
- Platform access (over-time) — Utility tokens granting access to a platform or service over a defined period. Revenue recognized ratably over the access period.
- Mining hosting contracts (over-time) — Providing hashrate, electricity, and infrastructure under a hosting arrangement. Revenue recognized as the service is delivered.
- Software licenses paid in crypto (point-in-time or over-time) — Depends on whether the license is a right-to-use (point-in-time) or right-to-access (over-time).
How Is Variable Consideration Handled for Crypto Revenue?
Variable consideration arises when the transaction price includes amounts that may change based on future events. In crypto, variable consideration occurs in 3 common scenarios:
- Price-contingent token releases — Token sale agreements where additional tokens are released if the market price drops below a threshold (price protection clauses)
- Performance-based staking rewards — Service contracts where the entity earns variable staking yields on behalf of customers
- Volume-dependent fee rebates — Exchange or platform fees that decrease as customer volume increases
ASC 606 requires estimation using either the expected value method (probability-weighted average of possible outcomes) or the most likely amount method (single most probable outcome). The estimate is subject to the constraint: revenue is recognized only to the extent that it is probable a significant reversal will not occur.
When Is Revenue Recognized for Token Sales?
Revenue recognition timing for token sales depends on the nature of the arrangement and whether performance obligations are satisfied at a point in time or over time.
| Token Sale Type | Recognition Timing | Key Factor |
|---|---|---|
| Simple token sale (no ongoing obligations) | Point-in-time — at token delivery | Transfer of control upon wallet receipt |
| SAFT (Simple Agreement for Future Tokens) | Deferred until token delivery | Revenue deferred as contract liability until TGE |
| Utility token with platform access | Over time — ratably over service period | Continuous transfer of benefit to customer |
| Governance token with no obligations | Point-in-time — at token delivery | No ongoing performance obligation |
| Token presale with vesting | Over time — as tokens vest and transfer | Control transfers at each vesting milestone |
SAFT agreements require particular attention. The entity receives cash or crypto consideration before the token generation event (TGE). Under ASC 606, the consideration is recorded as a contract liability (deferred revenue) because no performance obligation has been satisfied. Revenue is recognized at the TGE when tokens are delivered — or over time if the tokens carry ongoing obligations.
How Are Staking and Mining Rewards Classified?
The classification of staking and mining rewards depends on whether a customer contract exists under ASC 606. This distinction determines whether rewards are reported as revenue (top line) or as other income — with significant implications for financial statement presentation and valuation multiples.
| Account | Debit | Credit |
|---|---|---|
| Digital Asset Holdings (ETH) | $32,000 | — |
| Staking Revenue | — | $6,400 |
| Customer Staking Payable | — | $25,600 |
The entity recognizes $6,400 as revenue (its 20% fee) and records a liability of $25,600 payable to the customer. The full 10 ETH is recorded as a digital asset at fair value under ASU 2023-08, with subsequent fair value changes flowing through net income.
| Account | Debit | Credit |
|---|---|---|
| Digital Asset Holdings (SOL) | $400 | — |
| Other Income — Staking Yield | — | $400 |
Self-staking yield is not revenue under ASC 606 because no customer contract exists. The yield is recognized as other income at the fair value of the tokens received on the date of receipt. The mining revenue guide covers the parallel analysis for proof-of-work mining rewards.