SAFT Recalibration
Recurring valuation of SAFTs is an operational challenge we often see in practice.
Recurring valuation is an operational challenge we often see in practice. SAFTs were often held at cost because teams lacked a practical framework to true them up between signing and token launch.
In our work, we used agentic AI tools to help build an SAFT valuation template that analyzes legal terms, identifies economic assumptions, assesses scenario outcomes, and incorporates calibration logic. The result is a structured operating model that web3 finance teams can use to update SAFT valuations in response to changes in the economic environment and the entity’s facts and circumstances.
A calibrated scenario model can help management estimate changes in fair value after acquisition. The process starts with the deal terms at inception, calibrates to the transaction price, then updates probabilities and outcomes at each reporting date. This produces a more defensible fair value estimate for SAFTs, even when token delivery remains contingent.
SAFT Recalibration Model
13.1KB ∙ XLSX file
This file shows an illustrative calculation of SAFT contract value recalibration in accounting periods subsequent to the investment.
By anchoring the model to the original transaction and updating assumptions at each measurement date, companies can build a more consistent and auditable fair value process. The approach gives finance teams a repeatable process where they previously had a valuation gap. It also applies calibration discipline to instruments that were often left at cost until a major event forced a reset.
Used properly, with appropriate governance, expert review, and quality control, agentic AI tools can help create structured data that captures contractual terms, improve documentation, and support more accurate financial reporting.
How to use the accrual method in the digital asset staking accounting?
Most web3 native companies recognize staking income at the time when corresponding rewards are deposited in their wallets. But should reporting entities accrue unclaimed staking rewards when earned?
Staking rewards are often recognized when they are claimed and received in the validator's or delegator's wallet. However, that approach is not always consistent with the accrual basis of accounting. Staking arrangements are highly fact-dependent, and entities often apply ASC 606 either directly or by analogy after evaluating the specific protocol and contractual terms.
When the facts support recognition before claim, the timing should be tied to the completion of the validation activities that give rise to the reward and to the point at which the amount of consideration becomes known or reasonably calculable under the protocol. For some networks, that may occur when a block is added to the blockchain. For others, the reward may remain constrained until the end of an epoch, era, or another protocol-defined period.
Subscribe
When rewards are recognized before receipt, an entity may need to record a right to receive tokens. Under ASC 606, that right is generally presented as a receivable when it is unconditional, or as a contract asset when it remains conditional. Noncash consideration is generally measured at fair value at contract inception, so subsequent changes in token prices due to the form of consideration do not affect the amount of revenue recognized.
Accounting for post-inception price changes depends on the specific fact pattern, including whether the contract contains an embedded derivative that must be bifurcated.
The spreadsheet solution below was designed to help validators and delegators track these moving parts in a single model and support an accrual basis of accounting for staking rewards:
You can access our staking accounting template here.
This model can be reused, but it will require customization to the specific features of the networks your company operates. If you are working on setting up an accrual process for staking rewards and have questions, please reach out.
FASB Wrapped Tokens, ASC 350-60, and Stablecoin Cash Equivalent Guidance
FASB advanced wrapped token accounting under ASC 350-60 and proposed broader cash equivalent disclosures that could apply to all entities, not just stablecoin holders.
The Board made several key decisions that could matter well beyond a narrow subset of digital asset holders:
Include wrapped tokens within the scope of ASC 350-60, which would allow them to be measured at fair value.
Add illustrative examples to the Codification explaining how the definition of cash equivalents should be applied in determining whether certain stablecoins should or should not be classified as cash equivalents.
Propose annual disclosures of significant components of cash equivalents that would apply to all entities.
At its April 15 meeting, the Financial Accounting Standards Board discussed staff research and stakeholder feedback on two projects: accounting for transfers of crypto assets and the classification of certain digital assets as cash equivalents.
First, the Board decided to expand the scope of ASC 350-60 to include certain economically similar crypto assets, including wrapped tokens and receipt tokens, under the same fair value model as other in-scope crypto assets. The Board also decided that wrapped tokens should be disclosed separately from the underlying crypto asset.
Second, the Board considered stakeholder requests for more detailed guidance on when digital assets may qualify as cash equivalents. Rather than revising the definition of cash equivalents in the Master Glossary, the Board chose to move forward with illustrative examples. That approach keeps the existing definition in place while giving preparers more direction on how the Board expects it to be applied. Based on the Board’s discussion, those examples are expected to reinforce a high threshold, including the importance of maintaining at least 1:1 reserves in cash or traditional cash equivalents, and of a direct, on-demand contractual right to a known amount of cash.
The Board also supported annual disclosure of the significant components of cash equivalents for all entities, extending well beyond the project’s original focus on stablecoins. Those decisions are expected to be reflected in an exposure draft for public comment with a 90-day comment period.
If your organization holds, for example, WBTC (or other wrapped tokens), those assets could fall within ASC 350-60 and be measured at fair value if the Board’s proposal is finalized. WBTC holdings would need to be disclosed separately from BTC holdings.
The Board has not yet made decisions on crypto transfer derecognition issues.
The Board did not change the current accounting policy election framework for cash equivalents. Your organization can elect an accounting policy to classify certain stablecoins as cash equivalents, as long as all applicable requirements set in the glossary definition of cash equivalents are met.
The proposed annual disclosure of significant components of cash equivalents could affect all entities, not just those with stablecoin-related fact patterns. In that respect, the proposal has a broader reach than the project title might initially suggest.