KVORUM
lidoSource: Snapshot · #0x9d39cc7ed918e89cff5a597ff1e0bce0974f5721283dcac6ccc8274bde703d1f

Proposal to return back 11 ETH that were sent by BloXroute's builder to Lido Execution Layer Rewards Vault (restart)

succeededOct 24, 2022, 05:00 PM UTCsignaling · non-bindingbyDB0xdbbc…1cb6View on Snapshot ↗

01Summary

AISummary by Kvorum

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

02Description

258 words

Overview

Over the course of the day on 09/27 the BloXroute ethical relay was receiving and returning bad blocks to validators from one of our block builders running an experimental build strategy that resulted in missed slots.

This builder was improperly committing transactions and caused improperly formatted blocks. Because the relay was not simulating blocks from known builders these blocks were getting sent to validators causing them to miss slots due to proposing blocks with improper receipts or log blooms. A total of 15 slots were missed due to this issue.

BloXroute’s relay was not simulating blocks from internal builders and was instead relying on these builders to submit valid blocks.

This was resolved:

  • The experimental builder was taken offline and ensured that it was no longer submitting blocks to any of our relays.
  • All of the validators who missed slot’s were paid for the bids they received from the bloXroute relay.
  • On 09/30 all of the relays now simulate all block submissions regardless of source. While transferring funds to bloXroute’s builder to pay for the missed slots the builder considered the transfer of 11 ETH as an MEV tip for the validator and paid that 11 ETH to the Lido Execution Layer Rewards Vault on slots 4791729 and 4792026.

Proposal This proposal is to return back 11 ETH that were sent to the Lido Execution Layer Rewards Vault.

If the proposal is supported, then an on-chain vote will be launched to send 11 ETH from the Lido DAO Treasury to the address 0xea48ba2edefae9e4ddd43ea565aa8b9aa22baf08.

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.