Since the August 8th crisis, the organisation has found itself in the crossfire of regulatory scrutiny and unnecessary censorship. On such actions that attempt to restrict usage of the protocol, the graph censored the tornado subgraph on their hosted service. This resulted in the inability of the application to index deposit events for withdrawals and such proof generation. Essentially restricting normal usage of the protocol through the official interface.
While the frontend did have logic to fall back on cached events, it was not functional out of the box. Unfortunately, it took two independent builds to resolve these problems entirely, as the frontend had some undesirable logic that caused further issues.
In the case of Nova, it was dependent on the official Gnosis assigned RPC endpoint, which strangely experienced downtime after the crisis for amount of time - but was eventually restored. To negate reliance on one provider, a simple RPC resolver was developed and assigned as the Gnosis RPC endpoint. Additionally, SecureRPC was set as the default Ethereum endpoint in place of the censored Infura endpoint.
I undertook efforts to entirely resolve these conflicts, the solution builds have been deployed live under the following IPFS hashes, and assigned to the community-managed ENS for the past 2 weeks. No critical issues have been reported, thus seeming safe to bring into production and restore usage.
Classic (tornadocashcommunity.eth) [source code]
bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa
Nova (nova.tornadocashcommunity.eth) [source code]
bafybeifj3aynom2v5crx5cxrysgcgtvbwaejucxxpqacoe3zg7ysaua5sm
Furthermore, the need to update the official ENS’s IPFS content is because of the community social links. To those not aware the old community Discord’s invite link was namespaced attacked since its deletion. The adversaries are now luring in unaware potential users and exploiting them for their inexperience, Discord will also not do anything to resolve the problem.
This brings up the discussion of either:
- replacing all the social links with the new community substitutes (as implemented in the community build)
- removing all social links, the argument being to negate the liability of management
A draft implementation has been authored to enact this proposal and shall be finalised in the next few days. Please express your opinions and critiques on it or the basis of the proposal, as it will be going live shortly.