**Adding Support for the New TUSD Implementation Address** The upcoming executive vote will contain support for the new TUSD implementation contract ([0xd8D59c59Ab40B880b54C969920E8d9172182Ad7b](https://etherscan.io/address/0xd8d59c59ab40b880b54c969920e8d9172182ad7b)), which will allow resuming of TUSD collateral operation. This is a preliminary step that will allow vault owners to withdraw their collateral (if they wish to do so) as part of the TUSD offboarding [process](https://forum.makerdao.com/t/attention-tusd-a-users-collateral-offboarding/13927). Although the reasoning for this change was communicated in an ongoing forum [thread](https://forum.makerdao.com/t/tusd-disabled-due-to-unannounced-token-upgrade/2747), this post aims to summarize the issue. Since the TUSD contract is upgradeable, its actual implementation contract may change. As part of the Maker collateral integration a security measure was added to the GemJoin contract that disables the ability to insert or withdraw collateral if that implementation contract changes. In such a case the Maker governance has to approve the new implementation for use. The latest implementation [change](https://etherscan.io/tx/0x125823f2914e4f14e06b9b1b30fe9dd9512b36354cc1f6c063118c4fe03d8287) from the TUSD team happened on February 24th, after a security issue was found in the Compound TUSD integration, and reported by [OpenZeppelin](https://blog.openzeppelin.com/compound-tusd-integration-issue-retrospective/) and [ChainSecurity](https://medium.com/chainsecurity/trueusd-compound-vulnerability-bc5b696d29e2). The issue originated from the fact that the TUSD contract allowed more than one entry point (otherwise known as a proxy contract), while the Compound implementation assumed only one existed. A malicious actor could have used the additional entry point to send the underlying collateral of the TUSD Ctoken to the Compound Timelock contract. This would have reduced Compound’s TUSD to cTUSD exchange rate and would open up profit opportunities for the attacker on behalf of other Compound users. The new TUSD implementation has a small change to allow only one entry point, which is the newer TUSD proxy contract. This solves the above issue. The change was reviewed by the Protocol Engineering team and approved for use.