Proposal: Inclusion of SecureRPC.com MEV Relay as a Mandatory Relay in Lido's MEV Relay List

Proposals
1

Proposal: Inclusion of SecureRPC.com MEV Relay as a Mandatory Relay in Lido’s MEV Relay List

Overview

This proposal suggests the inclusion of the SecureRPC.com MEV Relay operated by Manifold Finance as a mandatory relay in Lido’s MEV Relay list, according to the guidelines set forth in LIP-17. Currently the SecureRPC relay is considered an optional relay. This is because of a security incident it was ‘downgraded’ even after repayment was made back to the Lido DAO. Currently, no other relay offers any sort of indemnity against losses, however SecureRPC has a new ‘Captive Insurance’ pool to provide renumeration for service outages. By integrating SecureRPC.com into Lido’s infrastructure, Lido DAO can enhance the security and efficiency of the network’s MEV processes, as the relay is both non-filtering and non-optimistic, unlike any of the current relays that are in mandatory usage. The relay’s non-filtering nature aligns with Lido’s commitment to maintaining a decentralized and permissionless ecosystem.

Context and Rationale

LIP-17 establishes the allowed list of MEV Boost relays that are considered safe and reliable for inclusion in Lido’s infrastructure. This proposal advocates for the SecureRPC.com relay to be added to this list and marked as “mandatory.” The following reasons justify this addition:

  1. Security and Integrity: The SecureRPC.com relay is operated by Manifold Finance, a trusted entity within the Ethereum community. Their relay ensures the integrity of MEV transactions by offering a secure, non-filtering relay, which aligns with Lido’s principles of transparency and security.

  2. Operational Efficiency: The SecureRPC.com relay has demonstrated robust performance on both mainnet and holesky testnet, ensuring that it meets the rigorous standards required for integration into Lido’s MEV infrastructure.

  3. Alignment with LIP-17: Adding SecureRPC.com as a mandatory relay is consistent with the principles outlined in LIP-17, which emphasizes the importance of selecting relays that contribute to a decentralized and efficient MEV ecosystem.

MEV Relay Parameters

For mainnet the following parameters are proposed for the SecureRPC.com MEV Relay:

  • URI: https://0xad2c0074aa2bb6149340187906196f719bbac701a20d0cc88baefd2bbcc9fc970fb060d5eeb5fedf22024db6e69582da@mainnet-auction.securerpc.com
  • Operator: Manifold Finance
  • Is Mandatory: true
  • Description: non-filtering

Implementation

The implementation of this proposal requires the following steps:

  1. Authorization: An authorized address from the Lido DAO will execute the addition of the SecureRPC.com relay using the command add_relay(0x2e21ecef).

  2. Monitoring: After the relay is added, continuous monitoring will be conducted to ensure its performance aligns with Lido’s standards.

  3. Reporting: Regular reports on the relay’s performance will be shared with the Lido community to maintain transparency.

Conclusion

Incorporating the SecureRPC.com MEV Relay as a mandatory relay in Lido’s infrastructure is a strategic move that enhances the security, reliability, and decentralization of Lido’s MEV operations. This proposal calls on the Lido DAO to approve the addition of the SecureRPC.com relay in accordance with LIP-17, thereby reinforcing Lido’s position as a leader in Ethereum staking and decentralized finance.

3 Likes
2

@Izzy @KimonSh - FYI above :slight_smile:

3

Thanks, will ask the RMC to take this into consideration!

1 Like
4

@MaxEF Question on this, this URI doesn’t match with the URI of the existing manifold relay on the “may use” list (i.e. https://0x98650451ba02064f7b000f5768cf0cf4d4e492317d82871bdc87ef841a0743f69f0f1eea11168503240ac35d101c9135@mainnet-relay.securerpc.com/). Given that this is a request for the upgrade of the relay from the “may use” list to “may use some” list, can you explain why a different URI is being pointed to?

5

You are correct, mainnet-relay is the correct URI my apologies.

I have updated the original post.

1 Like
6

URI

https://0x98650451ba02064f7b000f5768cf0cf4d4e492317d82871bdc87ef841a0743f69f0f1eea11168503240ac35d101c9135@mainnet-relay.securerpc.com/
  • Operator: Manifold Finance
  • Is Mandatory: true
  • Description: non-filtering
2 Likes
7

Thanks, will take it up with RMC!

3 Likes
8

Any update on your end? Appreciate it!

1 Like
9

Hey Sam, was wondering if you ever finalized the transition to the new mev-freelay codebase? Manifold Finance transition to new relay codebase if not, what is the relay running on now?

1 Like
10

that relay is under a separate endpoint, the securerpc relay does not have that logic detailed.

1 Like