Github Partially Restores Tornado Cash Codebase, Open Source Code Set to Read-Only Mode – Bitcoin News

Microsoft’s Internet hosting and software development subsidiary has partially discontinued Tornado Cash Stores following recent sanctions imposed by the US Treasury’s Office of Foreign Assets Control (OFAC). GitHub’s decision follows the U.S. Treasury Department’s update to the public, noting that Americans can copy, view, and discuss open source code. Github’s partial restore repository allows visitors to view the Tornado Cash codebase in read-only mode.

Github restores Tornado repositories in read-only mode

The cryptocurrency community has been in discussion after Internet hosting and software development platform Github decided to return part of Tornado Cash’s open source code to the platform. In the year On August 8, 2022, US Treasury Department regulator OFAC sanctioned Ethereum mixer Tornado Cash and several Ethereum addresses associated with the platform. When the OFAC sanctions were published, third-party platforms began to take action, and one open-source developer was banned from Github.

Roman Semenov, the developer of the software, said: “My Github account has been suspended he said. by the time. “Is it illegal to write open source code now?” Additionally, Microsoft-owned Github has removed the Tornado cache codebase repositories, and no one can access the code through the software development platform.

On September 13, 2022, after much criticism from the crypto community, the US Treasury updated the public about Americans linking themselves to Tornado Cash. For example, the sanctions will not apply in full to US persons who submitted an Ethereum mingling application before August 8. If this is the case and a US person still holds funds on the application, “you may request separate authorization from OFAC to participate. In transactions with the subject’s virtual currency.

OFAC America allows people to view, discuss, and educate themselves about sanctioned platforms and open source code through written publications.

An update to OFAC’s Frequently Asked Questions (FAQ) also explains open source code related to Tornado Cash. “U.S. persons copying open source code and making it available to others online, as well as discussing, teaching, or incorporating open source code in written publications, are not prohibited by U.S. sanctions laws,” the Treasury Department notes.

Ten days ago, following an update to the FAQ, Ethereum developer Preston Van Loon reported Github has partially restored the Tornado Cash codebase and unbanned codebase contributors. “Github has banned the Tornado Cash organization and contributors from the platform,” the developer said. “Everything seems to be in ‘read-only’ mode, but this is from a penalty block. I still encourage Github to undo all actions and restore the repositories to their original state,” Van Loon said. Added.

Tags in this story

block, code, editorial credit: Sundry Photography/, ethereum developer, Ethereum Mixer, github, Github Tornado Cash, OFAC, Office of Foreign Assets Control, open source code, partial restore, Preston Van Loon, read-only mode; Sanctions , Tornado Cash , Tornado Cash Contributors , Tornado Cash Organization , Treasury , US Treasury

What do you think about Github partially restoring Tornado Cash repositories? Let us know what you think about this in the comments section below.

Jamie Redman

Jamie Redman is the news lead at and a financial tech journalist based in Florida. Redman has been an active member of the cryptocurrency community since 2011. He is passionate about Bitcoin, open source code and decentralized applications. Since September 2015, Redman has written over 6,000 articles for News about the disruptive protocols emerging today.

Image credits: Shutterstock, Pixabay, Wiki Commons, Editorial Photo Credit: Sundry Photography /

DisclaimerThis article is for informational purposes only. It is not an offer or solicitation to buy or sell, or a recommendation or endorsement of any products, services or companies. does not provide investment, tax, legal or accounting advice. Neither the Company nor the Author shall be liable, directly or indirectly, for any damages or losses arising out of the use of or reliance on any content, goods or services referred to in this paragraph.

Source link

Leave a Reply

Your email address will not be published. Required fields are marked *