Unauthorized 0x7bA7 Addresses Lack TUSD Contract Access and Team Affiliation

TrueUSD's recent announcement on X platform states that there needs to be clarification regarding the address (0x7bA7EF06A2621267f063eF2DB2d482D5B507D8b3). This address has no permissions over the TUSD smart contract; it is specifically designated for token deployment. It has no authority over the current TUSD contract or user token assets and has no impact on the operation of TUSD. The address is not owned or controlled by the TUSD team, and there is no affiliation between the TUSD team and this address.

Since the end of 2020, the TUSD team has gained ownership of the TUSD contract. TUSD tokens are protected by the smart contract, which is securely owned and managed by the TUSD team.

Earlier today, TrueUSD clarified in its announcement on October 16th that it has “no relationship” with TEURO. However, blockchain analytics company ChainArgos points out that the TEURO token contract was deployed using one of TrueUSD's private keys. Given that TrueUSD acknowledged a hack no later than September 18th, and TEURO was deployed ten days ago, there appears to be only one explanation:

• Someone has access to some of TrueUSD's private keys.

• This suggests that TrueUSD may not have disclosed the full extent of the hack.

• Considering that someone (Sun Yuchen) successfully minted 850 million TUSD three days before the widely recognized hack date.

ChainArgos suggests that the entire situation is particularly dangerous, implying that it is possible that the reserve of TUSD has been stolen by someone holding the company's private keys.