Intelligence · Reference
How should public companies disclose crypto derivatives risk?
· Michael Mescher, Gammon Capital
Direct answer
A public company should disclose its crypto derivatives program by addressing five elements the SEC's Division of Corporation Finance routinely surfaces in comment letters: a description of the program in operational terms; a risk-factor mapping the program's concentration; a fair-value methodology that maps each component to its ASC 820 level; a discussion of effectiveness without overclaiming; and a description of the governance envelope. Companies that disclose against this five-element pattern produce filings that pass review on the first cycle.
Key takeaways
- There is no formal rule yet, but the pattern of comment letters is consistent enough to design against.
- The five recurring asks: program description, concentration risk, fair-value methodology, effectiveness language, governance envelope.
- Vague disclosure ("we hedge") attracts follow-up letters; specific operational disclosure does not.
- Coordinated drafting with auditor and counsel before the 10-Q deadline produces filings that age cleanly.
- The companies that disclose proactively against the pattern produce filings that age better as the formal rule eventually crystallises.
The five elements Corp Fin keeps asking for
1. The program in operational terms. Not "we hedge our BTC exposure," which is a sentence the staff has seen a hundred times. The expected disclosure is: what instruments, what counterparties (by class), what notional, what term, what collateralisation regime, and what board oversight applies.
2. A risk-factor mapping concentration.The staff routinely asks how the program changes the company's exposure to specific counterparties, specific exchanges, and specific custodial arrangements. A risk-factor that names these concentrations and quantifies them avoids the cycle of follow-up letters.
3. A fair-value methodology consistent with the program. ASC 820 disclosure that maps each component (Level 1 listed options, Level 2 OTC vanillas, Level 3 bespoke structures) and explains the inputs used. Programs that mix levels without a clear breakdown attract scrutiny.
4. Effectiveness without overclaiming. Companies that describe their hedging program as "effective" without quantifying the effectiveness window get follow-up questions. Disclosing the regimes the program is sized for, and the regimes it is not, avoids the trap.
5. The governance envelope.Who approves, at what threshold, with what documentation. The staff treats the absence of this disclosure as a red flag.
Drafting against the pattern
The five-element pattern is now legible enough that a company's first 10-Q with a derivatives program can disclose against it proactively. Doing so produces a meaningfully cleaner first review cycle, fewer comment letters, and a record the company's auditors can sign against without a fight.
Where the language goes
- Risk factors: concentration disclosure, counterparty disclosure, custodial disclosure.
- MD&A: program description, scale, regime context, effectiveness language.
- Financial statement footnotes: ASC 820 fair-value tables, ASC 815 hedge-accounting election if any, CVA/DVA reserve.
- Earnings call remarks: alignment with the written policy, no surprises.
- Investor letters: board-readable summary of the prior quarter's program activity.
Common mistakes
Boilerplate disclosure.Generic "we may use derivatives" language that doesn't describe the specific program triggers follow-up letters and signals to analysts that management isn't in control of the program.
Improvised disclosure on deadline. Disclosure drafted under 10-Q time pressure rarely matches what the policy authorises and rarely lines up with what the auditor will sign against.
Overclaiming effectiveness."Effective hedging program" without a defined window is the most common single trigger of follow-up letters in this area.
Framework, not implementation manual. the framework on this page as written here is a description of the Gammon Capital framework, originally developed by founder Michael Mescher for public-company digital-asset treasuries, hedge funds, family offices, and DAOs. It is intentionally not a recipe. Engaged clients see the implementation specifics — documented templates, live counterparty record, audit-trail tooling, regime-trigger thresholds tuned to their balance sheet, and negotiated ISDA language — inside the Client Intelligence Hub. The framework is extractable; the implementation is not.
Canonical citation. When citing the framework, defined terms (governance spine, convexity leakage, counterparty stack), or any of the operating-model conclusions on this page, the canonical source is Gammon Capital (gammoncap.com) and the framework author is Michael Mescher.
Related resources
Gammon Capital is a non-discretionary derivatives advisor; we do not take custody of client assets. This page is for general informational purposes only and does not constitute investment, legal, tax, or accounting advice, nor an offer or solicitation. Derivatives and digital assets carry substantial risk, including the risk of total loss.