Showing posts with label Blockchain. Show all posts
Showing posts with label Blockchain. Show all posts

Friday, March 19, 2021

Court of Chancery of the State of Delaware, Tetragon Financial Group Limited v. Ripple Labs Inc., Docket C.A. No. 2021-0007-MTZ

 

 

Blockchain Company

 

Cryptocurrency

-       Officially Determined to Constitute a Security?

-       In the Affirmative: Redemption Right is Triggered in Favor of Series C Preferred Stock’s Holder, According to Stockholders’ Agreement

 

Wells Notice and the SEC’s Filing of an Enforcement Action

 

Contract Drafting

 

Meaning of the Term “Determination

 

Delaware Law

 

 

 

In this expedited contractual dispute, defendant Ripple Labs, Inc. (“Ripple”) has moved for summary judgment (the “Motion”). Granted.

 

Ripple is an enterprise blockchain company. It uses a cryptocurrency called XRP in its payment network, and hosts a platform, RippleNet, to  facilitate transactions. Plaintiff Tetragon Financial Group Limited is an   investment company. Plaintiff, through its affiliates (collectively,  “Tetragon”), holds a majority of Ripple’s Series C preferred stock. Ripple  and Tetragon executed a stockholders’ agreement dated December 20, 2019 (the “Stockholders’ Agreement”) memorializing Tetragon’s investment and status as « Lead Purchaser. » Pursuant to that agreement, Tetragon has a redemption right that is triggered upon a “Securities Default” as defined in Section 5.4: A “Securities Default” means if XRP is determined on an official basis (including without limitation by settlement) by the U.S. Securities and Exchange Commission (or (1) another governmental authority or (2) a governmental  agency  of  similar  stature  and  standing)  to  constitute a security  on  a  current  and  going  forward  basis  (and  not,  for  the avoidance  of  doubt,  a  determination  that  XRP  was  a  security  in  the past). If a Securities Default occurs, Tetragon may demand redemption of its shares via a « Redemption Request. » Following receipt of a valid Redemption Request, the Stockholders’ Agreement requires Ripple to redeem Tetragon’s shares within sixty days and apply all of its legally available cash and other assets to the redemption. At issue in this case is whether certain actions by the Securities and Exchange Commission (the “SEC” or the “Commission”)—in particular, a “Wells Notice” and the filing of an enforcement action—constitute a “Securities Default” under Section 5.4.  Some brief background on these processes provides helpful context.

 

Wells Notices And Enforcement Actions Generally

SEC investigations are usually initiated when a potential violation of securities law is identified. If the matter escalates, the SEC will issue a Formal Order of Investigation, which identifies the nature of the investigation, grants power to the SEC’s staff (the “Staff”) to investigate, and allows the SEC and its officers to issue subpoenas and compel sworn witness testimony. If the Staff finds that further action is warranted, the Staff may recommend that the SEC file an enforcement action or institute other enforcement proceedings.

 

Prior to doing so, the Staff may send potential defendants a Wells Notice, which allows potential defendants the chance “to provide a written submission” in defense of their actions. At this stage, the Staff must obtain an Associate or Regional Director’s approval. Once a potential defendant submits a written response to a Wells Notice, that submission must be sent to the Commission with a staff memorandum.

 

Based on the Action Memorandum and the potential defendant’s written submissions, the Commission votes to approve or reject the recommendation.

 

An enforcement action begins when the SEC files suit in federal court. After the Commissioners vote to bring an enforcement action, they are minimally involved in the litigation. Once the SEC decides to file in federal court, the SEC’s role pivots to that of advocate for its position; barring settlement, the Court—not the Commission—decides whether the instrument in question is ultimately a security.

 

(…) In line with “Delaware’s well-understood principles of contract interpretation,” I find that the Stockholders’ Agreement’s plain language is susceptible to only one meaning: a determination “on an official basis” that XRP “constitutes a security on a current and going forward basis” answers the question of whether XRP is a security in the affirmative and with finality. Applying that meaning to the undisputed facts, I conclude that a Securities Default has not occurred.

 

(…) Neither party here meaningfully contends that the definition of Securities Default is ambiguous, so I do not reach the parties’ arguments about their negotiation history or other extrinsic evidence of their intent.

 

Instead, I turn directly to the language in question, and apply it to the Wells Notice and the SEC’s filing of the Enforcement Action.

 

“Under well-settled case law, Delaware courts look to dictionaries for assistance in determining the plain meaning of terms which are not defined in a contract,” as “dictionaries are the customary reference source that a reasonable person in the position of a party to a contract would use to ascertain the ordinary meaning of words not defined in the contract.” And so, I look to contemporary dictionaries to help understand Section 5.4’s undefined terms.

 

By its plain meaning, a “determination” has finality. According to Merriam- Webster’s Dictionary, to “determine” something means “to fix conclusively or authoritatively,” as in to “determine national policy,” or “to settle or decide by choice of alternatives or possibilities,” as in to “determine the best time to go.” The Oxford Learner’s Dictionary similarly states that a “determination” is “the process of deciding something officially.” The “official” nature of a determination is echoed in definitions in the legal arena. In those definitions, a determination comes from an authoritative source, such as a court. Black’s Law Dictionary tells us that a “determination” is “the act of deciding something officially; especially, a final decision by a court or administrative agency.” Merriam-Webster’s definition suggests that a legal determination has finality, « a judicial decision settling and ending a controversy ».

 

(…) Applying this plain meaning to the SEC’s decision to file the Enforcement Action and issue a Wells Notice, it is clear that neither constitutes a Securities Default.

 

(…) Tetragon’s arguments regarding the Wells Notice present an even weaker case for a Securities Default. A Wells Notice precedes an enforcement action, giving potential defendants notice of the SEC investigation and providing them the opportunity to explain to the SEC why an enforcement action is unnecessary. As the parties’ experts explained, a Wells Notice indicates that the Staff might recommend an enforcement action to the SEC Commissioners, but the Commission itself is free to reject this recommendation. SEC Commissioners, who lead the SEC, are simply not involved in the Wells process. Further, a Wells Notice invites the potential defendant to convince the Staff that such a recommendation would be improper. Wells Notice from Staff is a far cry from the type of official, final decision contemplated by Section 5.4.

 

My conclusion that the SEC actions at issue fall short of “determinations” does not gut Section 5.4 of its meaning. It is undisputed that the SEC can make “determinations on an official basis” in three other ways: (1) an administrative proceeding, (2) a report pursuant to the Securities Exchange Act of 1934 (the “’34 Act”), and (3) rulemaking.

 

 

(Court of Chancery of the State of Delaware, March 19, 2021, Tetragon Financial Group Limited v. Ripple Labs Inc., Docket C.A. No. 2021-0007-MTZ)

 

Saturday, August 8, 2020

California Court of Appeal, First Appellate District, Archer v. Coinbase, Inc., Docket No. A157690, Certified for Publication

 

Bitcoin

 

Cryptocurrency

 

Online Digital Currency Exchange Platform

 

Blockchain

 

Internet Law

 

User Agreement

 

Breach of Contract Claim

 

Parole Evidence v. Integration Clause

 

California Law

 

Contract Drafting

 

 

(…) As plaintiff correctly notes, this case—concerning the recovery of damages for failure of a cryptocurrency exchange to provide access to a forked digital currency created by a third party—presents an issue of first impression in California.

 

 

Plaintiff Darrell Archer filed suit against Coinbase, Inc. (Coinbase), an online digital currency exchange platform, alleging causes of action for breach of contract, negligence, and conversion stemming from Coinbase’s purported refusal to allow him to access a “forked” cryptocurrency (Bitcoin Gold) stored in his Coinbase account. The trial court granted summary judgment for Coinbase.  Plaintiff filed an appeal from the order granting summary judgment. We affirm.

 

 

A digital currency (also known as “cryptocurrency”) is a type of currency maintained by a decentralized network of participants’ computers, rather than a centralized government or organization.  Anyone can volunteer his or her computer to be part of such a network by running software that allows the computer to interact with the network. Once an individual joins a particular digital currency’s network, he or she can interact with that digital currency.  A holder of a digital currency can send it to another individual on the network, by authorizing that it be sent to the recipient’s “public key,” an alphanumeric string of characters that acts as a public identifier.  Transactions between network participants are recorded on a “blockchain,” which is a public ledger of digital currency transactions.  Bitcoin is among the world’s most well-known digital currencies, but there are thousands of digital currencies in existence.  Each operates on its own unique network and blockchain ledger.  Anyone can create a new digital currency, and new currencies are created almost daily.

 

 

On October 23, 2017, plaintiff had 350 Bitcoin stored in his account with Coinbase.  That day, a third party launched a new cryptocurrency, “Bitcoin Gold,” as a “fork.”  A fork is a way of creating a new digital currency by copying the source code of an existing digital currency’s blockchain and repurposing it into a new digital currency network.  When a developer creates a fork, the existing ledger of transactions from the original currency is used, and holders of the original currency are assigned equivalent units of the new currency on the new network.  The new currency then “forks” into a separate blockchain ledger that records transactions of the new currency between participants in the new network.

 

 

When Bitcoin Gold was created, Coinbase monitored and evaluated Bitcoin Gold’s network and decided it would not support the new currency.  Coinbase informed its customers via its website:  “ ‘At this time, Coinbase cannot support Bitcoin Gold because its developers have not made the code available to the public to review.  This is a major security risk.’ ”  In 2018, the Bitcoin Gold network was attacked by hackers who stole millions of dollars of funds from trading platforms and individuals on its network.

 

 

On March 27, 2018, plaintiff filed suit against Coinbase.  Shortly thereafter, plaintiff filed a first amended complaint, alleging various causes of action based on Coinbase’s failure and refusal to allow him to receive his forked Bitcoin Gold currency and Coinbase’s retention of control over plaintiff’s Bitcoin Gold for its own benefit.

 

 

The trial court subsequently granted summary judgment for Coinbase on all three causes of action.  The court concluded, “The fact that Coinbase’s User Agreement with Plaintiff contains no provision requiring Defendant to provide services related to any particular digital currency created by a third party is dispositive, requiring the Court to grant this motion.”

 

 

Breach of Contract Claim

 

We agree with the trial court that plaintiff’s breach of contract claim fails because plaintiff did not establish the existence of an agreement with Coinbase to provide the Bitcoin Gold to him.  (Sonic Manufacturing Technologies, Inc. v. AAE Systems, Inc. (2011) 196 Cal.App.4th 456, 464 [elements of breach of contract cause of action are existence of a contract, plaintiff’s performance, the other party’s breach, and damages]; Levy v. State Farm Mutual Automobile Ins. Co. (2007) 150 Cal.App.4th 1,   5  (Levy) [claim for breach of contract requires plaintiff specifically plead breach of agreed upon contractual provision].)  It is undisputed that the User Agreement does not contain a provision requiring it to support or provide services for any particular digital currency created by a third party.  Plaintiff also did not dispute he was aware at the time of the fork that Coinbase does not support every digital currency and that Coinbase has no duty or obligation to support every new digital currency that is created.  Coinbase presented evidence it monitored and evaluated Bitcoin Gold’s network when the new currency was created, determined the network was not stable or reliable, and issued a public statement that it would not support the new currency due to security concerns.  Plaintiff did not identify any representations, oral or written, by Coinbase that it would support Bitcoin Gold, or that it would provide usual and customary services.

 

 

On appeal, plaintiff argues the trial court erred in its interpretation of the User Agreement.  First, plaintiff contends his “right and entitlement” to the Bitcoin Gold fork is established by his possession and ownership of Bitcoin on deposit with Coinbase.  But regardless of whether that is true, plaintiff’s alleged ownership of Bitcoin Gold resulting from the cryptocurrency fork says nothing about Coinbase’s contractual obligation to provide Bitcoin Gold to plaintiff.

 

 

(…) Both versions of the User Agreement submitted by Coinbase and electronically signed by plaintiff had integration clauses stating the agreement represented the entire agreement between the parties and superseded “any and all prior discussions, agreements and understandings of any kind . . . .”

 

 

We further reject plaintiff’s attempted reliance on parol evidence because the User Agreement contains an integration clause stating it is the “entire understanding and agreement” of the parties.  “When the parties to a written contract have agreed to it as an ‘integration’—a complete and final embodiment of the terms of an agreement—parol evidence cannot be used to add to or vary its terms.”  (Masterson v. Sine (1968) 68 Cal.2d 222, 225; Brown v. Goldstein, supra, 34 Cal.App.5th at p. 432.)  Plaintiff did not present any extrinsic evidence of a collateral agreement in opposition to the summary judgment motion.

 

 

As plaintiff correctly notes, this case—concerning the recovery of damages for failure of a cryptocurrency exchange to provide access to a forked digital currency created by a third party—presents an issue of first impression in California.

 

 

We decline to impose a major new absolute tort duty on digital currency exchanges to honor forked currencies.

 

 

 

 

 

(California Court of Appeal, First Appellate District, August 8, 2020, Archer v. Coinbase, Inc., Docket No. A157690, Certified for Publication)