KVORUM
lidoSource: Snapshot · #0x211ebdacbfae9d3492ff9e096b6f7be8a58bd48cd9eb8fc57454575b68bd6fc1

A decision on an outflow of 39.8 ETH from the Lido DAO treasury to aid in the Sushi recovery

succeededMay 11, 2023, 06:00 PM UTCsignaling · non-bindingby7F0x7fea…171bView on Snapshot ↗

01Summary

AISummary by Kvorum

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

02Description

281 words

Proposal

Should the 39.8 ETH that flowed into the Lido DAO Treasury, as a result of an exploited vulnerability in SushiSwap RouteProcessor2, be sent to sifuvision.eth (the affected party) as an expression of goodwill?

Motivation

Untangling the original post and discussion, two, largely orthogonal, decisions at hand may be derived:

  1. A decision on an outflow of 39.8 ETH from the Lido DAO treasury to help Sushi (this is the amount which came into the treasury as a result of the exploit).
  2. A wider policy decision on whether or not the DAO should ever act as an arbiter between stakers, node operators, and third parties – and if so, how, and under what conditions.

The discussion under the original post has revolved almost entirely around the second decision – yet this has not been made clear within the discussion itself.

To minimize the risk of decisions, on both fronts, being made for the wrong reasons, it makes sense to move these two decisions into separate threads where they can be discussed individually.

Key points

Concerns of the type that Hasu and Misha have raised in the original thread are not especially relevant to this initial decision at hand.

In particular:

  • Lido DAO does not a priori need a broader framework to make decisions on what to do about unexpected treasury inflows.
  • Voting in favour of this decision does not turn the Lido DAO into an arbiter or open up a slippery slope that could detract from its neutrality.

Voting options

  • No action
  • Send 39.8 ETH to sifuvision.eth

Actual transfer in case of approval by Lido DAO be done via Aragon on-chain vote.

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.