TrueUSD: The address starting with 0x7bA7 has no authority over the TUSD smart contract and is not related to the team.

TrueUSD posted on the X platform that it should be clarified about the address (0x7bA7EF06A2621267f063eF2DB2d482D5B507D8b3) that this address has no authority over the TUSD smart contract; it is an address specifically designated for token deployment. It has no authority over the current TUSD contracts or user token assets, and has no impact on the operations of TUSD. This address is not owned or controlled by the TUSD team, and there is no connection between the TUSD team and this address. Since the end of 2020, the TUSD team has taken ownership of the TUSD contract. TUSD tokens are secured by smart contracts, which are securely owned and managed by the TUSD team. Earlier today, it was reported that stablecoin issuer TrueUSD clarified in an announcement on October 16 that it had “no relationship” with TEURO, but blockchain analysis company ChainArgos stated that the TEURO token contract is one of the private keys that uses TrueUSD Deployed. Given that TrueUSD admitted to being hacked as late as September 18th, and TEURO was deployed 10 days ago, there seems to be only one explanation here: 1. Someone has some private keys of TrueUSD; 2. This means that TrueUSD may not be telling the whole truth about the extent of the hack; 3. Considering that someone (Justin Sun) successfully minted 850 million TUSD 3 days before the recognized date of the hack. ChainArgos said the entire situation is particularly dangerous. In other words, it is at least possible that TUSD’s reserves were stolen by someone who holds the company’s private key.