Staking Router + Community Staking Module upgrade announcement

[Maksim_Kuraian]

Staking Router + Community Staking Module upgrade actions plan

Contributors from the Lido ValSet workstream have developed a detailed action plan based on the previously approved LIP-23, LIP-25 and LIP-26 proposals.

The objective is:

• Upgrade the Staking Router and related contracts.
• Upgrade the Accounting Oracle sanity checker.
• Add the Community Staking Module (CSM).

Recap and References

• Proposals published on the Lido Research Forum:

  • Staking Router 2.0;
  • Negative rebase sanity check;
  • Community Staking Module.

• The upgrade is based on the design supported by the Lido DAO through the snapshot votes:

  • LIP-23: Negative rebase sanity chek;
  • LIP-25: Staking Router 2.0;
  • LIP-26: Community Staking Module.

• The upgrade was successfully piloted on the Holesky testnet, which included:

  • Testing the Community Staking Module and related contracts
  • Testing the negative rebase feature
  • Testing deposits and withdrawals
  • Testing boosted validator exit mode
  • Testing vetting and unvetting keys
  • Testing module share thresholds
  • Testing accounting reports and reward distribution

• The solution passed audits by Ackee Blockchain and MixBytes

  • Ackee Blockchain Lido Community Staking Module Report 10-24.pdf
  • Ackee Blockchain Lido Staking Router v2 Report 10-24.pdf
  • MixBytes Lido CSM Security Audit Report.pdf
  • MixBytes Lido Oracle Security Audit Report 10-24.pdf

Technical Details

The following contracts were deployed in advance:

• Staking Router contracts;
• Community Staking Module contracts.

See the announcement above for details on the initial upgrade parameters.

Voting Script

The voting script, including all necessary upgrades for Negative Rebase, Staking Router 2.0, and Community Staking Module features, has been prepared and published on the forum. A full description can be found by following this link.

Tentative Upgrade Timeline

• Oct-22-2024 (Tue): Start Aragon voting.
• Oct-24-2024 (Thu): Main voting phase ends.
• Oct-25-2024 (Fri): Contingent on the voting outcome.
  • The objection phase and overall voting conclude. Enactment if passed.
  • Announce of new CSM UI.
• Oct-26-2024 (Sat): First post-upgrade Accounting Oracle report.
• Oct-28-2024 (Mon):
  • Announce of Node Operator Widget UI update.
  • Further minor protocol-related announcements.

Contingency Planning

The proposed upgrade has passed a rigorous security process. However, in the event of a failure during the upgrade:

• If the vote fails to reach quorum, a vote restart will be suggested.
• Operational delays or last-minute security concerns will be communicated, and new dates will be announced accordingly.
• A postmortem will be issued in case of any severe unforeseen issues.

Discussion

Any additional feedback or suggestions on this proposal would be highly appreciated.