Skip to content
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

Closed
cwgoes opened this issue Apr 8, 2022 · 8 comments
Closed

Specs: Ethereum bridge recovery multisig #170

cwgoes opened this issue Apr 8, 2022 · 8 comments

Comments

@cwgoes
Copy link
Contributor

cwgoes commented Apr 8, 2022

As discussed with @adrianbrink

  • Require all Namada validators to create an Ethereum address and sign it
  • Create a threshold 2/3 multisignature contract on Ethereum with voting weights and addresses of the validators
  • Keep that contract up to date when there are validator set updates
  • After a delay period with no regular updates, the contract can recover the funds in the Namada bridge contract
@cwgoes
Copy link
Contributor Author

cwgoes commented Apr 11, 2022

cc @Fraccaman

@cwgoes cwgoes mentioned this issue Jul 8, 2022
8 tasks
@Fraccaman
Copy link
Member

The current contract implements a recovery mechanism but there is no delay period. How should that be implemented?

@cwgoes
Copy link
Contributor Author

cwgoes commented Jun 8, 2022

We should keep a timestamp of the last (regular) header update from Namada, and recovery from the multisig can only be initiated if now - lastUpdateTimestamp > delayPeriod. delayPeriod can be a week or something like that.

@cwgoes cwgoes transferred this issue from another repository Jul 8, 2022
@cwgoes cwgoes changed the title Ethereum bridge recovery multisig Specs: Ethereum bridge recovery multisig Jul 8, 2022
@cwgoes
Copy link
Contributor Author

cwgoes commented Jan 12, 2023

@Fraccaman @batconjurer have we implemented a recovery multisig yet, or not yet?

@batconjurer
Copy link
Member

@cwgoes Not yet, no

@sug0
Copy link
Contributor

sug0 commented Jul 18, 2023

I presume this is related to anoma/ethereum-bridge#62 ??

@cwgoes
Copy link
Contributor Author

cwgoes commented Aug 17, 2023

Yes, unless you had another, different plan for enabling emergency withdrawals.

@sug0
Copy link
Contributor

sug0 commented Aug 17, 2023

@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

@sug0 sug0 closed this as completed Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants