Token Valuation

Token FMV at December 31: What Your Auditor Will Ask

Pulley shuts down December 8, 2026. Its token customers have a measurement date three weeks later. This is what the year-end file has to answer.

The measurement date is fixed

For a calendar-year company, the token mark is measured as of December 31. The provider that delivered last quarter's mark closes on December 8.

The audit question is narrow. What evidence will your auditor accept for the number in the financial statements? The answer depends on three facts.

First, whether the token trades. A traded token starts from a market price. An untraded token starts from a model.

Second, how much of the supply is restricted. Lock-ups, vesting schedules, and transfer limits set how far a holder's position sits from the quoted price. They also decide which standard governs that gap.

Third, whether the entity that holds the equity is the entity that holds the token. If it is not, the equity value and the token value are one problem, not two.

The five questions auditors ask about a token mark

1. Is the observable price a fair value?

What they are checking. Whether the price came from the principal market, and whether that market is active. ASC 820 ranks inputs. A quoted price in an active market is Level 1. A price from a thin market is an input to adjust, not a conclusion.

A weak answer. "We used the aggregator close at midnight." It names no venue, no time zone, and no volume. The token trades every hour of December 31. Midnight UTC on January 1 is still December 31 in California. The file has to say which moment is the measurement point, and why.

A defensible answer. It names the venue. It shows volume and bid-ask spread around the measurement date. It states a cut-off time and uses the same one every quarter. If the market is thin, it explains the adjustment and classifies the input at the right level. It does not discount for the size of the position. ASC 820 does not permit a blockage factor on a Level 1 price.

2. How are lock-up and restriction discounts supported?

What they are checking. First, whether a discount belongs in the measurement at all. Then, whether its size has support.

The first part turns on purpose. Under ASC 820, a contractual sale restriction on an equity security is not part of the unit of account and is not discounted. The crypto asset guidance in ASU 2023-08 (ASC 350-60) applies the same principle to tokens the company holds. Under ASC 718, a restriction that continues after vesting can be reflected in an award's grant-date fair value. For tax value on a vest or distribution date, separate rules decide whether a restriction that will lapse counts at all. One token can carry different answers on one date.

A weak answer. A single discount cited to "studies." No link to the token's own unlock schedule or volatility. The same discount applied to every tranche, whatever its remaining lock-up.

A defensible answer. It starts from the unlock schedule. Each tranche is measured on its own remaining term. The discount comes from a model with stated inputs, such as a put-option approach using the token's own volatility. Observed trades in restricted units are used where they exist. Every input traces to a source the auditor can re-perform.

3. Pre-TGE: how did you handle probability and timing?

What they are checking. Before TGE there is no token price. The mark is a model of whether the token launches, when, and at what value. Auditors test each of those inputs separately.

A weak answer. The last SAFT round price, carried forward. Or a comparable project's post-TGE value, applied as if launch were certain and immediate. Both skip the two inputs that do most of the work.

A defensible answer. It sets out scenarios. A launch scenario has an expected date, a supply schedule at launch, and a value at launch. A delay scenario moves the date. A failure scenario states what SAFT and token warrant holders receive if no token issues. Each weight ties to evidence: milestones met, legal and listing workstreams, runway. The model is calibrated to the most recent SAFT or token warrant round, then rolled forward for what changed. If the weights move between quarters, the file says what evidence moved them.

4. Does the token mark agree with the equity 409A?

What they are checking. Whether two valuations of the same company tell the same story. When token rights sit on the cap table, the equity 409A has to carry a value for them. The token mark carries its own. The auditor reads both.

A weak answer. The 409A assumes TGE in the second quarter. The token mark assumes the fourth. The two use different supply figures and different discount rates. Nobody has compared them.

A defensible answer. One set of assumptions feeds both reports: TGE probability and timing, circulating and total supply, the treasury the company holds, and the obligations owed to SAFT and token warrant holders. Where the valuation dates differ, a short reconciliation bridges them.

This matters beyond the audit. The equity 409A sets option strike prices. Under IRC 409A, the presumption of reasonableness rests on a reasonable method applied by an independent appraiser. A token assumption that contradicts the company's own token mark is a weak point in that method.

5. Who signed, and where are the workpapers?

What they are checking. Whether a specialist the audit team can rely on stands behind the number. The engagement team, often with its own valuation specialists, evaluates the specialist's competence, objectivity, and work.

A weak answer. A PDF with a concluded value and no named signer. No model file. No data pulls. No one to call.

A defensible answer. A report signed by a named appraiser. A model available for review. Market data saved as pulled, with timestamps. Inputs that trace to documents: the SAFT, the token warrant, the RTU plan, the unlock schedule, the intercompany agreement. A signer who answers questions on this report and on the prior ones.

The DevCo/foundation problem

Many token companies split in two. A foundation issues the token and holds the treasury. A DevCo holds the team, the IP, and the venture equity.

In that structure, the equity holder's claim on the token is contractual. It runs through an intercompany agreement. Common forms are a token allocation agreement, a development services agreement, or a side letter. The agreement decides how many tokens DevCo receives, when, and under what restrictions.

The equity 409A cannot be done without it. DevCo's value includes whatever the agreement gives it. If the allocation is uncertain, the 409A models the uncertainty. If part of the allocation passes through to SAFT or token warrant holders, the 409A nets it out. A 409A that values DevCo as a software company and ignores the allocation misses an asset.

The auditor will ask for the agreement. They will read it for enforceability, timing, and delivery conditions. They will check that the valuation used the numbers the agreement states.

They will also ask about awards. Foundation tokens are often granted to DevCo employees as RTUs or token options. Under ASC 718, an award from a related party for services to the reporting entity is accounted for by the reporting entity. The token mark becomes DevCo's compensation expense.

Put these in the file before fieldwork:

What breaks when the prior provider disappears

The history. A December 31 mark does not stand alone. The auditor compares it to September 30 and earlier quarters. If prior reports and their inputs leave with the provider, the history is a column of numbers no one can explain.

The reconciliation. The new firm's first mark has to bridge from the last delivered mark. Price moved. A tranche unlocked. Supply changed. TGE timing shifted. A round closed. Each item explains part of the change. Whatever is left unexplained looks like a change in method, and the auditor will ask why the method changed. The new firm needs the prior inputs to build that bridge. Without them, it re-performs the prior mark from source documents.

The distribution date. Vesting and distribution events do not wait for a provider transition. Tokens delivered to employees are wage income at fair market value on the delivery date. The company withholds on that value. If a distribution falls between December 8 and December 31 and no mark exists for that date, payroll has no number. The employer is liable for tax it failed to withhold. W-2s are due January 31.

Before December 8:

MELD

MELD values the equity 409A with token allocation and the token FMV under one engagement. The annual plan is $18,000, or $16,500 paid in full at signing. It covers the 409A, four quarterly token marks for grants, vesting events, and distributions, and auditor support with one consolidated comment round per report. The same appraiser signs every report, so the history stays in one file.

Turnaround is five business days from a complete document set. If your last mark came from Pulley, download the history before December 8 and include it in the document set. Scope and pricing are at meldvaluation.com/pulley-token-valuation.