Skip to content

Conversation

@LHerskind
Copy link
Contributor

1) Only rollup stakers have a say in governance, meaning that end users have no direct say in governance;
2) The voting power from stake can be delegated, and will by default be delegated to the rollup itself, which will follow the signalling;
3) "Willing" stake can be moved by governance and bypass the exit delay.
4) At the end of execution of proposals from the governance proposaler the canonical instance must have >X fraction of stake;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
4) At the end of execution of proposals from the governance proposaler the canonical instance must have >X fraction of stake;
4) At the end of execution of proposals from the governance proposer the canonical instance must have >X fraction of stake;

```


We then will have this information for EVERY rollup instance (only possible to add a new if it is the current canonical as per the Registry).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't look like we consult the registry in the current implementation PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, ye you are right we don't currently. There is a bit of detail later talking about using the governance for it to avoid having to deal with the issues of incompatible rollups and such. Will get rid of the text in parenthesis.


For the `canonical` voting power, a special case using the `MAGIC_CANONICAL_ADDRESS` is to be used, note however, that unless there is a separate checkpoint around when the canonical is moved around, it might be the case that the power for a vote in the past is passed along in case of an upgrade (edge case).

The `GSE` must have logic to allow the cast of votes from anyone with voting power, so if a staker does not agree with the rollup, there is a way for him to vote against it.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Details on how this will be done would be good.

> [!info] Point of discussion
>Is it desired to always require > 2/3 of stake stake to be on the canonical for the proposal to be passable, or is it acceptable that this is bypassed when a proposal is made using the `proposeAndLock`?

To support requirement 3, we will alter the `GovernanceProposer` such that it any proposals from it will be extended with a check at the end that the stake held in the canonical is >2/3 of the stake in the `GSE` (instance directly + canonical).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this include non-upgrade proposals?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, does this mean that if a whale comes along and stakes over a third in an old version then the governance proposer is bricked?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes and yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants