# RMC Proposal: Add Relays Supporting Proposer Commitments to the Holesky Allow List

**URL:** <https://research.lido.fi/t/rmc-proposal-add-relays-supporting-proposer-commitments-to-the-holesky-allow-list/8992>\
**Category:** Node Operators\
**Created:** [December 2, 2024, 8:04am UTC](https://research.lido.fi/t/rmc-proposal-add-relays-supporting-proposer-commitments-to-the-holesky-allow-list/8992 "2024-12-02T08:04:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sabrychiaa](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@sabrychiaa](https://research.lido.fi/u/sabrychiaa)\
**Post date:** [December 2, 2024, 8:04am UTC](https://research.lido.fi/t/rmc-proposal-add-relays-supporting-proposer-commitments-to-the-holesky-allow-list/8992/1 "2024-12-02T08:04:24Z")

</div>

This proposal seeks to expand the Holesky “may use” list by incorporating additional relays necessary for testing proposer commitments. Node operators can choose to test by running either the Bolt sidecar or the Commit-Boost with the Bolt module. For more details, please visit:[link](https://research.lido.fi/t/perch-request-for-node-operators-to-run-and-test-bolt/8698).

To enable preconfirmations while remaining PBS-compatible, additional responsibilities have been incorporated into the relay specification, including:

- Getter function for delegations and constraints in a slot.
- Subscription to new constraints using Server Side Events (SSE).
- Implement an updated block submission endpoint with support for inclusion proofs.

A list of relays which support constraints API are listed below, three marked with [NEW] are currently not in the vetted relay list.

- [NEW] Chainbound [https://0xa55c1285d84ba83a5ad26420cd5ad3091e49c55a813eee651cd467db38a8c8e63192f47955e9376f6b42f6d190571cb5@relay-holesky.bolt.chainbound.io](https://0xa55c1285d84ba83a5ad26420cd5ad3091e49c55a813eee651cd467db38a8c8e63192f47955e9376f6b42f6d190571cb5@relay-holesky.bolt.chainbound.io)
- [NEW] Titan [https://0xaa58208899c6105603b74396734a6263cc7d947f444f396a90f7b7d3e65d102aec7e5e5291b27e08d02c50a050825c2f@holesky-preconf.titanrelay.xyz](https://0xaa58208899c6105603b74396734a6263cc7d947f444f396a90f7b7d3e65d102aec7e5e5291b27e08d02c50a050825c2f@holesky-preconf.titanrelay.xyz)
- [NEW] Aestus [https://0x8d6ff9fdf3b8c05293f6c240f57034c6c5244d7ecb2b9a6e597de575b373610d6345f5060c150012d1cc42d38b8383ac@preconfs-holesky.aestus.live](https://0x8d6ff9fdf3b8c05293f6c240f57034c6c5244d7ecb2b9a6e597de575b373610d6345f5060c150012d1cc42d38b8383ac@preconfs-holesky.aestus.live)
- Bloxroute [https://0x821f2a65afb70e7f2e820a925a9b4c80a159620582c1766b1b09729fec178b11ea22abb3a51f07b288be815a1a2ff516@bloxroute.holesky.blxrbdn.com](https://0x821f2a65afb70e7f2e820a925a9b4c80a159620582c1766b1b09729fec178b11ea22abb3a51f07b288be815a1a2ff516@bloxroute.holesky.blxrbdn.com)

Source: [bolt/testnets/holesky at unstable · chainbound/bolt · GitHub](https://github.com/chainbound/bolt/tree/unstable/testnets/holesky#supported-relays)

---

<div class="post-metadata">

**Author:** ![Chainbound](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/chainbound/32/4462_2.png) [@Chainbound](https://research.lido.fi/u/Chainbound)\
**Post date:** [December 4, 2024, 7:11pm UTC](https://research.lido.fi/t/rmc-proposal-add-relays-supporting-proposer-commitments-to-the-holesky-allow-list/8992/2 "2024-12-04T19:11:48Z")

</div>

Attaching our post on our bolt Holesky v1 deployment, signaling our need and support for this!

> [@\[bolt Holesky v1\] Node Operator Working Group and Relay Support](https://research.lido.fi/t/bolt-holesky-v1-node-operator-working-group-and-relay-support/9000):
>
> bolt • Holesky v1: Node Operator Working Group and Relay Support This post aims to update the Lido community on our current Holesky Initiative, invite Node Operators to join Cohort 1 of our Working Group, and seek support for the recent proposal to add bolt-compatible relays to Lido’s vetted relay list. NO Primer To catch Lido community members up to speed, here is a quick primer and a couple helpful resources on bolt. Bolt enables sub-second inclusion preconfirmatio…

---

<div class="post-metadata">

**Author:** ![infra\_john](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/infra_john/32/5379_2.png) [@infra\_john](https://research.lido.fi/u/infra_john)\
**Post date:** [December 6, 2024, 6:56am UTC](https://research.lido.fi/t/rmc-proposal-add-relays-supporting-proposer-commitments-to-the-holesky-allow-list/8992/4 "2024-12-06T06:56:49Z")

</div>

Thanks for the proposal! As a node operator, we would like to signal interest in running Bolt with our Lido nodes.

We’re Nodeinfra, an operator based in Korea, who has been running Lido Obol/SSV Mainnet/Holesky SDVT nodes including a SuperCluster node, as well as Lido CSM nodes.

We are also part of Cohort 1 of Bolt and are very active in the Symbiotic/Mellow ecosystem.

We hope the proposal is accepted, enabling us to operate and test Bolt-enabled Lido nodes.

---

<div class="post-metadata">

**Author:** ![Sven](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sven](https://research.lido.fi/u/Sven)\
**Post date:** [December 13, 2024, 9:25am UTC](https://research.lido.fi/t/rmc-proposal-add-relays-supporting-proposer-commitments-to-the-holesky-allow-list/8992/5 "2024-12-13T09:25:21Z")

</div>

**Update on Holesky Relay Additions**

This post is to confirm that the proposal to expand the Holesky “may use” list by incorporating additional relays supporting constraints has been reviewed, with no objections raised by the Relay Maintenance Committee. Accordingly, the following relays will be added to the “may use” list on Holesky.

These additions are aimed at enabling and testing preconfirmation flows within the **Protocol Evaluation and Request Coordination Hub (PERCH)** while maintaining PBS compatibility (more on [PERCH here](https://research.lido.fi/t/proposal-perch-protocol-evaluation-and-request-coordination-hub/8306), [and here](https://research.lido.fi/t/perch-request-for-node-operators-to-run-and-test-bolt/8698)). Node operators can now choose to run either the Bolt sidecar or the Commit-Boost with the Bolt module for their preconfirmation testing.

**Relays to be Added:**

- **[NEW] Chainbound**:  
`https://0xa55c1285d84ba83a5ad26420cd5ad3091e49c55a813eee651cd467db38a8c8e63192f47955e9376f6b42f6d190571cb5@relay-holesky.bolt.chainbound.io`
- **[NEW] Titan**:  
`https://0xaa58208899c6105603b74396734a6263cc7d947f444f396a90f7b7d3e65d102aec7e5e5291b27e08d02c50a050825c2f@holesky-preconf.titanrelay.xyz`
- **[NEW] Aestus**:  
`https://0x8d6ff9fdf3b8c05293f6c240f57034c6c5244d7ecb2b9a6e597de575b373610d6345f5060c150012d1cc42d38b8383ac@preconfs-holesky.aestus.live`

For reference, the [MEV Relay list is viewable here](https://enchanted-direction-844.notion.site/6d369eb33f664487800b0dedfe32171e?v=d255247c822c409f99c498aeb6a4e51d).
