-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Collective pallet: max proposal weight #13771
Collective pallet: max proposal weight #13771
Conversation
bot rebase |
…-max-proposal-weight
Rebased |
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.
Personally I would probably favor a disapprove_proposal
that can be initiated by a simple majority of collective members to cancel a call.
let proposal_weight = proposal.get_dispatch_info().weight; | ||
ensure!( | ||
proposal_weight.all_lte(T::MaxProposalWeight::get()), | ||
Error::<T, I>::WrongProposalWeight | ||
); |
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 proposal weight is already added to the weight of propose
if threshold < 2
. So, we would not even add this tx to a block when the weight is too big. TLDR: This should not be required.
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.
But yeah, to have the properties as do_propose_proposed
it makes sense.
bot merge |
Error: Github API says paritytech/cumulus#2410 is not mergeable |
bot rebase |
…-max-proposal-weight
Rebased |
bot merge |
Error: Github API says paritytech/polkadot#6983 is not mergeable |
bot merge |
* collective: max proposal weight * fix test --------- Co-authored-by: parity-processbot <>
Introducing a limit for the weight of the proposed call.
polkadot companion: paritytech/polkadot#6983
cumulus companion: paritytech/cumulus#2410