Summary:
- Professor Matthew D. Green of the Computer Science Department at John Hopkins University has reuploaded the Tornado Cash Source Code on Github.
- Prof. Green claims the Tornado Cash code is relevant for teaching and research purposes.
- He explained that he understood why Github would remove the code given the OFAC sanctions, but a loss of Tornado Cash would be a loss to science.
Tornado Cash’s source code has been handed a second chance as Professor Matthew D. Green of the Computer Science department at the John Hopkins University has reuploaded it on Github for research and teaching purposes.
According to Professor Green, Github succeeded in removing all original copies of Tornado Cash’s source code repositories.
However, Github did not remove all forks made by Tornado Cash users. As a result, the source code Professor Green unloaded ‘is simply another fork of the repositories they collected.’ He added that several of these forks exist and are being collected or forked by Tornado Cash community members.
Tornado Cash has Helped Students Create Amazing Projects.
Professor Green pointed out that as a researched and instructor at John Hopkins, Tornado Cash and Tornado Nova code has been instrumental in teaching ‘concepts related to cryptocurrency privacy and zero-knowledge technology.’
As a result, the code has been helpful to students who have created amazing projects. Therefore, losing Tornado Cash’s source code would be ‘harmful to the scientific and technical communities.’
Offline Copies Exist that Can be Uploaded Elsewhere
He also added that he understood why Github would want to pull down the Tornado Cash source code given the US Treasury sanctions. Github is a private company and has every right to remove the code as ‘a risk mitigation procedure.’
However, he chose to reupload the code on Github since it is a globally known hub for software code and developers. He explained that there were offline copies that he could republish elsewhere should Github remove his upload. He said:
© Solana Daily Brief, Inc. All Rights Reserved. This article is for informational purposes only. It is not to be used as legal, tax, investment, financial, or other advice.GitHub may see things differently: if so, that would be fascinating. It goes without saying that I have made offline copies of all these repositories and will immediately re-publish them in a different location (such as a University server) if this site becomes inaccessible.