Multisig and timelock
Blizz was developed by a team of industry veterans with significant previous experience working on DeFi projects. We choose to remain anonymous, but rest assured we are qualified for the task at hand. The codebase has been well tested and peer-reviewed, and is currently undergoing a formal audit which we expect to conclude within the next three (3) weeks after launch. The audit results will be published as soon as it is completed.
As Blizz is based on Aave, many of the core contracts are upgradeable by the owner. We understand that anonymous devs with the power to upgrade contracts may rightfully make some users feel uncomfortable. To mitigate these concerns, ownership of all Blizz smart contracts will be placed behind a Timelock contract with a two day delay for any action. We will publish the address to this contract prominently, and inform the community prior to any admin-related actions involving the timelock. We encourage community members to monitor inbound transactions to the timelock.
While we have taken every precaution to ensure the safety of user funds and instill confidence in our work, we still must remind users that this is all new technology and not without risk. Do not deposit more than you can afford to lose. If you are nervous about security you may wish to wait until the protocol has been operational for some time without incident before interacting with it.
The Blizz multisig is a 3/5 safe with non custodial admin rights over the Blizz protocol.
The multisigs can be found at those addresses:
Emergency multisig: 0xb05312835edA7835Dd820C7C5fCF646778c25B7A
Owner multisig: 0x60Cae9bCC9324fa6B7f5423dfF3ee3f3f83698A8
All admin rights to the Blizz protocol are owned by a TimeLock contract with a 2 day delay. The timelock is deployed at:
Timelock: 0x3160806b5976c2269837afD44A7685103b0474f8
The Blizz team will always announce admin related actions prior to queuing them in the timelock.
Last modified 1yr ago