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.

Sign up for GitHub

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

chore: update 0069-VCBS-094, validator key treated like any other for… #2223

Merged
merged 2 commits into from
Mar 27, 2024
Merged

chore: update 0069-VCBS-094, validator key treated like any other for… #2223

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a150533
chore: update 0069-VCBS-094, validator key treated like any other for…
wwestgarth Mar 25, 2024
000d500
Merge branch 'colosseo' into align-with-core
wwestgarth Mar 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion protocol/0069-VCBS-validators_chosen_by_stake.md
View file
Open in desktop
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
Loading