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

Using CHURP as a decentralised admin for smart contracts #8

Open
alonmuroch opened this issue Sep 13, 2020 · 0 comments
Open

Using CHURP as a decentralised admin for smart contracts #8

alonmuroch opened this issue Sep 13, 2020 · 0 comments

Comments

@alonmuroch
Copy link

Hi @bl4ck5un @mskd12 @wanglun1996 love your work!
One of the use-cases i think could be to distribuite an admin key for smart contracts.

Many smart contracts have some admin key for different operations (updating the contract, halting operations in case of an issue and more).
I was thinking that CHURP can be used (using BLS keys) as a way to distribute the admin key.

Setup is:

  • a set of V collateralised validators participate in a consensus protocol
  • each new epoch E, a new sub set of validators is chosen randomly
  • sub set from epoch E-1 rotates shares of the secret admin key to sub set at epoch E
  • any subset can collectively sign with the admin key above a certain threshold
  • they decide on what to sign by the consensus protocol
  • as long as V has 2/3 honest validators this scheme should be secure

The cool thing about it is that the actual actions can be arbitrary which can serve a wide verity of use-cases.

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

No branches or pull requests

1 participant