Craig Wright challenges to Sue BTC and BCH With Potential Lawsuits
The Bitcoin (BTC) and BCH have been alerted by Craig Wright, who claims to be the Bitcoin developer known as Satoshi Nakamoto, to stop using the Bitcoin blockchain to avoid potential litigation. He says all networks may also infringe the laws under the terms of the original EULA and MIT license issued by Bitcoin. Let’s check to Craig Wright challenges to Sue BTC and BCH With Potential Lawsuits.
In the recent personal blog post, the man behind Bitcoin SV added that he will take back control of the system he developed and that he is ready to fight for his rights this year.
The Argument of Craig Wright
Wrights claims that the distributed Bitcoin database rights are regulated by the 1988 Copyright, Designs and Patents Act (CDPA) and the 1997 Law on Copyright and Rights in Databases (Databases Regulations 1997). It should therefore be treated as personal property.
Dr. Wright says that representing a total of 21 million Bitcoin which is divisible by 100 million Bitcoin each is just a verbal contract. The developer of the Bitcoin should have full rights to claim this unilateral agreement with those nodes to be released, adding:
“As the creator of Bitcoin, I maintain the sui generis rights to any copy of the database created from Genesis in January 2009. I shall not be relinquishing the ownership. I will be licensing it, and have already engaged in a process.”
In a case filed on behalf of the family of Dave Kleiman, Wright’s late business partner, Craig Wright has been defendant since 2018. The lawsuit claimed that Wright illegally stole more than one million Bitcoin (BTC) after Kleiman’s death in 2013 that the pair had mined jointly in the early years of the cryptocurrency, as well as some relevant intellectual property.
The new trial was postponed to April 17 with Kleiman’s case, and the trial will not be held until July 2020. But it shouldn’t take long in any case to find all of those claims legitimate or not.
Disclaimer:
This article has only intended for information purposes. Neither the company nor the author shall liable, directly or indirectly, for any damage or loss caused or alleged to result from or in connection with the use or reliance on any content, goods or services referred to in this article.
Published at Mon, 17 Feb 2020 13:04:31 +0000
