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

Multiparty Trustless DKG Multisig Infrastructure #78

Open
poroburu opened this issue Jun 16, 2022 · 1 comment · May be fixed by #152
Open

Multiparty Trustless DKG Multisig Infrastructure #78

poroburu opened this issue Jun 16, 2022 · 1 comment · May be fixed by #152
Milestone

Comments

@poroburu
Copy link

  1. Can horcrux be used with a trustless distributed key generator to enable multisig validators? The current migration documentation requires a trusted party to distribute the key shares.

Dev (Osmosis) co-authored a handy article that references a 'rust implementation of multiparty Ed25519 signature scheme' repository that supports trustless DKG:

https://medium.com/blockchain-at-berkeley/alternative-signatures-schemes-14a563d9d562
https://github.com/ZenGo-X/multi-party-eddsa

Signing seems to be a blocker for DAO validators. With Interchain Accounts, Juno DAOs can create validator infrastructure on Akash. But how DAOs will securely supply cryptographic keys to the infrastructure for remote signing is not apparent.

  1. Can horcrux nodes be geographically distributed? For example, Raspberry Pi nodes running on the edge with the multisig holder. While the sentry full nodes are hosted in the cloud.
@poroburu poroburu changed the title Multiparty Trustless DKG Multisig Multiparty Trustless DKG Multisig Infrastructure Jun 16, 2022
@jackzampolin
Copy link
Member

  1. This would require some cryptography work. Here is a library in go (https://github.com/taurusgroup/frost-ed25519) that could be used to do this. Would require some changes to horcrux that we are happy to collaborate on.
  2. Yes you can run them geographically distributed.

@boojamya boojamya added this to the v3.0.0 milestone Aug 16, 2022
@agouin agouin linked a pull request May 18, 2023 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants