Cooldown functionality in Treasury

CarmineOptions / konoha

A toolkit for DAO-like governance on Starknet

Apache License 2.0

30 stars 41 forks source link

Cooldown functionality in Treasury #128

Closed tensojka closed 1 month ago

tensojka commented 3 months ago

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 commented 3 months ago

Thanks

Oshioke-Salaki commented 3 months ago

Hello please can I take this up?

ScottyDavies commented 2 months ago

Hello @tensojka i would love to take up this issue. ETA 4-6 days

tensojka commented 1 month ago

Done in #131