Cooldown functionality in Treasury

[tensojka]

In the case governance is hacked, the treasury needs to have a cooldown period (two days). Any transfer out from the treasury is subject to it. During the period, anyone from a list of guardians can come in and cancel not-yet-executed transfer.

Storage layout

transfer_on_cooldown: Map::<u64, Transfer>,
current_transfer_pointer: u64
guardian: Map::<u32, ContractAddress>

External functions:

execute_all_pending cancel_execution

assigned to @faurdent

[faurdent]

Thanks

[Oshioke-Salaki]

Hello please can I take this up?