Skip to content

Commit

Permalink
Merge pull request #246 from lidofinance/cms/lido-landing/scorecard
Browse files Browse the repository at this point in the history
Update Lido landing “scorecard”
  • Loading branch information
karinamaulitova authored Jan 13, 2025
2 parents 144d2ec + e3811a8 commit 881cc62
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions lido-landing/scorecard.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ rows:
- scorecard-attribute: "Withdrawal requests are automatically fulfilled"
categories: "Validator set"
self-assessment: "Good"
comments: "The Lido protocol has a [subsystem](https://{{ethereum_docs}}/contracts/withdrawal-queue-erc721#what-is-withdrawalqueueerc721) which can self-execute withdrawals with no human participation, apart from requiring Node Operators to maintain tooling (their own or [open-source alternatives](https://github.com/lidofinance/validator-ejector/)) to process requests (semi-)automatically. This subsystem ensures withdrawal requests can’t be cancelled (within a bounded period of time) and is designed to work even during chaotic tail-risk scenarios. The total volume of withdrawals processed since May 2023(withdrawals implementation) can be found on the [dedicated Dune dashboard](https://dune.com/embeds/2475364/4072036)."
comments: "The Lido protocol has a [subsystem](https://{{ethereum_docs}}/contracts/withdrawal-queue-erc721/#what-is-withdrawalqueueerc721) which can self-execute withdrawals with no human participation, apart from requiring Node Operators to maintain tooling (their own or [open-source alternatives](https://github.com/lidofinance/validator-ejector/)) to process requests (semi-)automatically. This subsystem ensures withdrawal requests can’t be cancelled (within a bounded period of time) and is designed to work even during chaotic tail-risk scenarios. The total volume of withdrawals processed since May 2023(withdrawals implementation) can be found on the [dedicated Dune dashboard](https://dune.com/embeds/2475364/4072036)."
- scorecard-attribute: "No operator has more than 1% of the total stake"
categories: "Validator set"
self-assessment: "Good"
Expand All @@ -48,7 +48,7 @@ rows:
- scorecard-attribute: "Withdrawal credentials are non-custodial being managed by a smart-contact maintained by LDO tokenholders"
categories: "Security"
self-assessment: "Good"
comments: "[All](https://twitter.com/LidoFinance/status/1646977448410480643) Lido on Ethereum participating validators use 0x01 (smart contract) withdrawal credentials."
comments: "[All](https://x.com/LidoFinance/status/1646977448410480643) Lido on Ethereum participating validators use 0x01 (smart contract) withdrawal credentials."
- scorecard-attribute: "Smart contracts are shielded using best-in-class security standards"
categories: "Security"
self-assessment: "Good"
Expand Down Expand Up @@ -90,7 +90,7 @@ rows:
- scorecard-attribute: "DAO goals are easily accessible"
categories: "Governance"
self-assessment: "Okay"
comments: "[The GOOSE framework](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x58bbc5d540e46081043ef29d4d1ee56b7df4dc1b0369aa78e0c15a2403549353) is utilized to set one-year and three-year goals. The [goals for 2025](https://snapshot.org/#/lido-snapshot.eth/proposal/0xeedef9fea3d782f192410768cabaf6974da40ef36e1d22c7f8fff5fd4cfc7a59) were adopted in November 2024, marking a new focus for the upcoming year.\\\nMeanwhile, [](https://snapshot.org/#/lido-snapshot.eth/proposal/0x0fa423280ce2bcc2596901d81322716ad440c7581658030a7d21784c2661d81c)[the current goals](https://snapshot.org/#/lido-snapshot.eth/proposal/0x0fa423280ce2bcc2596901d81322716ad440c7581658030a7d21784c2661d81c), adopted in November 2023, were adjusted in May 2024 ([reGOOSE](https://snapshot.org/#/lido-snapshot.eth/proposal/0x300523518b08f20c585751c0a720ef3ec53698d4e5062154d285b15cb062f96c)), remain active and relevant."
comments: "[The GOOSE framework](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x58bbc5d540e46081043ef29d4d1ee56b7df4dc1b0369aa78e0c15a2403549353) is utilized to set one-year and three-year goals. The [goals for 2025](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xeedef9fea3d782f192410768cabaf6974da40ef36e1d22c7f8fff5fd4cfc7a59) were adopted in November 2024, marking a new focus for the upcoming year.\\\nMeanwhile, [](https://snapshot.org/#/lido-snapshot.eth/proposal/0x0fa423280ce2bcc2596901d81322716ad440c7581658030a7d21784c2661d81c)[the current goals](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x0fa423280ce2bcc2596901d81322716ad440c7581658030a7d21784c2661d81c), adopted in November 2023, were adjusted in May 2024 ([reGOOSE](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x300523518b08f20c585751c0a720ef3ec53698d4e5062154d285b15cb062f96c)), remain active and relevant."
- scorecard-attribute: "Distributed variation of on-premises infra and cloud providers"
categories: "Validator set"
self-assessment: "Okay"
Expand Down

0 comments on commit 881cc62

Please sign in to comment.