Tellor3 Upgrade

Published on: 21.05.2021

Tellor deployed a small but important Tellor3 update to the Tellor contracts.

The purpose of the tellor3 upgrade is to ensure this never happens again, and to transition away from the migration protocol we’ve been undertaking.

🔹The tellor3 upgrade has two main aspects:

Improved upgrade procedures

The contract we migrated to in order to fix the Tellor system after the February 15th error contains an admin privileges, which was included to get Tellor back up and running quickly and ensure the token migration went smoothly. Once we achieved this we began working on ways to more robustly verify the processes in our upgrade procedure. We’ve successfully added this new verification method that will entirely prevent another major error of this kind.

Removal of migrator contract

Part of the migration to the new Tellor contract that fixed our system was the addition of a contract that contained certain functions allowing holders of TRB to migrate their old tokens to the new TRB. Now that the token supply is nearly fully migrated, the tellor3 upgrade is getting rid of the migrator contract to minimize potential vulnerabilities. Independent of the migrator contract there will remain two accessible migration functions: ‘migrate’ which any user can call and ‘migrateFor’ that helps the team transition users locked in unique contracts or pools. Both of these functions still exist for those yet to migrate.

🔹Going Forward

One of their main goals in this entire migration process was to make sure we came out of this better than ever. Ultimately, this tellor3 upgrade is a step forward in the maturity and strength of Tellor, by providing with a secure path back to token governance.