Executive summary

A public-company Bitcoin treasury runs a derivatives program whether its board has authorised one or not. The implicit short-volatility position embedded in any reserve, the embedded short-gamma in any convertible note issued against it, and the basis exposure embedded in the financing structures that fund it together produce a derivatives book that exists by default. The choice management has is whether to govern that book consciously or to discover it when a stress event repricing makes the discovery expensive.

This paper is the operating playbook for governing it consciously. It covers the eight components of a board-readable derivatives policy, the instrument-selection trade-offs across loans, futures, and options, the four ISDA clauses that move the most money, the counterparty-management framework, the four GAAP elections that live in the financial statements indefinitely, and the SEC disclosure pattern that produces filings that pass review on the first cycle. It is meant to be read by CFOs, treasurers, audit-committee members, and the counsel and auditors who advise them.

1. The implicit derivatives book

Three exposures sit on the balance sheet of a public-company digital-asset treasury before management writes its first option ticket. The first is structural: the reserve asset is marked at spot while liabilities are denominated in fiat, scheduled in calendar time, and insensitive to the underlying. Drawdowns concentrate decisions (margin calls, financing renegotiations, dilutive issuance) at the worst possible price. This is what “short volatility” means in this context: not a literal options position, but a payoff structure with linear upside and asymmetric downside, with the worst outcomes clustered around exactly the regimes the company is least able to absorb.

The second is contractual: convertible notes issued by a BTC-treasury company embed a short-gamma position the issuer implicitly carries. As the underlying rises toward the conversion price, the implied dilution accelerates, and the natural management responses (issuing more equity, buying back stock) become procyclical. The third is operational: financing arrangements (BTC-collateralised dollar borrows, structured-product issuance, counterparty lending) carry basis and rehypothecation exposure that shifts in stress events in ways the standard finance team is not staffed to monitor.

The remainder of this paper assumes those three exposures exist. The question is not whether to have a derivatives program; it is how to structure the program the company already has.

2. The governance spine

A board-readable derivatives policy should arrive at the audit committee in twelve pages or fewer and contain eight components.

1. Scope of permitted instruments. A positive list of every authorised instrument: listed options, OTC options, futures, structured notes, swaps, financing trades. Anything not named is forbidden.
2. Sizing rules. Limits in delta-equivalent on the reserve, vega against balance-sheet sensitivity, notional against liquidity. Hard caps and soft thresholds; soft thresholds require documented review.
3. Approval matrix.Named signatories at each tier. CFO alone for routine roll inside the program; CFO plus audit-committee chair for size or instrument expansions; full committee vote for new underlyings or new counterparty classes.
4. Audit-trail standard.Every trade, quote, roll, and exception logged. Multi-dealer pricing on every roll, with the dispersion archived.
5. Regime triggers.Drawdown, funding-spread, NAV-discount, and counterparty- concentration thresholds, each paired with a pre-authorised response.
6. Reporting cadence.Monthly to the full board, weekly to the audit committee, on-demand to the auditor.
7. Exception procedure.How an out-of-policy action is requested, approved, documented, and either closed out or formalised into the policy.
8. Disclosure language.Pre-drafted earnings-call language, risk-factor inserts, MD&A inserts, and investor-letter templates aligned with what the policy authorises and coordinated with counsel and the auditor.

3. Instrument selection: loan vs futures vs options

A USD loan secured by BTC, BTC futures, and BTC options each let a treasury manage exposure, but they sit at different points on the trade-offs of capital efficiency, counterparty risk, downside path, and governance burden. A loan is the cheapest carry when prices are stable and ruinous when they aren't. Futures are capital-efficient but demand variation margin, which requires same- day collateral movement during stress. Options are the only structure with a defined-risk downside path, and the only structure that does not produce margin calls.

The right mix almost always involves more than one. A loan against a fraction of the reserve to meet near-term USD needs; a long-put protection layer sized to the worst-case drawdown the board has authorised against; a futures overlay used tactically to adjust sensitivity around catalysts. The program-design problem is sizing each one against the others, with the regime triggers in the governance spine determining when each component scales up or down.

4. The counterparty stack

Counterparty risk in digital-asset derivatives is the largest unmanaged risk in most public-company treasury programs. Failure in this market is rarely a surprise: the funding and rehypothecation patterns are visible in public disclosures eighteen months in advance for most failures. Eighteen months before the BlockFills counterparty failure in 2026, the pattern was visible. The lesson is that the data was public; only the framework for acting on it was missing.

The framework has five elements: a documented scoring rubric per counterparty (credit, pricing, workflow, product depth, ISDA terms, disclosure quality); a diversification floor (no more than 30-40% of program notional with any single counterparty); ISDA-grade terms (eligible-collateral expansion, narrowed termination events, dispute language flipped to the issuer side); a documented quarterly monitoring cadence with red flags written down in advance; and a pre-authorised regime-trigger response that allows exposure to be reduced on a yellow signal without a fresh board meeting.

5. ISDA / CSA: the four clauses that move the most money

Standard ISDA and CSA terms favour the dealer; issuer-grade terms have to be negotiated explicitly. Four clauses move the most money over the life of the program.

Eligible collateral. The fund-grade default is cash, with maybe Treasuries at a haircut. Issuer-grade terms expand the eligible-collateral list to include the underlying digital asset itself at a documented haircut, with a rehypothecation prohibition. Margin calls then fund themselves out of the asset on hand rather than out of the equity capital markets.

Threshold mechanics.Issuer-grade thresholds are sized to the issuer's liquidity profile, not the dealer's comfort. Independent amounts, if used, sit on the dealer side after a documented credit review.

Termination events.Standard ISDA termination clauses allow the dealer a discretionary right to terminate on a vaguely-defined material adverse change, on a credit-rating downgrade, or on an unusual movement in the underlying. Issuer-grade language narrows each of these to specific, objectively-measurable events with defined cure periods.

Valuation-dispute mechanic.Standard forms allow the dealer's mark to govern in dispute. Issuer-grade language flips the burden: the dealer must source third-party marks within a defined window; the client's mark stands in the interim; the resolution defaults to the client's side if the dealer doesn't source the marks.

6. The four GAAP elections that live indefinitely

A derivatives program inherits four accounting decisions made once and reflected in the financial statements indefinitely. Hedge- accounting designation under ASC 815 (binary, made at trade inception, with effectiveness testing). Fair-value level under ASC 820 (Level 1, 2, or 3, with disclosures and audit procedures following). Revenue / gain treatment for structured products coming off the program. Counterparty-risk reserve methodology (CVA / DVA) documented in advance. Each is defensible only if management has actively considered the alternative.

7. The SEC disclosure pattern

No formal rule specifies how a public company must disclose its crypto derivatives program. What exists is a pattern of comment letters from Corp Fin that collectively define what the staff expects to see. The pattern has five elements: a description of the program in operational terms; a risk-factor mapping concentration; a fair-value methodology consistent with the program; effectiveness language scoped to the regimes the program is sized for, without overclaiming; and a description of the governance envelope. Companies that disclose against this pattern proactively produce filings that pass review on the first cycle.

8. Convexity leakage and the multi-dealer process

The largest cost in any treasury derivatives program is not the premium spent on protection; it is the bid-offer spread paid on every roll, on every leg, for the life of the program. Compounded across a five-year overlay that spread is often 30-50% of the total program cost. The single most reliable mechanism to compress it is a multi-dealer quote process: three or more dealers, quoted simultaneously on the same instrument with the same reference time, on the same trade ticket, with all quotes recorded with timestamp, dealer name, mid, bid, ask, and conditions.

The dispersion record is the single most valuable artefact in the program. It produces a defensible best-execution narrative for the audit committee, leverage in the next negotiation (dealers who consistently price wide stop seeing flow), and an internal benchmark for what each instrument should cost. A treasury that runs a disciplined multi-dealer process compresses spreads by 20- 40% over the first twelve months, with further compression in the next twelve as dealers internalise that the company is a sophisticated counterparty.

9. Operating cadence and the board pack

A clean monthly board pack for a public-company digital-asset treasury is roughly twenty pages: cover, position summary, counterparty status, financing status, scenario monitor, activity log, sign-off, and an appendix of methodology and reference tables. It is the document the audit committee, the CFO, and the chair all read from in the same meeting. Numbers go in tables, status goes in colour, exceptions go in a list. Where prose is unavoidable, it is short. The board pack is not a report card; it is the operating record of a program the board has authorised, presented in a way that lets the committee discharge its oversight duty in a defined window every month.

10. How an engagement produces this

This paper describes the framework. It is not the implementation manual. The implementation is what the engagement produces, and it is composed of three things the framework alone cannot give a company.

A counterparty network that bids for the flow. Multi-dealer pricing with documented dispersion across every roll, ISDA and CSA terms negotiated against the precedent built up across the network, and a working roster of dealers who internalise that the company is a sophisticated counterparty. None of this comes from a written policy; it comes from the network and from documented, repeated execution.

The audit-committee posture.The work is operationally credible because there is a named outside expert the auditor and counsel sign against. Reading a framework does not give a CFO that posture; engaging the firm does. This is the layer that converts the document into a decision the audit committee will defend.

Implementation tempo.The companies that succeed turn policy into a working program in ninety days, then refine it across the first cycle. The companies that try to run the playbook unaided typically take two to three years to reach the same operating state, and most of them lose their first stress event in the meantime. Tempo is the third thing the engagement provides and the framework cannot.

What this means in practice: by the end of the first year of an engagement, a public-company digital-asset treasury is producing the audit-ready, regime-aware, market-friendly artefact this paper describes. The discount compression is cumulative across cycles. Companies that try to assemble it from a public framework continue to discover their derivatives program at exactly the moment it is most expensive to discover.

Framework, not implementation manual

This white paper, and every canonical reference page on gammoncap.com, is a description of the Gammon Capital framework. It is intentionally not a recipe. Engaged clients see the implementation specifics, the documented templates, the live counterparty record, the audit-trail tooling, the regime-trigger thresholds tuned to their balance sheet, and the negotiated ISDA language inside the Client Intelligence Hub. The framework is extractable; the implementation is not.