Intelligence · Reference
Are covered calls risky for a Bitcoin treasury?
· Michael Mescher, Gammon Capital
Direct answer
Yes, covered calls on a Bitcoin treasury are risky in the way most overlay programs misunderstand. The trade is not yield; it is a sale of the upside optionality embedded in the reserve, in exchange for a premium that is almost always smaller than the optionality is worth. Three narrow regimes make the trade defensible: when the strike sits above the company's strategic upside case, when the program is sized as a small overlay against a much larger spot position, and when the call is sold inside a defined-risk spread rather than naked.
Key takeaways
- A covered call is short volatility and short upside on the reserve asset.
- In a trending bull regime the strategy systematically caps upside at the worst possible time.
- The narrative cost (analysts noting that the company sold its upside before it materialised) is real and shows up in the multiple.
- Three narrow regimes make the trade defensible: strike well above the strategic case, small sizing, or spread-form structure.
- If the rationale is yield, the wrong question is being asked.
Why the trade looks attractive
On paper a covered call generates yield against an asset that otherwise pays nothing. For a treasury, that maps cleanly onto a narrative about converting an unproductive reserve into a recurring income stream. The premium is real cash, the position is bounded, and the trade reads as conservative.
Why it isn't
The buyer of the call is paying for the right to capture upside above the strike. If the BTC reserve is a strategic asset (the company's narrative is explicitly about owning the upside), then the premium received is the cost of selling the very thing the company is supposed to be holding for shareholders. The covered call generates yield by liquidating the strategic case for the position one expiry at a time.
The narrative damage compounds. Analysts notice that the company sold its upside before it materialised; the multiple on the equity reflects that. A program that books premium income but loses on equity multiple is a worse outcome than no program at all.
Three regimes where it is defensible
Strike above the strategic case. Selling a call at $200,000 on a treasury whose investment thesis assumes long-run BTC at $150,000 is internally consistent. The premium captures yield without liquidating the position the company actually wants to hold.
Small sizing.Selling calls against 10% of the reserve, with tight delta-hedging discipline, harvests premium without meaningfully shaping the company's exposure to the upside thesis.
Spread form. A short call hedged with a longer-dated call at a higher strike caps the upside-give-up at a defined level. The structure is no longer a covered call but a calendar or a vertical, and the framing should change with it.
What to ask before authorising the program
- What is the company's strategic upside case? Where does the call strike sit relative to it?
- What size against the reserve? Sized as a small overlay or as a primary income source?
- Naked or spread? If naked, what justifies the open-ended upside cap?
- What is the regime trigger that pauses or unwinds the program?
- How will it be disclosed and how will the IR team narrate it?
Common mistakes
Framing it as yield.Covered call income is a sale of optionality. Calling it yield masks what was sold.
Running it through a trending bull regime. The program systematically underperforms in exactly the regime the company most wants to be exposed to.
No exit trigger.Programs without a pre-defined exit run themselves into the next gamma squeeze.
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.