Skip to content

Commit 4fa1416

Browse files
committed
fix: remove outdated subtext
subtext was in reference to an older image
1 parent fbc9ee7 commit 4fa1416

File tree

1 file changed

+0
-2
lines changed
  • public/content/developers/docs/nodes-and-clients/node-architecture

1 file changed

+0
-2
lines changed

public/content/developers/docs/nodes-and-clients/node-architecture/index.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ The diagram below shows the relationship between the two Ethereum clients. The t
1212

1313
![](node-architecture-text-background.png)
1414

15-
_This image is borrowed from geth.ethereum.org and uses the Geth logo to represent execution clients - there are other options for the execution client including Erigon, Nethermind and Besu_
16-
1715
For this two-client structure to work, consensus clients must be able to pass bundles of transactions to the execution client. Executing the transactions locally is how the client validates that the transactions do not violate any Ethereum rules and that the proposed update to Ethereum’s state is correct. Likewise, when the node is selected to be a block producer the consensus client must be able to request bundles of transactions from Geth to include in the new block and execute them to update the global state. This inter-client communication is handled by a local RPC connection using the [engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md).
1816

1917
## What does the execution client do? {#execution-client}

0 commit comments

Comments
 (0)