Bitcoin treasury derivatives governance: what it is and why it matters

Definition

Bitcoin treasury derivatives governance is the set of written, board-approved policies, controls, and operating procedures that govern every derivatives position a public-company digital-asset treasury authorises, executes, and discloses. It includes: the scope of permitted instruments (options, futures, swaps, structured products, financing trades); sizing rules expressed in delta, vega, and notional; named approval thresholds; regime triggers with pre-authorised responses; a reporting and audit-log standard; and the disclosure language coordinated with counsel.

It is not a trading strategy. It is the control system inside which a strategy runs. The strategy can change with the regime; the governance is intended to outlive every regime the company will see.

Why it matters

A BTC treasury that runs a derivatives program without a written governance framework discovers, in the first stress event, that the decisions it should have made in advance, sizing limits, exit triggers, counterparty rules, are being made under pressure with the chair, the auditor, and the bank on the same call. The decisions made under pressure are systematically worse than the decisions made in advance. The governance framework exists to make those decisions when nobody is shouting.

It also matters for what it produces externally. The SEC's Division of Corporation Finance routinely asks public companies to disclose the governance envelope around their derivatives activity. Companies whose policies are written and rehearsed produce filings that pass review on the first cycle; companies whose programs are improvised attract follow-up comment letters that materially extend the disclosure burden.

Framework: the eight components

1. Scope of permitted instruments. A positive list naming each authorised instrument: listed options, OTC vanilla options, structured notes, futures, basis trades, swaps, financing trades. Anything not named is forbidden.
2. Sizing rules. Limits in delta, vega, notional, and gross premium spend, expressed against balance-sheet aggregates rather than absolute dollar amounts.
3. Approval matrix. Named signatories at each tier; CFO alone for routine rolls inside the program; CFO plus audit-committee chair for expansions; full committee vote for new underlyings or new counterparty classes.
4. Audit-trail standard. Every trade, every quote, every roll logged in a form an auditor can pull on demand. Multi-dealer pricing on every roll, with the dispersion archived.
5. Regime triggers and pre-defined responses. Drawdown, funding-spread, NAV-discount, and counterparty-concentration thresholds, each paired with the response it authorises so the response is on file before the trigger fires.
6. Reporting cadence. Monthly to the full board, weekly to the audit committee, on-demand to the auditor. Single source of truth, versioned, immutable archive.
7. Exception procedure. How out-of-policy actions are 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 coordinated with counsel and the auditor.

Example

A public BTC treasury holds 5,000 BTC against $200M of long-dated convertible debt. Under its derivatives governance, the audit committee has pre-authorised a defensive overlay (long puts financed by short calls) sized to a maximum of 25% of the reserve's delta exposure, scoped to listed options on a defined counterparty list, and limited to a 6-month tenor. A regime trigger ties the program's expansion to a measured drawdown of 20% from the prior quarter-end peak. When BTC falls 18% in a week, the CFO does not call an emergency board meeting; the program already authorises the next move at a 20% threshold, and the response is executed on the second day with the audit-committee chair informed by email rather than phone.

Common mistakes

Treating the policy as boilerplate. Most company derivatives policies are recycled from a counsel template and authorise everything, vaguely. A vague policy is the same as no policy in a stress event.

Authorising instruments the board doesn't understand. An audit committee that signs off on a structure it cannot describe in an earnings call has not actually authorised the structure. The right scope is what the committee can defend in writing.

Skipping the disclosure language. Without pre-drafted language, the disclosure is improvised on the day of the 10-Q deadline. That is the most common single source of follow-up comment letters from the SEC staff.

No regime triggers. A program that requires a fresh board decision for every defensive move is a program that does not move quickly enough in the regime the program was designed for.

Gammon Capital view

Derivatives governance is the highest-leverage document a public-company digital-asset treasury produces. It is also the cheapest: a single twelve-page artefact, written once, defended by the audit committee, and re-used through every regime. The companies that ship one early compound the advantage; the ones that don't spend the next several quarters catching up under pressure. The work is procedural before it is technical; few have done it.