# Proposal: Inclusion of SecureRPC.com MEV Relay as a Mandatory Relay in Lido's MEV Relay List **URL:** \ **Category:** Proposals\ **Created:** [August 13, 2024, 9:37pm UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073 "2024-08-13T21:37:46Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![sambacha](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/sambacha/32/1126_2.png) [@sambacha](https://research.lido.fi/u/sambacha)\ **Post date:** [August 13, 2024, 9:37pm UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/1 "2024-08-13T21:37:46Z")
# Proposal: Inclusion of [SecureRPC.com](http://SecureRPC.com) MEV Relay as a Mandatory Relay in Lido’s MEV Relay List ## Overview This proposal suggests the inclusion of the [SecureRPC.com](http://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](http://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](http://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](http://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](http://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](http://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](http://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](http://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](http://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](http://SecureRPC.com) relay in accordance with LIP-17, thereby reinforcing Lido’s position as a leader in Ethereum staking and decentralized finance. ---
**Author:** ![MaxEF](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/maxef/32/3121_2.png) [@MaxEF](https://research.lido.fi/u/MaxEF)\ **Post date:** [August 19, 2024, 1:32pm UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/2 "2024-08-19T13:32:18Z")
@Izzy @KimonSh - FYI above 🙂 ---
**Author:** ![Izzy](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/izzy/32/320_2.png) [@Izzy](https://research.lido.fi/u/Izzy)\ **Post date:** [August 20, 2024, 9:40am UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/3 "2024-08-20T09:40:52Z")
Thanks, will ask the RMC to take this into consideration! ---
**Author:** ![Izzy](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/izzy/32/320_2.png) [@Izzy](https://research.lido.fi/u/Izzy)\ **Post date:** [September 23, 2024, 4:54am UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/4 "2024-09-23T04:54:48Z")
> [@sambacha](#): > > For mainnet the following parameters are proposed for the [SecureRPC.com](http://SecureRPC.com) MEV Relay: > > - **URI** : `https://0xad2c0074aa2bb6149340187906196f719bbac701a20d0cc88baefd2bbcc9fc970fb060d5eeb5fedf22024db6e69582da@mainnet-auction.securerpc.com` > - **Operator** : Manifold Finance > - **Is Mandatory** : `true` > - **Description** : non-filtering @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/](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? ---
**Author:** ![sambacha](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/sambacha/32/1126_2.png) [@sambacha](https://research.lido.fi/u/sambacha)\ **Post date:** [October 21, 2024, 11:14pm UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/5 "2024-10-21T23:14:04Z")
You are correct, `mainnet-relay` is the correct URI my apologies. I have updated the original post. ---
**Author:** ![sambacha](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/sambacha/32/1126_2.png) [@sambacha](https://research.lido.fi/u/sambacha)\ **Post date:** [October 21, 2024, 11:15pm UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/6 "2024-10-21T23:15:17Z")
**URI** ```auto https://0x98650451ba02064f7b000f5768cf0cf4d4e492317d82871bdc87ef841a0743f69f0f1eea11168503240ac35d101c9135@mainnet-relay.securerpc.com/ ``` - **Operator** : Manifold Finance - **Is Mandatory** : `true` - **Description** : non-filtering ---
**Author:** ![Izzy](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/izzy/32/320_2.png) [@Izzy](https://research.lido.fi/u/Izzy)\ **Post date:** [October 28, 2024, 5:25pm UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/7 "2024-10-28T17:25:40Z")
Thanks, will take it up with RMC! ---
**Author:** ![sambacha](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/sambacha/32/1126_2.png) [@sambacha](https://research.lido.fi/u/sambacha)\ **Post date:** [December 9, 2024, 4:26pm UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/8 "2024-12-09T16:26:08Z")
Any update on your end? Appreciate it! ---
**Author:** ![Sven](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sven](https://research.lido.fi/u/Sven)\ **Post date:** [December 10, 2024, 9:11am UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/9 "2024-12-10T09:11:23Z")
Hey Sam, was wondering if you ever finalized the transition to the new mev-freelay codebase? [Manifold Finance transition to new relay codebase](https://research.lido.fi/t/manifold-finance-transition-to-new-relay-codebase/4578) if not, what is the relay running on now? ---
**Author:** ![sambacha](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/sambacha/32/1126_2.png) [@sambacha](https://research.lido.fi/u/sambacha)\ **Post date:** [December 12, 2024, 9:19am UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/10 "2024-12-12T09:19:58Z")
that relay is under a separate endpoint, the securerpc relay does not have that logic detailed. ---
**Author:** ![Sven](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sven](https://research.lido.fi/u/Sven)\ **Post date:** [June 16, 2025, 4:07pm UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/11 "2025-06-16T16:07:22Z")
On behalf of the RMC: The RMC has reviewed and discussed the proposal submitted by **Manifold** to update its relay status. After internal review, no objections were raised by committee members. The RMC approves the request from Manifold to move their relay from the current **allow-list** to the **must-use-some list**. This motion has [just been submitted via Easy Track](https://easytrack.lido.fi/motions/847) and is currently pending during the objection period. ---
**Author:** ![Sven](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sven](https://research.lido.fi/u/Sven)\ **Post date:** [June 19, 2025, 5:32pm UTC](https://research.lido.fi/t/proposal-inclusion-of-securerpc-com-mev-relay-as-a-mandatory-relay-in-lidos-mev-relay-list/8073/12 "2025-06-19T17:32:42Z")
The proposal was enacted today, [following the Easytrack process for the first time, after receiving no objections](https://easytrack.lido.fi/motions/847). As of June 1st, RMC [motions to add or remove relays will be processed via Easytrack](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xf1074ec134595ba8ba6f802c5e505fda32e6ab93e9763d1e43001f439241b7c9). The updated list of relays is shown below and can always be checked [here](https://etherscan.io/address/0xf95f069f9ad107938f6ba802a3da87892298610e#readContract). ```auto [https://0xa7ab7a996c8584251c8f925da3170bdfd6ebc75d50f5ddc4050a6fdc77f2a3b5fce2cc750d0865e05d7228af97d69561@agnostic-relay.net,Agnostic,true,Agnostic Relay] [https://0xb0b07cd0abef743db4260b0ed50619cf6ad4d82064cb4fbec9d3ec530f7c5e6793d9f286c4e082c0244ffb9f2658fe88@bloxroute.regulated.blxrbdn.com,bloXroute,true,bloXroute Regulated Relay] [https://0xa15b52576bcbf1072f4a011c0f99f9fb6c66f3e1ff321f11f461d15e31b1cb359caa092c71bbded0bae5b5ea401aab7e@aestus.live,Aestus,true,Aestus Relay] [https://0x8b5d2e73e2a3a55c6c87b8b6eb92e0149a125c852751db1422fa951e42a09b82c142c3ea98d0d9930b056a3bc9896b8f@bloxroute.max-profit.blxrbdn.com,bloXroute,true,bloXroute Max-Profit Relay] [https://0xac6e77dfe25ecd6110b8e780608cce0dab71fdd5ebea22a16c0205200f2f8e2e3ad3b71d3499c54ad14d6c21b41a37ae@boost-relay.flashbots.net,Flashbots,true,Flashbots Relay] [https://0xa1559ace749633b997cb3fdacffb890aeebdb0f5a3b6aaa7eeeaf1a38af0a8fe88b9e4b1f61f236d2e64d95733327a62@relay.ultrasound.money,Ultra Sound,true,Ultra Sound Relay] [https://0x8c4ed5e24fe5c6ae21018437bde147693f68cda427cd1122cf20819c30eda7ed74f72dece09bb313f2a1855595ab677d@regional.titanrelay.xyz,Gattaca,false,Titan Relay Regional (filtering)] [https://0x8c4ed5e24fe5c6ae21018437bde147693f68cda427cd1122cf20819c30eda7ed74f72dece09bb313f2a1855595ab677d@global.titanrelay.xyz,Gattaca,false,Titan Relay Global (non-filtering)] [https://0x98650451ba02064f7b000f5768cf0cf4d4e492317d82871bdc87ef841a0743f69f0f1eea11168503240ac35d101c9135@mainnet-relay.securerpc.com/,Manifold Finance,true,Manifold SecureRPC Relay] ```