KVORUM
lidoSource: Snapshot · #0xbb5c7f1b0ae30b502ec207cffa324b05f69d6024cc56d94b0ea8df69216de1c4

Lido on Polygon V2 upgrade

succeededDec 12, 2022, 04:00 PM UTCsignaling · non-bindingbyDB0xdbbc…1cb6View on Snapshot ↗

01Summary

AISummary by Kvorum

An AI summary is not generated yet. Read the description →

02Description

267 words

Following the successful launch of Lido on Polygon V1, we’ve been working hard incorporating stakeholder feedback to make marked improvements in reducing both staker as well as node operator friction. As a result, we’ve come up with a V2 of Lido on Polygon that makes fewer compromises, eases operator entry and exit, and provides a smoother flow for users and network participants. This version not only brings nice-to-have features for node operators participating in the Lido on Polygon protocol, but also reduces the gas needed for depositing and withdrawing staked tokens through the Lido on Polygon protocol.

As we are committed to the values put forward by the community and the DAO, this upgrade will enable us to onboard a new set of node operators and further decentralise the Polygon network while providing options for more top tier node operators to join the Lido family.

TL;DR change log:

  • Rebalancing stake among validators on deposits and withdrawals
  • Simplified logic for node operator registry
  • No need to transfer validator ownership to Lido’s smart contracts
    • Polygon staking NFT (ownership) migration for existing V1 Node Operators
  • Finer role based access control
  • Gas optimizations for delegations/withdrawals and node operator controls
  • Code refactoring for readability and maintenance
  • Small fixes and code improvements

Security audit

All the contracts went through internal reviews by Lido core team and Shard Labs before they were sent for the professional audit by Oxorio.

Link to the report: https://github.com/lidofinance/polygon-contracts/tree/main/audits/v2/oxorio

Audited commit hash: 6b18e23ae258ff0aa84aecb82d8498f3c52f29e4

If this proposal is supported, Lido on Polygon team will make the upgrade through manager-multisig.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

0 total

This proposal carries no on-chain actions.

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.