KVORUM
lidoSource: Snapshot · #0xa478fa5518769096eda2b7403a1d4104ca47de3102e8a9abab8640ef1b50650c

Organize the Lido Alliance Program as a Lido-DAO-Adjacent BORG

succeededSep 5, 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

1,361 words

Summary

Following the approval of the Lido Alliance Proposal in May, Lido DAO contributors have worked with MetaLeX to propose the creation of a LIDO Alliance workgroup, including through the incorporation of a Lido-DAO-adjacent cybernetic organization (BORG) to “legally wrap” the “Alliance workgroup” and the related assets and activities.

The Lido Alliance BORG Foundation consists of a memberless, beneficiary-less Cayman foundation whose purposes are restricted to furthering the Alliance Program, including submitting or facilitating the proposal of worthwhile Lido DAO Allies to Lido DAO and owning and holding assets contributed by such Lido DAO Allies in onchain multisigs.

The Bylaws and other legal docs of the Lido Alliance BORG Foundation provide for legal checks-and-balances between the entity and Lido DAO (explained below).

To complement the legal check-and-balance mechanisms expressed in the Lido Alliance BORG’s legal documents, the multisigs for holding the Lido Alliance BORG’s operational budget will use Easy Track — which gives Lido DAO an onchain veto over spending of these assets. The assets contributed by Lido Allies will be subject to legal checks-and-balances with the DAO and held in a transparent 4/7 multisigs staffed by the BORG Personnel. The BORG personnel hope to eventually transition these multisigs to MetaLeX’s forthcoming technology stack to provide a more full-featured set of onchain checks-and-balances mirroring the prescribed legal arrangements.

This proposal seeks to inform Lido DAO and the broader Lido community of the details of the Lido Alliance BORG and to obtain a signal of the Lido DAO’s support for the structure through an approval of the proposal. If the proposal is approved, the Lido Alliance BORG will be incorporated as described herein. More details regarding BORGs and legal aspects around them can be found in Motivation and Implementation sections of the original proposal at the research forum.

Detailed Proposal

The Lido Alliance BORG is requesting an initial budget of $125,000 for 2024, as part of the st2024 v2 EGG request approved in July and is expected to require a yearly budget of $250,000 from 2025 to operate, which will be requested through subsequent EGG requests. The budget includes director fees, local law firm fees, contributor compensation and any other operational expenses, following the EGG budget requests framework. For every new EGG request, a retro review of the last EGG spend for the Alliance BORG will also be included.

The Board of Directors of the BORG is responsible for running all aspects of the Lido Alliance program and is in charge of the BORG overall. The Directors must sit on all multisigs of the BORG. The initial Directors of the BORG would initially be adcv and Hillstone of steakhouse. Any future Directors would be approved by Lido DAO and the Board. An individual Director can be removed either by the Board itself or by Lido DAO. An individual Director may also unilaterally resign.

The Guardians of the BORG are additional members of the BORG’s multisigs appointed by the Board. They generally should follow the Board’s instructions but may refuse to sign a multisig transaction based on security or compliance considerations. The initial Guardians of the BORG would be shik_happens, mac3w, jenya_k, olga_k, Alexander_Lukin

All Lido Allies must be approved by the Board and Lido DAO, and the BORG would hold all tokens contributed by Lido Allies in the Alliance Multisigs, which will (at minimum) be 4/7 multisigs consisting of the Directors and the Guardians. Lido DAO’s co-approval is required for all usages of the Lido-Ally-contributed tokens as a security measure–this requirement is initially imposed by virtue of the BORG’s Bylaws, and Lido contributors and MetaLeX hope to create additional onchain enforcement of these rules as well, though the technical ability to do so may vary from chain to chain.

Lido Alliance Allies/Partners Multisig address - 0x92ABC000698374B44206148596AcD8a934687E66 with following signers:

Operational funds would be held separately at the discretion of the Board and are currently expected to be held in 3/5 multisig (topped up using Easy Track on a quarterly schedule). Mentioned Easy Track set is requested to be added with a following configuration for the operational multisig:

Lido Alliance Operational Multisig address - 0x606f77BF3dd6Ed9790D9771C7003f269a385D942 with following signers:

The permitted purposes of the BORG are to further the Lido Alliance Program as it was approved by Lido DAO.

The BORG Personnel (including the Directors and Guardians) do not owe any direct duties to Lido DAO or Lido community members, but owe duties to the BORG entity, and the BORG entity’s purposes are restricted to fulfilling the Lido Alliance Program, which benefits the Lido DAO and broader Lido community.

Alliance Multisig Members have obligations to identify material conflicts of interest and, in certain circumstances, disclose them to the Lido community.

Lido DAO approval would be required for any liquidation of the entity or any amendment of the entity’s documents that adversely affect the Lido community or any sub-constituency thereof.

The BORG has a ‘supervisor’, which is a statutory role in the Caymans intended to monitor a foundation company’s compliance with the entity’s own rules. The initial supervisor, intended to be temporary, is MetaLeX Pro LLC, the same law firm that led the creation of the BORG in consultation with various Lido contributors. This role is currently un-compensated and MetaLeX has committed to perform the role without additional compensation for up to three months. The final supervisor is expected to be a “Lido OpsBORG” or similar entity, which is currently in ideation phase and will be separately proposed to Lido DAO once various details are finalized.

If an “Adverse Event” occurs, Lido DAO may directly appoint an “Emergency Supervisor” for the BORG. “Adverse Event” is defined to include egregious violations of law or the BORG’s own rules by the BORG or BORG Personnel in connection with the BORG’s activities, certain crimes independently committed by BORG Personnel (whether or not related to the BORG’s activities), and sustained deadlocks within the BORG’s governance/decision-making. The Emergency Supervisor would have broad powers under the BORG’s Bylaws and Caymans law, including the power to investigate the Adverse Event, bring lawsuits against BORG personnel in the name of the BORG and to remove and appoint Directors. The Emergency Supervisor role is intended to be temporary and the Emergency Supervisor must resign once the Adverse Event is handled or, in any event, the Emergency Supervisor’s tenure is automatically terminated after 12 months if not renewed by Lido DAO. Lido DAO also has the power to directly set the compensation of Emergency Supervisors.

The BORG Personnel are indemnified by the BORG entity, within certain customary limits. This indemnification would be paid solely out of operating funds and not any of the Lido-Ally-contributed assets, unless Lido DAO approves to use additional funds of the BORG to indemnify the BORG personnel who acted on behalf of the BORG.

The BORG Personnel would not have personal liability to the BORG for their BORG-related activities except to the extent they engage in gross negligence, willful misconduct, or fraud.

The BORG Personnel must satisfy various eligibility criteria including not being subject to sanctions, not having previous egregious criminal convictions, and being reasonably sophisticated regarding blockchain technologies.

Voting

Note: The Lido Alliance program has already been approved by the Lido DAO.

This proposal requests the following:

  • Recognition of the DAO adjacent BORG structure of the Lido Alliance program with its many check and balance mechanisms including, but not limited to, setting up on-chain tooling of the operational multisig (configuration above) to enable DAO vetoes
  • Approval of the initial budget to operate the Lido Alliance BORG

By voting Approve, you indicate support for funding and operating the Lido Alliance BORG as described herein.

By voting Reject, you indicate you do not support funding and operating the Lido Alliance BORG as described herein.

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

Voters91
VP participating0
Outcome (current)Approve the Lido Alliance BORG
Current support99.8%

06Voters

91 total
Filter:
VoterChoice% of totalRationale
4A0x4af8…6a0bApprove the Lido Alliance BORG025.86%—2y ago
810x8172…922eApprove the Lido Alliance BORG012.50%—2y ago
7E0x7ee0…bb6cApprove the Lido Alliance BORG09.94%—2y ago
6D0x6d8d…0cccApprove the Lido Alliance BORG07.82%—2y ago
510x510a…8d0eApprove the Lido Alliance BORG07.77%—2y ago
EE0xee44…fad1Approve the Lido Alliance BORG07.13%—2y ago
LIlido.banteg.eth0x55bc…f0faApprove the Lido Alliance BORG07.13%—2y ago
C00xc006…8123Approve the Lido Alliance BORG05.94%—2y ago
110x1109…43daApprove the Lido Alliance BORG04.05%—2y ago
6A0x6a39…4bd2Approve the Lido Alliance BORG02.83%—2y ago
B90xb933…8dd1Approve the Lido Alliance BORG01.90%—2y ago
7A0x7a59…8e22Approve the Lido Alliance BORG01.83%—2y ago
A20xa2ff…7be9Approve the Lido Alliance BORG01.25%—2y ago
330x33c4…8c4bApprove the Lido Alliance BORG00.84%—2y ago
E80xe80e…28e8Approve the Lido Alliance BORG00.63%—2y ago
2C0x2cc1…4df1Approve the Lido Alliance BORG00.56%—2y ago
870x8787…ea52Approve the Lido Alliance BORG00.46%—2y ago
290x29b5…2c2fApprove the Lido Alliance BORG00.41%—2y ago
100x10a2…36f3Approve the Lido Alliance BORG00.28%—2y ago
E30xe3a3…bbb8Approve the Lido Alliance BORG00.26%—2y ago
620x624d…2cd0Reject the Lido Alliance BORG00.21%—2y ago
060x06a9…bba0Approve the Lido Alliance BORG00.16%—2y ago
C30xc324…4798Approve the Lido Alliance BORG00.11%—2y ago
180x18ac…3a1aApprove the Lido Alliance BORG00.04%—2y ago
490x49f1…6cdbApprove the Lido Alliance BORG00.04%—2y ago
530x5357…e248Approve the Lido Alliance BORG00.02%—2y ago
6B0x6bd3…fd13Approve the Lido Alliance BORG00.01%—2y ago
9E0x9e0b…da3aApprove the Lido Alliance BORG00.01%—2y ago
050x0579…4048Approve the Lido Alliance BORG00.01%—2y ago
420x42e6…3fb0Approve the Lido Alliance BORG00.00%—2y ago
610x617e…5265Approve the Lido Alliance BORG00.00%—2y ago
7A0x7af3…8df3Approve the Lido Alliance BORG00.00%—2y ago
3D0x3d5a…b97fApprove the Lido Alliance BORG00.00%—2y ago
6A0x6afa…5deeApprove the Lido Alliance BORG00.00%—2y ago
3D0x3ddc…05b0Approve the Lido Alliance BORG00.00%—2y ago
ED0xed95…68a6Approve the Lido Alliance BORG00.00%—2y ago
CE0xce3b…2e55Approve the Lido Alliance BORG00.00%—2y ago
520x5243…3440Reject the Lido Alliance BORG00.00%—2y ago
B30xb36f…1b47Approve the Lido Alliance BORG00.00%—2y ago
EC0xecc2…6ac9Approve the Lido Alliance BORG00.00%—2y ago
C10xc1c2…24f8Approve the Lido Alliance BORG00.00%—2y ago
E60xe6b5…f1fdApprove the Lido Alliance BORG00.00%—2y ago
D30xd31a…1072Approve the Lido Alliance BORG00.00%—2y ago
8B0x8bc8…7276Approve the Lido Alliance BORG00.00%—2y ago
500x500f…7d0bApprove the Lido Alliance BORG00.00%—2y ago
C40xc48b…75b6Approve the Lido Alliance BORG00.00%—2y ago
960x968a…d19cApprove the Lido Alliance BORG00.00%—2y ago
270x2748…ac26Approve the Lido Alliance BORG00.00%—2y ago
D50xd5d7…3c4dApprove the Lido Alliance BORG00.00%—2y ago
760x76c6…efe6Approve the Lido Alliance BORG00.00%—2y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.