Shin v. ICON Foundation

District Court, N.D. California·Decided August 9, 2021·No. 3:20-cv-07363·Unknown

Opinion

1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 MARK SHIN, Case No. 20-cv-07363-WHO

8 Plaintiff, ORDER GRANTING IN PART AND 9 v. DENYING IN PART MOTION TO DISMISS SECOND AMENDED 10 ICON FOUNDATION, COMPLAINT; RE-SETTING DATE FOR CASE MANAGEMENT 11 Defendant. CONFERENCE

12 Re: Dkt. No. 59

13 14 Plaintiff Mark Shin alleges that defendant ICON Foundation (“ICON”) improperly 15 interfered with his ownership and possession of ICX tokens, a crypto-asset native to the ICON 16 blockchain network (“ICON Network”), which he created while taking advantage of an 17 unintended error in ICON’s protocols. He appears to raise issues of first impression: both parties 18 attempt to apply common law principles to the unique rules of the ICON Network to accuse the 19 other of, among other things, interference with property rights. This area of law, and the rights of 20 the parties, will benefit from a more complete factual record before decisions on the merits are 21 made. At this stage, I find that Shin has stated a plausible claim. For the reasons set forth below, 22 ICON’s motion to dismiss the Second Amended Complaint is DENIED with respect to the 23 conversion and trespass to chattel claims and GRANTED with respect to the punitive damages 24 claim. 25 BACKGROUND 26 The allegations in the First Amended Complaint are detailed in my previous order, which I 27 incorporate by reference here. See Order Granting Motion to Dismiss with Leave to Amend and 1 Amended Complaint, Shin drops his claims for declaratory relief and defamation and now only 2 asserts three property-based claims: (i) conversion based on the frozen ICX tokens in his ICON 3 wallet; (ii) trespass to chattel based on the frozen ICX tokens in his ICON wallet; and (iii) trespass 4 to chattel based on the frozen crypto-assets in his accounts on exchange platforms Binance and 5 Kraken. See Second Amended Complaint (“SAC”) [Dkt. No. 58]. His allegations are largely the 6 same, with some additions noted below. 7 The ICON Network hosts a “delegated proof of stake” blockchain, which allows for the 8 creation of a cryptocurrency called ICX. SAC ¶ 32. ICON “essentially aims for decentralized 9 governance,” where transactions “are verified by a ledger shared within the community network 10 itself, not controlled by a centralized authority.” Id. ¶ 54 (emphasis in original). To achieve such 11 decentralization, ICON “incentivized its users to run full nodes that themselves were comprised of 12 community Public Representatives (‘P-Reps’).” Id. ¶ 55. The ICON Network is controlled by 22 P- 13 Reps. Id. ¶ 68. P-Reps are able to “change the policies of the various nodes or communities of which 14 they are part” on the ICON Network, and, through their voting power can “determine when to update 15 the code underlying the ICON Network and help contribute to the overall ICON ecosystem by 16 developing new apps and new features for the code.” Id. ¶ 55. 17 Sometime in early August 2020, ICON published a software proposal, the “Revision 9 18 Proposal,” which included a series of updates and was adopted on August 13, 2020. Id. ¶¶ 67, 69. On 19 August 22, 2020, Shin “attempted to direct some of his staked ICX tokens from being delegated to one 20 P-Rep to being delegated to another through the ICONex wallet.” Id. ¶ 69. After initiating the 21 redelegation process, “a process he had performed many times before,” Shin “noticed that 25,000 new 22 ICX tokens had appeared in his wallet.” Id. ¶ 70. He “thought that there was a visual bug” and when 23 he tried redelegating his tokens again, he saw that another 25,000 ICX tokens had appeared in his 24 wallet. Id. ¶ 71. “Considering that the protocol was awarding him ICX tokens every time he initiated 25 the redelegation process, Shin continued to repeat the process,” and “[b]y the end of the day, he had 26 received approximately 14 million ICX tokens from the ICX protocol.” Id. ¶ 78. Shin acknowledges 27 that “[t]he authors and developers of the Revision 9 Proposal may not have intended for the network 1 did adopt into the network.” Id. ¶ 80. He claims he is the “lawful owner of the ~14 million ICX 2 tokens rewarded to him on August 22, 2020.” Id. ¶ 81. 3 Shin transferred “a significant portion of” the approximately 14 million ICX tokens to crypto- 4 asset exchange platforms Kraken and Binance. Id. ¶ 82. “A few hours later, he learned that he could 5 no longer transfer any of his crypto-assets—including the ICX tokens—out of his Binance and Kraken 6 accounts.” Id. (emphasis in original). He alleges that this was because ICON contacted Kraken and 7 Binance and “directed them to freeze his accounts on those exchanges, which they did.” Id. ¶ 83. 8 Binance and Kraken froze his accounts based on allegedly false statements by ICON that “Shin was a 9 ‘malicious attacker’ who acquired ‘stolen’ funds.” Id. ¶ 85. Shin adds that Binance and Kraken were 10 able to identify his specific accounts because “he had previously provided the exchanges with his 11 personal information—including his driver’s license and home address—when setting up and 12 maintaining his accounts” and because ICON provided both exchanges with “the public key 13 information related to Shin’s ICX transactions.” Id. ¶¶ 87–88. 14 On August 24, 2020, ICON announced on the Medium website (the “Medium Post”) that 15 another software proposal, the “Revision 10 Proposal,” sought to correct the bug that Shin discovered, 16 explaining that on August 22, 2020, an account had “attack[ed] the ICON Network.” Id. ¶ 91.1 Shin 17 claims that the Medium Post “contains multiple misrepresentations” and that he did not “attack” the 18 ICON Network as he “merely initiated a series of transactions directly facilitated by the ICON 19 blockchain and expressly permitted by ICON and P-Reps.” Id. ¶ 94. He adds that it is also false that 20 “the tokens were created by a single account” because he only created 14 million tokens whereas 21 ICON admitted “that nearly 20 million ICX tokens were created through the bug,” and thus other users 22 created 6 million tokens. Id. ¶ 95. 23 Shin also adds new allegations that “numerous affiliates of ICON benefited from the Revision 24 9 minting bug, dating back to at least August 14, 2020—eight days prior to Shin discovering its 25 existence.” Id. (emphasis in original). ICON publicly targeted him as a “scapegoat to distract 26 from its culpability in introducing the Revision 9 minting bug” and “at the same time sought to 27 1 cover up the fact that many of its close affiliates received ICX tokens from the same mechanism as 2 Shin.” Id. ¶ 108. Since filing this action, he claims that his counsel has investigated the ICON 3 blockchain to determine the identity of the other ICX wallets that benefited from the bug and has 4 so far identified at least four other entities: “Velic, StakingTeam, ICX Station, and Hyperconnect.” 5 Id. ¶ 109. The SAC lists the number of tokens each of the entities minted and the date the minting 6 occurred, including one on August 17, 2020, two on August 21, 2020, and one on August 22, 7 2020, the same day as Shin. Id. ¶ 110. Shin alleges that the Revision 10 software update only 8 limited his access to the ICX tokens in his wallet, not the other alleged beneficiaries of the 9 Revision 9 bug. Id. ¶¶ 96–107. 10 Though ICON claims it has a decentralized system, Shin contends that it had de facto 11 control over the ICON Network, particularly the network proposal approval process, including the 12 Revision 10 update that deprived him of his property. Id. ¶¶ 117–32. He claims that ICON 13 “punitively changed its code to target Shin, and in doing so interfered with and precluded him 14 from exercising his rights of ownership over his property.” Id. ¶ 98. 15 LEGAL STANDARD 16 Under Federal Rule of Civil Procedure

Free access — add to your briefcase to read the full text and ask questions with AI

Shin v. ICON Foundation, (N.D. Cal. 2021).

Shin v. ICON Foundation (Shin v. ICON Foundation) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Hughes v. Oklahoma
441 U.S. 322 (Supreme Court, 1979)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Farrington v. A. Teichert & Son, Inc.
139 P.2d 80 (California Court of Appeal, 1943)
Downing v. Municipal Court
198 P.2d 923 (California Court of Appeal, 1948)
In Re Gilead Sciences Securities Litigation
536 F.3d 1049 (Ninth Circuit, 2008)
Clajon Production Corp. v. Petera
854 F. Supp. 843 (D. Wyoming, 1994)
Oakdale Village Group v. Fong
43 Cal. App. 4th 539 (California Court of Appeal, 1996)
Burlesci v. Petersen
80 Cal. Rptr. 2d 704 (California Court of Appeal, 1998)
Jamgotchian v. Slender
170 Cal. App. 4th 1384 (California Court of Appeal, 2009)
eBay, Inc. v. Bidder's Edge, Inc.
100 F. Supp. 2d 1058 (N.D. California, 2000)
People v. Rinehart
377 P.3d 818 (California Supreme Court, 2016)
Kimball v. Lohmas
31 Cal. 154 (California Supreme Court, 1866)
Lincoln National Life Insurance Co. v. McClendon
230 F. Supp. 3d 1180 (C.D. California, 2017)
Kremen v. Cohen
337 F.3d 1024 (Ninth Circuit, 2003)