Add retweet etchebeblock with media welcome tornadocash to etc your deployment

[etc-contribunator]

This Pull Request creates a new retweet of https://x.com/EtcHebeBlock/status/1940089711525339374 with 1 image.

---

Created using the ETC Contribunator Bot

[github-actions]

Found 1 new .tweet file(s)

✅ Valid Tweet

Retweeting https://twitter.com/EtcHebeBlock/status/1940089711525339374

🚀 Welcome #TornadoCash to $ETC !
Your deployment will enhance privacy on #EthereumClassic .
'Code is law' in action.
#ClassicIsComing #CodeIsLaw #DeFi #ETCArmy #ETC

---

Updated preview using b81652a generated by Twitter, together!

[realcodywburns]

lgtm

link updated

[chris-mercer]

@IstoraMandiri I forget if we use the eth_classic account to post dapp announcements, I remember it was stricter. Is it ETC_Network account that dapps get posted on? Can you remind me on the guidelines?

[realcodywburns]

✅️Dignity: No obscenities, explicit language, racism, sexism, etc.

✅️Neutrality: No attacking or promoting of non-ETC projects, no drama.

✅️Seriousness: No memes, jokes, quips, hot takes, etc.

✅️Accuracy: No linking to overly opinionated, biased or unverifiable information.

✅️Relevance: No spam, non-ETC related content, limit tweets about the same topic.

✅️Subtlety: Don't tell people to buy ETC directly, instead tell them why.

✅️Safety: No links to scams, no encouraging the purchase of assets.

Third Party Projects

✅️Must be relevant to ETC.

✅️Can be retweets, but must contain disclaimers (e.g. do your own research).

✅️Large projects from established teams that are well known to the crypto-Twitter community and have been operating for at least 2 years are allowed.

[chris-mercer]

👋 Thanks for the submission. I’d like to raise a concern before we move forward with retweeting this from the main @eth_classic account.

Based on reports from the Tornado Cash community and lead contributors, the contracts linked in this deployment are not the canonical Tornado Cash contracts that follow the standard deterministic deployment method. Instead, they appear to be modified versions which introduce:

• Non-standard fee logic, potentially for personal gain;
• UI-level code changes that obscure function behavior;
• And regulatory risk due to changes that may violate Tornado Cash’s original audit assumptions and operating model.

Specifically, the [Tornado Cash community alert](https://discord.com/channels/223674353001168906/223674353001168906/1382629508061990954) outlines that:

“These contracts were not deployed using the standard deterministic deployer (0xce0042b868300000d44a59004da54a005ffdcf9f) and include unnecessary modifications that introduce money transmitter risks and contradict Tornado Cash principles.”

Given that the UI and contracts in question differ from the audited and widely accepted versions, endorsing this deployment from the main ETC account may unintentionally validate a non-transparent or deceptive implementation, and expose us to reputational and compliance risk.

🛑 I recommend we pause this tweet for now and instead:

1. Encourage the Tornado Cash devs who deployed the canonical contracts (without modifications) to submit a PR for review.
2. Direct dapp announcements like this to the more appropriate @ETC_Network or a separate ecosystem channel, rather than Ethereum Classic’s main brand account.

cc: @realcodywburns @IstoraMandiri @ethereumclassic/tweeters

Here is the original discord message:
https://discord.com/channels/223674353001168906/223674353001168906/1382629508061990954

Hello, I am the OP who posted the contract deployments above and the dev of github.com/tornadocontrib/tornado-scripts codeberg.org/tornadocash/tornado-withdraw who have written Tornado Cash UI from scratch and who have served as a Tornado Cash TG Community Mod for more than a year ( From 2023 Nov ~ 2025 Feb ).

1. People are opposed because you ( Hebeswap ) have deployed a modified unaudited contracts to gain personal fees while those are unnecessary and against the principles of Tornado Cash

Every Tornado Cash pools must follow the same contract addresses & code and it is possible because there is a deterministic deployer which if you have the same code it would result in same contract address

For example, this is the contract used for deterministic deployment

0xce0042b868300000d44a59004da54a005ffdcf9f ( go to etherscan for the code )

Because you have modified the code to grief fees and modify UI codes with poorly written hacky functions it was rosen to oppose it as well.

](https://discord.com/channels/223674353001168906/223674353001168906/1382629508061990954)

[chris-mercer]

Due to global compliance risks and the potential for public confusion, we ask that you do not use the name "Tornado Cash" in connection with modified contracts. This may be misleading to users and regulators alike.

If you're proposing changes, please submit a PR using the canonical Tornado Cash contracts unmodified for review first. Any improvements or forks should be clearly differentiated and submitted separately after that baseline is established.

Thanks for understanding.

Per conversation in pr