Skip to content

Commit

Permalink
chore: update 0069-VCBS-094, validator key treated like any other for…
Browse files Browse the repository at this point in the history
… spam on the multisig thing (#2223)
  • Loading branch information
wwestgarth authored Mar 27, 2024
1 parent bace2df commit d04bbcb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion protocol/0069-VCBS-validators_chosen_by_stake.md
Original file line number Diff line number Diff line change
Expand Up @@ -570,7 +570,7 @@ Setup a network with 6 nodes (3 validators, 2 ersatz validators, 1 pending valid
- Verify that no rewards are paid out on the first epoch.
- Update all multisig contracts by removing the demoted validator, and adding the new tendermint validator.
- Verify that rewards are paid out at the end of the epoch.
1. Any vega key with number of governance tokens more than or equal to `spam.protection.minMultisigUpdates` or a vega key that belongs to a validator can submit a request to the vega network to obtain the signature bundle that would update the multisig signers to be the keys of the current consensus (tendermint) validators up to `network.validators.multisig.numberOfSigners`. This request can only be submitted `spam.protection.max.MultisigUpdates` times per epoch per vega key per registered EVM/ERPC asset chain (alternatively the request will provide the update bundles for all the chains). Once multisig uses weights it will also include the correct weights for all multisig contracts. (<a name="0069-VCBS-094" href="#0069-VCBS-094">0069-VCBS-094</a>)
1. Any vega key with number of governance tokens more than or equal to `spam.protection.minMultisigUpdates` can submit a request to the vega network to obtain the signature bundle that would update the multisig signers to be the keys of the current consensus (tendermint) validators up to `network.validators.multisig.numberOfSigners`. This request can only be submitted `spam.protection.max.MultisigUpdates` times per epoch per vega key per registered EVM/ERPC asset chain (alternatively the request will provide the update bundles for all the chains). Once multisig uses weights it will also include the correct weights for all multisig contracts. (<a name="0069-VCBS-094" href="#0069-VCBS-094">0069-VCBS-094</a>)
1. Replace a validator with a new node via promotion/demotion. Ensure that rewards are paid out at the end of the epoch if all multisigs are updated to match the new validator. (<a name="0069-VCBS-091" href="#0069-VCBS-091">0069-VCBS-091</a>)

### Re-Issuing Signature Bundles by non Validators
Expand Down

0 comments on commit d04bbcb

Please sign in to comment.