# \[PERCH\] Request for Node Operators to run and test bolt

**URL:** https://research.lido.fi/t/perch-request-for-node-operators-to-run-and-test-bolt/8698
**Category:** Department of Decentralisation
**Created:** [October 22, 2024, 3:39pm UTC](https://research.lido.fi/t/perch-request-for-node-operators-to-run-and-test-bolt/8698 "2024-10-22T15:39:04Z")
**Posts on this page:** 4
**Page:** 1

<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: [October 22, 2024, 3:39pm UTC](https://research.lido.fi/t/perch-request-for-node-operators-to-run-and-test-bolt/8698/1 "2024-10-22T15:39:05Z")

</div>

# [PERCH] bolt

## **bolt – Enabling Preconfirmations with Proposer Commitments**

* * *

 ![bolt logo (light blue)](https://europe1.discourse-cdn.com/flex013/uploads/lido/original/2X/d/d5dc6564aff9e42260c91e5f5f91fa7b08579ddb.png)

_This post is in response to [[Proposal] PERCH: Protocol Evaluation and Request Coordination Hub](https://research.lido.fi/t/proposal-perch-protocol-evaluation-and-request-coordination-hub/8306)_

### bolt TLDR

- With bolt, users can receive **near-instant confirmation** on non-contentious transactions through **inclusion preconfirmations**. Actions like transfers, approvals, and mints, which previously took an average of 7 seconds, can now be preconfirmed in approximately _250ms_. Users can be confident in these ‘promises of inclusion’, as they are backed by economic collateral and enforced by slashing conditions.

- Starting with inclusion preconfirmations on Ethereum, bolt enables validators to further monetize their blockspace. Bolt leverages **proposer commitments** —a novel primitive that allows proposers (validators) to make credible commitments on the blocks they produce—to achieve this. Bolt is fully **PBS-compatible** , allowing validators to access ancillary revenue streams without giving up MEV rewards.

- Bolt starts with inclusion pre-confirmations but is designed to be **flexible** to unlock a variety of use cases. Promising applications include encrypted transaction inclusion, event-driven promises, settlement guarantees for dApps and rollups—and most notably, based sequencing. In future iterations, bolt plans to expand to other commitment types, such as blockspace claims, to potentially enable execution preconfirmations and blockspace futures.

### PERCH Expectations

1. **Number of Participants:**

2. **Application Form** :

3. **Testing Outline** :

4. **Requirements** :

* * *

 ![bolt banner (light blue)](https://europe1.discourse-cdn.com/flex013/uploads/lido/original/2X/5/5474ee22c323ab2810fde389df28d3b9cdf0cf19.png)

---

<div class="post-metadata">

### Author: ![Lanski](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/lanski/32/4846_2.png) [@Lanski](https://research.lido.fi/u/Lanski)
#### Post date: [October 24, 2024, 8:44am UTC](https://research.lido.fi/t/perch-request-for-node-operators-to-run-and-test-bolt/8698/2 "2024-10-24T08:44:33Z")

</div>

If you create a dappnode package for it I’m sure hundreds of Solo Stakers will join the testnet.  
Should be very easy to do with the [SDK](https://docs.dappnode.io/docs/dev/) if you’ve got a docker image.  
You can hit me up for support 🫡

---

<div class="post-metadata">

### Author: ![ChorusOne](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/chorusone/32/3049_2.png) [@ChorusOne](https://research.lido.fi/u/ChorusOne)
#### Post date: [December 3, 2024, 12:32pm UTC](https://research.lido.fi/t/perch-request-for-node-operators-to-run-and-test-bolt/8698/3 "2024-12-03T12:32:58Z")

</div>

Hi from Chorus One.  
We’ve been testing every testnet instance of Bolt going back to [ZuBerlin in June 2024](https://x.com/drakefjustin/status/1801321889152835758). We also ran Bolt on mainnet during [the November 2024 Devcon pilot](https://x.com/drakefjustin/status/1857083454011101600).

Due to our extensive experience running Bolt without incident, and Bolt’s technical maturity, we would be happy to extend our test to our Lido testnet nodes.  
We believe in inclusion preconfirmations as a meaningful unlock for Ethereum, and think that Bolt specifically can deliver on this use case and other positive applications, like inclusion lists.

---

<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 3, 2024, 3:37pm UTC](https://research.lido.fi/t/perch-request-for-node-operators-to-run-and-test-bolt/8698/4 "2024-12-03T15:37:03Z")

</div>

Linking our recent post for our Holesky v1 deployment:

> [@\[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…

Most up-to-date info can be found here!
