Book a demo
Deployment · 1:54 min

Governance handover

After launch no single key can upgrade the contracts or grant roles. Control moves to the operator's multisig behind a timelock of 48 hours.

Narration in English, subtitles in your language. Recorded on the demo platform with demo data and the demo stablecoin tUSDC.

Who takes part

  • Platform owner, holder of the deployment key
  • Operator's multisig

Steps

  1. The contracts are deployed, and the deployment key is still their administrator.
  2. The handover takes the address of the operator's Safe multisig and the list of asset tokens.
  3. The script deploys a timelock with a 48-hour delay, proposed and executed by the multisig, and makes it the administrator of the factory, registries, sale, market and payout contracts and asset tokens.
  4. The fee recipient moves to the multisig, the multisig gets the pause role, and the deployment key renounces its roles.
  5. On-chain checks confirm that the timelock is the administrator, the deployment key is not, and the backend agent keeps only its operational role.

Result

  • Upgrades and role changes are scheduled by the multisig and executed after 48 hours.
  • The multisig can pause the market and payouts at once, while lifting a pause goes through the timelock.