Skip to content

Using CHURP as a decentralised admin for smart contracts  #8

@alonmuroch

Description

@alonmuroch

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions