Skip to content

Commit 758f7dd

Browse files
Update src/content/developers/docs/nodes-and-clients/index.md
Co-authored-by: Joshua <62268199+minimalsm@users.noreply.github.com>
1 parent fe21d2b commit 758f7dd

File tree

1 file changed

+1
-1
lines changed
  • src/content/developers/docs/nodes-and-clients

1 file changed

+1
-1
lines changed

src/content/developers/docs/nodes-and-clients/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ If you're new to the topic of nodes, we recommend first checking out our user-fr
1919

2020
A "node" is any instance of Ethereum client software that is connected to other computers also running Ethereum software, forming a network. A client is an implementation of Ethereum that verifies data against the protocol rules and keeps the network secure.
2121

22-
Post-Merge Ethereum consists of two parts: the **execution layer** and the **consensus layer**. Both layers are run by different client software. On this page, we'll refer to them as the execution client and consensus client.
22+
Post-Merge Ethereum consists of two parts: the execution layer and the consensus layer. Both layers are run by different client software. On this page, we'll refer to them as the execution client and consensus client.
2323

2424
- The execution client (also known as the Execution Engine, EL client or formerly the Eth1 client) listens to new transactions broadcasted in the network, executes them in EVM, and holds the latest state and database of all current Ethereum data.
2525
- The consensus client (also known as the Beacon Node, CL client or formerly the Eth2 client) implements the proof-of-stake consensus algorithm, which enables the network to achieve agreement based on validated data from the execution client.

0 commit comments

Comments
 (0)