Intelligence · Reference
Managing counterparty risk in digital-asset derivatives
· Michael Mescher, Gammon Capital
Direct answer
Counterparty risk in digital-asset derivatives is the largest unmanaged risk in most public-company treasury programs. Managing it is procedural: score every counterparty against a defined rubric, diversify across at least three counterparties before scaling notional, negotiate issuer-grade ISDA and CSA terms, monitor public-disclosure signals continuously, and pre-authorise the regime-trigger response that walks the program out before the failure becomes public.
Key takeaways
- Counterparty failure in crypto is rarely a surprise; the funding and rehypothecation patterns are visible in public disclosures eighteen months in advance for most failures.
- Concentration in a single dealer or exchange is the most common single risk factor across the universe.
- ISDA-grade terms (eligible collateral, narrowed termination events, dispute language flipped) materially reduce the loss given a counterparty failure.
- Monitoring is structural, not reactive: a documented review cadence per counterparty, with public-disclosure red flags written down in advance.
- The regime-trigger response should be pre-authorised so the program can act on a yellow signal without a fresh board meeting.
Why counterparty risk dominates
In a derivatives program, counterparty failure is a higher-impact event than market loss. A 30% drawdown on the underlying has a scenario-defined cost that the program is designed to absorb. A counterparty failure is open-ended: collateral may be locked, positions may be unwound at adverse marks, and the company is in litigation rather than execution.
For digital-asset treasuries, counterparty risk is structurally larger than for equity-vol programs, because the dealer base is narrower, the legal and operational frameworks are less mature, and rehypothecation patterns are more aggressive at some venues than most issuers realise.
The five-element framework
1. Scoring rubric.Every authorised counterparty is scored on credit, pricing consistency, operational workflow, product-depth across instruments, ISDA terms, and public-disclosure quality. The rubric is documented in the policy, refreshed quarterly, and visible to the audit committee.
2. Diversification floor.No more than 30-40% of program notional with any single counterparty, regardless of pricing. The discount you give up to a tighter single-dealer arrangement is dwarfed by the loss given default.
3. ISDA-grade terms.Eligible-collateral expansion, narrowed termination events, dispute language flipped to the issuer side, rehypothecation prohibition. See the ISDA checklist.
4. Monitoring cadence.A documented review of each counterparty's public disclosures, funding patterns, and rehypothecation language quarterly. Specific red flags (going-concern audit qualifications, rehypothecation expansions, segregation-language degradation) are listed in advance and trigger an immediate review.
5. Pre-authorised regime trigger. Yellow signal (degraded score, concerning disclosure) authorises a documented reduction of exposure without a fresh board meeting. Red signal authorises full unwind.
The pattern in failures
Counterparty failures in crypto follow a recognisable pattern. Funding becomes more aggressive (less collateral, longer rehypothecation chains, more liability stacking on top of less equity). Public disclosures become more guarded. Spreads on the firm's own derivatives products widen, and certain trades stop being available. Each of these is a yellow signal in its own right; together they are a red signal.
Eighteen months before the BlockFills counterparty failure in 2026, the funding-and-rehypothecation pattern was visible in public disclosures. Treasuries that were watching walked out; treasuries that weren't took the loss. The lesson is that the data was public; only the framework for acting on it was missing.
Common mistakes
Concentrating for pricing.The cheapest single-dealer arrangement is the most expensive one to unwind in a stress event.
No documented review cadence.A monitoring framework that doesn't produce a quarterly artefact isn't a framework.
Reactive rather than pre-authorised exits. Unwinding under pressure means the dealer prices the unwind, not the issuer.
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.