Increasing number of active Easy Track motions run simultaneously (restart)
TL;DR
This is a new round of voting for the proposal to increase the maximum number of active Easy Track motions run simultaneously. The previous voting proposal did not gain a minimum quorum, as votes split between two options for increase.
This time we suggest you to choose between “Increase by 8 to 20” and “No change”. We have chosen to propose “Increase by 8 to 20” this time, as adding 8 more motions is the option that is between previous ones. More details can be found on the Research Forum.
Background
In the last 2 weeks of February Lido protocol experienced an active inflow of several whales, which motivated Node Operators to request staking limit increases. This resulted in Easy Track congestion as most new motions were related to increasing node operator staking limits – since February 27, a day after a huge influx of stake from one whale (200,100 ETH), there were only 16 falling under “Increase node operator staking limit” category, apart from other open categories “Top up referral partner”, “Top up LDO referral partner”, “Top up LDO TRP”.
Due to the current limit on the number of concurrent Easy Track motions (12), other actors needed to wait once some motion was completed and enacted to submit theirs. More details can be found on the Research Forum.
Proposal
We propose to increase the limit of active/ongoing Easy Track motions, as under the current settings there could not be more than 12 simultaneous motions. The absolute top the Easy Track contract allows is 24 at the same time (this is hardcoded, and can be changed only via a contract change and redeployment of the whole Easy Track setup, but this is not the issue of this proposal).
Based on this and to avoid an unnecessary overburden in the future, when it is unneeded and may impose a loss of potential profit, we propose to increase by 8 to 20 active concurrent motions.
Please vote
You are welcomed to vote below and help to decrease Easy Track votings overburden in the future thanks to your choice.
Off-Chain Vote
Loading…
- Author
zuzu_eeka
- IPFS#bafkreic
- Voting Systemsingle-choice
- Start DateApr 07, 2023
- End DateApr 14, 2023
- Total Votes Cast53.2M LDO
- Total Voters1.63K
Timeline
- Apr 07, 2023Proposal created
- Apr 07, 2023Proposal vote started
- Apr 14, 2023Proposal vote ended
- Jul 21, 2025Proposal updated