The ultra sound team is pleased to make a submission to this RFP! Two new dashboards titled “sanctions censorship” and “inclusion delay” will be live on relay.ultrasound.money in a couple hours. A few notes:
- experimental: This is an experimental beta release. There are known bugs and rough edges—please bear with us. The team will rapidly improve the dashboards next week. We are also open to improvement suggestions from Lido and the wider community.
- open-source: The code is split across two MIT-licensed repos for the backend and the frontend. There is an additional MIT-licensed repo with OFAC Ethereum addresses. Figma designs can be found here—feel free to reuse them! We can also share ad hoc read access to the DB—please contact a team member.
- holistic: The “sanctions censorship” dashboard aims to provide a birds-eye view of Ethereum censorship, diving into the three key stages of the MEV pipeline: building, relaying, proposing. There is a second “inclusion delay” dashboard to shine light into the various reasons Ethereum transactions may be delayed beyond censorship—these include congestion, insufficient base fee, and low tip.
- Lido-focused: We currently focus on Lido operators for proposer censorship. We aim to expand to non-Lido operators and validators in a future release.
-
definitions:
- A builder or relay is said to perform sanctions censorship if none of its blocks contain transactions touching addresses from a sanctions list. We know of two sanctions lists with Ethereum addresses: the US OFAC SDN list and the UK sanctions list. The UK sanctions list only has one Ethereum address with no transactions since the merge, hence our focus on the OFAC SDN list.
- A validator operator is said to perform sanctions censorship if its validators only connect to censoring relays and all its self-built blocks also censor. In this initial release we ignore self-built blocks for Lido operators—a more fine-grained analysis taking into account self-built blocks will come in a future release.
- data sources: We have taken care to build a comprehensive data set that covers the full lifetime of MEV-boost from the merge onwards. Special thanks to zeromev.org for sharing their mempool timestamps as observed from nodes in three separate geographies: America, Asia, Europe. We will be enriching this dataset using Blocknative mempool timestamps, once publicly available. Relay block inclusion data is gathered directly at the source by querying relays. A mapping from builder pubkeys to builder names was manually collated as part of the ultra sound relay operations.
- Figma screenshots: Below are screenshots of the Figma designs. These are mockups with fake data. Please see relay.ultrasound.money for a live version with real data.
Dashboard 1: The above “sanctions censorship” dashboard focuses on OFAC censorship at three different stages of the MEV pipeline: builders, relays, proposers.
Dashboard 2: The above “inclusion delay” dashboard looks at all reasons for transaction delays, beyond censorship.