Bounties For Errors: Market Testing Contracts
Harvard Business Law Review, Vol. 10, 2020
USC CLASS Research Papers Series No. CLASS20-5
41 Pages Posted: 26 Sep 2019 Last revised: 7 Apr 2020
Date Written: April 6, 2020
Abstract
Many scholars and courts have championed a plain meaning approach to interpreting commercial contracts between sophisticated parties. These parties are assumed to carefully draft contracts to make their rights and obligations clear and knowable if the language is enforced as written. However, recent events in the commercial lending arena have raised questions about the efficacy of this approach. Aggressive parties have combed through reams of complex documents looking for ways around seemingly clear contractual barriers. For example, Hovnanian promised to intentionally default on a debt payment to one of its wholly-owned subsidiaries in exchange for favorable financing from a hedge fund whose substantial CDS short position would have otherwise become worthless. In another case, J.Crew, faced with financial distress, found a way to divert the crown jewels from the collateral package pledged to its lenders, and instead use this value to prevent a default on unsecured notes that were coming due. Both of these transactions upended the expectations of those who put the original deals together. They raise the question: how can systems that depend on clear rules evolve, correct problems and reduce unintended consequences without resorting to a subjective standard? One approach is to crowdsource error-checking to market-participants by paying bounties to those who detect and publicize flaws in rules-based systems so that problems can be diagnosed and corrected (or, at least, their consequences mitigated) by subsequently revising the rules. This article considers such an iterative approach in the context of the Credit Default Swaps Market and the syndicated loan market.
Keywords: contract, plain meaning, rule, standard, credit default swap, syndicated loan, covenant, hovnanian, engineered default, credit event, j.crew, collateral, basket, error-checking
JEL Classification: K12, K22, M21
Suggested Citation: Suggested Citation


