Treasury Engineering
Why a BTC treasury is implicitly short volatility
· Michael Mescher, Gammon Capital
A digital-asset treasury sits implicitly short volatility. The position is rarely written down that way, but the cash-flow geometry of the balance sheet leaves no ambiguity: drawdowns concentrate decisions at the worst possible price.
The mechanism is not exotic. Reserves are marked at the spot price; liabilities (interest payments, converts, equity issuance windows) are denominated in fiat, scheduled in calendar time, and therefore insensitive to the underlying. When the reserve asset falls, coverage falls, financing windows close, and the choices left are all bad: sell into the drawdown, raise dilutive equity, or breach a covenant.
This is what “short vol” means here. Not a literal options position, but a payoff structure: linear upside, asymmetric downside, with the worst outcomes clustered around exactly the regimes a treasury is least able to absorb.
Three places the structure breaks
Forced-sale. A maturity that lands inside a drawdown forces selling at the bottom. The cure is laddered liabilities and a liquidity buffer sized to the deepest drawdown the board is willing to plan against, not the most likely one.
Reflexive funding. Issuance and converts that worked at peak NAV become punitive when the discount-to-NAV widens. Capital structures should be regime-aware: priced and timed to a window where execution is possible, not assumed.
Governance gaps. Boards approving derivatives without a sizing policy, audit trail, or scenario framework expose themselves and the company. The fix is procedural before it is technical: sizing limits, approval rights, and reporting that survives turnover.
The shape of the fix
A treasury can work toward converting this implicit short-volatility exposure into a vol expression sized to the regime (long, short, structured, or layered) inside a policy the board has authorized. The components are well-understood individually: overlay programs, hedged issuance, liability laddering, scenario-driven sizing, and a counterparty stack that doesn’t bid you wide on every roll. The value is in how they interlock. Standalone hedges leak; standalone governance is performative; standalone balance-sheet engineering misses the trade. The architecture has to ship together.
Subsequent notes in this series cover each component on its own, and how they fit into a single, defensible chassis a board can sign off on.
Practice
How we build this architecture for a public-company treasury →
Engagement
Request capacity for an introductory diligence call →
For general informational purposes only. Not investment, legal, tax, or accounting advice, and not an offer or solicitation. Derivatives, digital assets, and overlay strategies involve substantial risk, including the risk of total loss. Past performance is not indicative of future results.