High Court claim involving claimed Bitcoin creator – the latest twist

High Court claim involving claimed Bitcoin creator – the latest twist

There have been further interesting developments in the Tulip Trading case, involving claimed Bitcoin creator Dr Craig Wright, on which we previously reported.

Tulip, ultimately owned by Dr Craig Wright and his family, alleged that open-source software developers who worked on the Bitcoin Core and Bitcoin Cash ABC software owed tortious and fiduciary duties to Tulip which required the developers to re-write or amend the underlying software code to enable Tulip to access its Bitcoin.

The High Court has now given judgment on various jurisdictional issues. In the course of doing so, it made the following findings on the merits of the allegations of tortious and fiduciary duties in the case. In particular:

  • The Court held that Tulip’s case that the developers owed fiduciary duties was not seriously arguable: “whilst an imbalance of power, together with vulnerability to abuse of that power, is often a feature of fiduciary relationships and may in broad terms be a rationale for the concept, it is not a defining characteristic and is certainly not a sufficient condition for the existence of that duty”.
  • Similarly, the Court held that it was not arguable that the developers owed tortious duties: “the required special relationship to found a duty of care in respect of economic loss could not exist”.

Whilst these findings are disappointing for Tulip, this case does not mark the end of the road for allegations that crypto software developers owe non-contractual duties under English law. Indeed, the High Court acknowledged that, in other factual scenarios, the existence of those sorts of duties may be more readily arguable.

In particular, the Court indicated that some sort of duty could be engaged where “in making an update to the software, the Defendants acted in their own interests and contrary to the interests of owners, for example, in introducing for their own advantage a bug or feature that compromised owners’ security but served their own purposes…

Potential claimants who have suffered at the hands of rogue developers will no doubt wish to draw on those comments when pursuing crypto software developers in future.

The recent judgment can be found below.

https://www.bailii.org/ew/cases/EWHC/Ch/2022/667.html

Recent posts

Previous
Next
AI Report
Read more
Baby Reindeer, internet sleuths and the perils of jigsaw identification
Read more
What businesses should consider before implementing monitoring
Read more
'Consent or pay’: the EDPB’s two cents on the right model
Read more
Take note: new guidance on the ICO’s penalties and fines
Read more
Labour’s proposed secondary ticketing reforms
Read more
The abolition of non-domicile in the Spring Budget
Read more
Content moderation: the ICO's guide
Read more
The Government moves to address unlawful immigration exemption under the Data Protection Act 2018
Read more
How can I get probate to sell my property?
Read more

More from this author

Previous
Next
Positive Development for Cross-Border Enforcement
Read more
Dispute Resolution in the Metaverse
Read more
How brands can adopt generative AI and avoid disputes
Read more
Digital Assets: Final Report
Read more
Service of Court documents via NFTs – no longer a novelty
Read more
High Court claim involving claimed Bitcoin creator – a significant Court of Appeal judgment
Read more
Significant Court of Appeal Judgment on Limitation of Liability in IT Contracts
Read more
Meet you in the Metaverse
Read more
New Podcast: Succession & Digital Assets
Read more
High Court claim involving claimed Bitcoin creator – one to watch
Read more
Tech and Sport podcast now live
Read more
Jurisdiction in 2021: LexisNexis webinar
Read more
Smart legal contracts: important update
Read more
Latest trends in data protection enforcement
Read more
Listen to our new podcast episode on NFTs
Read more
Listen to our first Digital Download podcast
Read more
Lawtech UK feasibility study
Read more
Jurisdiction post Brexit: Lugano Convention update
Read more

Share this page