-
Notifications
You must be signed in to change notification settings - Fork 947
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specs: Ethereum bridge recovery multisig #170
Comments
cc @Fraccaman |
The current contract implements a recovery mechanism but there is no delay period. How should that be implemented? |
We should keep a timestamp of the last (regular) header update from Namada, and recovery from the multisig can only be initiated if |
@Fraccaman @batconjurer have we implemented a recovery multisig yet, or not yet? |
@cwgoes Not yet, no |
I presume this is related to anoma/ethereum-bridge#62 ?? |
Yes, unless you had another, different plan for enabling emergency withdrawals. |
@cwgoes was just checking. all namada side things are complete, then. only the smart contracts need to be updated, so I'm closing the issue on this side |
As discussed with @adrianbrink
The text was updated successfully, but these errors were encountered: