Description

The provide_sequencer_stake function part of the sequencer staking pallet does not correctly enforce the maximum number of registered sequencers.

Impact

More than the maximum intended number of sequencers may be able to register by using provide_sequencer_stake.

Recommendations

Check the number of currently registered sequencers as a precondition to accepting new sequencer registrations.

Remediation

This issue has been acknowledged by Gasp, and a fix was implemented in commit 8d96e174↗.