Skip to content

Commit 4ccbdcf

Browse files
committed
Execution and Consensus Layer Client Options drop down 4
1 parent 20a38ca commit 4ccbdcf

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

lib/ethereum/README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ Configure your setup.
100100
<summary>Geth Lighthouse</summary>
101101
<br>
102102

103-
### Configure your Node Runners Ethereum - Geth Lighthouse
103+
**Configure your Node Runners Ethereum - Geth Lighthouse**
104104

105105
To specify the Ethereum client combination you wish to deploy, create your own copy of `.env` file and edit it using your preferred text editor. The contents of your file for a Geth / Lighthouse node deployment is as follows, which uses a sample config from the repository:
106106
```bash
@@ -117,8 +117,9 @@ nano .env
117117
<details>
118118

119119
<summary>Erigon Lighthouse</summary>
120+
<br>
120121

121-
### Configure your Node Runners Ethereum - Erigon Lighthouse
122+
**Configure your Node Runners Ethereum - Erigon Lighthouse**
122123

123124
To specify the Ethereum client combination you wish to deploy, create your own copy of `.env` file and edit it using your preferred text editor. The contents of your file for a Erigon / Prysm node deployment is as follows, which uses a sample config from the repository:
124125
```bash
@@ -135,8 +136,9 @@ nano .env
135136
<details>
136137

137138
<summary>Erigon Prysm</summary>
139+
<br>
138140

139-
### Configure your Node Runners Ethereum - Erigon Prysm
141+
**Configure your Node Runners Ethereum - Erigon Prysm**
140142

141143
To specify the Ethereum client combination you wish to deploy, create your own copy of `.env` file and edit it using your preferred text editor. The contents of your file for a Erigon / Prysm node deployment is as follows, which uses a sample config from the repository:
142144
```bash

0 commit comments

Comments
 (0)