mirror of
https://github.com/serai-dex/serai.git
synced 2025-12-08 12:19:24 +00:00
Address review comments from #53
This commit is contained in:
@@ -2,19 +2,21 @@
|
||||
|
||||
Validator Sets are defined at the protocol level, with the following parameters:
|
||||
|
||||
- `index` (VS): Validator set index, a global key atomically increasing
|
||||
- `index` (VS): Validator set index, a global key atomically increasing
|
||||
from 0.
|
||||
- `bond` (Amount): Amount of bond per key-share of this validator set.
|
||||
- `coins` (Vec<Coin>): Coins managed by this validator set.
|
||||
- `bond` (Amount): Amount of bond per key-share of this validator set.
|
||||
- `coins` (Vec\<Coin>): Coins managed by this validator set.
|
||||
|
||||
At launch, there will solely be validator set 0, managing Bitcoin, Ethereum,
|
||||
USDC, DAI, and Monero.
|
||||
|
||||
### Multisig Management
|
||||
|
||||
Every validator set is expected to form a multisig per curve required by its
|
||||
coins. This multisig is secure to hold funds up to 67% of the validator set's
|
||||
bond value.
|
||||
Every validator set is expected to form a t-of-n multisig, where n is the amount
|
||||
of key shares in the validator set and t is `n / 3 * 2 + 1`, per curve required
|
||||
by its coins. This multisig is secure to hold funds up to 67% of the validator
|
||||
set's bond value. If funds exceed that threshold, there's more value in the
|
||||
multisig than in the supermajority of bond that must be put forth to control it.
|
||||
|
||||
### Participation in the BFT process
|
||||
|
||||
|
||||
Reference in New Issue
Block a user