Distributed Key Generation
Last updated
Last updated
To confirm bridge transfers, validators use distributed key. Validators participate in distributed key generation (DKG) process to come up with individual secret key shares, which later allows them to create signatures from mutual account. No one has access to full private key, from which signatures are created.
Once validators list is changed, due to staking or slashing, they participate in four rounds of key generation. Each next round requires completion of previous round by all the DKG participants. Results of each round is written to special . Round result includes public data, for all participants, encrypted private data for other participants and encrypted intermediate data for validator itself. Intermediate data in contract allows to restore validator secret share, even if node is restarted from scratch and synchronized from the first block.
It's not a secret that we live in a not ideal world and we cannot be sure that validators will run their nodes with 100% uptime, or that validators won't submit any corrupted data as a round results.
To address this issue, validators, during DKG process can vote against misbehaving participants on-chain and restart the DKG process without them. Fortunately that we use allows to identify misbehaving participants. If validators misbehave too often, they are being .