🔗Security

TimeLock: All governance actions are delayed a minimum of two days by the time lock contract before they can be executed.

The Security Module mitigates the effects of disruptive proposals on the ecosystem by instituting a delay before executing the winning vote result.

The module wraps new code before deployment to the system and is held for final consideration for 48 hours, during which time all interested parties can review the code to ensure system integrity.

The public is encouraged to self audit the code. Check that the contract code is visible, if there is a default structure, check that it is implemented, make sure that what was voted is what is actually in the code, check oracle addresses (if used), changes in rates, check the runtime. Verify the entire contract and if there are errors encourage the negative vote of the same.

In the future, BLDT holders may want to develop special user interfaces or other voting interfaces.