KVORUM
lidoSource: Snapshot · #0x8ad1089720d2fd68cc49b74e138915af7fec35a06b04c2af2fcf4828d5bbd220

Simple On-chain Delegation

succeededMar 21, 2024, 04:00 PM UTCsignaling · non-bindingbyDB0xdbbc…1cb6View on Snapshot ↗

01Summary

AISummary by Kvorum

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

02Description

519 words

This is a signal proposal intended to approve the overall design for Simple On-chain Delegation. If the DAO approves this proposal, the voting dedicated to on-chain changes will take place in April after all audits and security checks pass.

TL;DR

The Simple On-chain Delegation allows LDO token holders to delegate their voting power to other addresses and delegates to participate in on-chain voting on behalf of their delegated voters. Alongside that, it’s proposed to add TRP (Token Rewards Plan) participants the ability to delegate their LDO rewards.

This proposal is intended to address the security and operational hurdles arising from the lack of delegation for on-chain voting. This quick and cost-effective solution involves some simplification of the user experience; however, it is intended to address urgent needs while a more comprehensive solution is worked on.

Motivation

In the current conditions, reaching a quorum in on-chain voting has become highly challenging, and several consecutive votes failed to reach a quorum. The absence of an on-chain delegation is a blocker for stable and sufficient participation in on-chain voting and protocol development.

Projects objective

Three vectors can be directly or indirectly solved through on-chain delegation:

  1. Activate the voting power of the voters who are already involved in the governance process and have delegated their voting power on off-chain snapshot.org but have never participated in on-chain voting.
  2. Ease the on-chain voting process for those who are already involved in the governance process and participate in on-chain voting but irregularly. There are various reasons for this: limited and complex access to cold wallets given the short 48-hour voting phase or multi-sig as a token holder.
  3. Attract those willing to participate in the governance process when Lido DAO determines an open delegation mechanism with a list of delegates.

The project aims to achieve a 20-30M increase in quarterly active voting power participation on-chain within 3 months of its launch (for Q4 2023, the quarterly active VP on on-chain votes accounted for ~90M LDO, and on off-chain snapshot.org ~120M LDO).

Design Requirements and trade-offs

A proper full-fledged delegation mechanism involves maintaining an accounting to track actual delegated voting power at any moment accurately. Implementing this is a complex and time-consuming project.

The current solution is a simplified version that addresses three basic requirements:

  1. There is a mapping of token holders’ and delegates’ addresses; the token holder can set a delegate and cancel the delegation, and the delegate can obtain the addresses of all those who have delegated to them.
  2. A delegate can vote on behalf of a token holder or a list of token holders.
  3. A token holder has an ultimate authority, they can override the delegate’s decision on a vote.

You can dive into the design description of the solution in the specification: LIP-21. Simple On-chain Delegation.

Next steps

Now the solution is undergoing several security audits.

If this vote gets approval from the DAO, the on-chain voting (hopefully the last one without the delegation feature) is planned for April.

The on-chain voting will be held after all audits and security checks successfully pass.

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

Voters268
VP participating0
Outcome (current)Support
Current support—

06Voters

268 total
Filter:
VoterChoice% of totalRationale
450x4580…5f81Support025.49%—3y ago
4A0x4af8…6a0bSupport015.87%—3y ago
D10xd1c7…0aaeSupport011.61%—3y ago
7E0x7ee0…bb6cSupport07.18%—3y ago
D20xd2dd…a7b7Support07.16%—3y ago
AE0xae09…256bSupport05.75%—3y ago
6D0x6d8d…0cccSupport05.52%—3y ago
510x510a…8d0eSupport05.47%—3y ago
LIlido.banteg.eth0x55bc…f0faSupport05.16%—3y ago
110x1109…43daSupport02.92%—3y ago
1F0x1f38…b7b3Support02.23%—3y ago
B90xb933…8dd1Support01.37%—3y ago
7A0x7a59…8e22Support00.97%—3y ago
A20xa2ff…7be9Support00.91%—3y ago
E80xe80e…28e8Support00.46%—3y ago
A60xa620…2eafSupport00.34%—3y ago
110x116a…41b9Support00.30%—3y ago
290x29b5…2c2fSupport00.29%—3y ago
B30xb3ba…ebc5Support00.20%—3y ago
E30xe3a3…bbb8Support00.19%—3y ago
4C0x4c26…fab1Support00.14%—3y ago
AA0xaa44…507eSupport00.14%—3y ago
3D0x3d63…4afcSupport00.09%—3y ago
780x78d1…753aSupport00.07%—3y ago
BA0xba03…a59fSupport00.06%—3y ago
490x49f1…6cdbSupport00.03%—3y ago
E40xe445…27afSupport00.02%—3y ago
5D0x5dd7…97edSupport00.02%—3y ago
0A0x0a54…f4c9Support00.01%—3y ago
2B0x2b1d…8a42Support00.01%—3y ago
9E0x9e0b…da3aSupport00.01%—3y ago
880x8845…53f5Support00.01%—3y ago
610x617e…5265Support00.00%—3y ago
7A0x7af3…8df3Support00.00%—3y ago
DB0xdbbc…1cb6Support00.00%—3y ago
3D0x3d5a…b97fSupport00.00%—3y ago
520x5259…f0cfSupport00.00%—3y ago
0F0x0fad…1d32Support00.00%—3y ago
520x5243…3440Don’t support00.00%—3y ago
A90xa908…c4f4Support00.00%—3y ago
8B0x8b8f…63d5Support00.00%—3y ago
5E0x5ecc…4036Support00.00%—3y ago
6C0x6cc1…9415Support00.00%—3y ago
6A0x6a2d…03e0Support00.00%—3y ago
E60xe6b5…f1fdSupport00.00%—3y ago
530x53c4…3584Support00.00%—3y ago
950x95e9…444eSupport00.00%—3y ago
EB0xeb0e…a99dSupport00.00%—3y ago
D30xd31a…1072Support00.00%—3y ago
3F0x3f2d…ce6bSupport00.00%—3y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.