Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
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
Add GovernorSequentialProposalId extension for sequential numbers on proposals #5290
Add GovernorSequentialProposalId extension for sequential numbers on proposals #5290
Changes from 11 commits
a25d139
a4ee283
e34a8b9
3cf1b80
9063080
8755aa6
c52f001
d9f3477
b063a61
19dfdf8
185b6a3
cb91e76
5ff56da
f0e9fb5
becc77a
8ffad72
3e49fb9
41d49c4
f8cfe02
76d57a2
74bdb35
3206080
c174090
9786e76
df711fe
a04b47f
2de3660
da959cd
e037708
fdea2cc
9b42d64
1dcb637
9ec9b40
99a4126
98ee374
1526974
512aa40
4791572
0502607
b931eea
0808e8c
a1194af
8d532ec
7a78f2f
df16ef1
b10f9be
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add a big caveat about decreasing the proposal count. I'd consider enforcing it in a require statement too, not sure if there are significant downsides to that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The use-case that @arr00 metionned that someone may set the count to type(uint256).max to (temporarily) disable proposing until the correct number is set.
IMO that usecase (prevent any proposal from being submitted could be more cleanly done using the proposal threshold).
This is the require I proposed: #5290 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would like to get @wildmolasses thoughts here. I'm leaning towards pushing the above approach of just using the proposal threshold.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I'd keep that use case separate. But I do think it's a concern if setting the count to the max uint permanently blocks the governor from functioning... So this is why I'm not all in on enforcing that the update is an increase. A safer thing would be to allow increases of some reasonable size (like uint32), it seems arbitrary but I think it works.