Removal of SecureRPC (Manifold) from Lido's relay list due to sustained unavailability

Proposals
1

Summary

This proposal suggests removing the SecureRPC (Manifold) relay

mainnet-relay.securerpc.com from the “must-use-some” category due to sustained unavailability.

Background

The relay was previously promoted from optional to “must-use-some” based on its non-filtering design and alignment with decentralization goals.

Issue

  • The relay has been unavailable for ~4 months

  • Node operators consistently observe:

    • non-200 responses

    • failed requests / timeouts

  • No recent communication or recovery timeline from the operator

Rationale

Relays in the “must-use-some” category are expected to be reliably operational.

A persistently unavailable relay:

  • adds unnecessary errors for node operators

  • provides no value in block building

  • undermines the reliability of the curated relay set

Proposal

Remove the following relay:

https://0x98650451ba02064f7b000f5768cf0cf4d4e492317d82871bdc87ef841a0743f69f0f1eea11168503240ac35d101c9135@mainnet-relay.securerpc.com/

7 Likes
2

RockLogic supports this proposal.

3 Likes
3

Gateway.FM supports the proposal

3 Likes
4

P2P.org supports this proposal too

3 Likes
5

Thanks for the proposal. I have shared it with the others in the RMC. I’ve also seen the downtime by Manifold. Reaching out to them so far has not resulted in a response so I’ve suggested to go ahead with the removal. As a reminder - as of last year these changes are made through easytrack motion. I will share the vote once it’s made on-chain.