---
# System prepended metadata

title: 'EPF Cohort 4 Update #2'

---

In continuation to exploring Reth, I was able to understand better the design rationale behind reth.
It has become mandatory to operate a consensus client alongside the execution client to connect to any "post-Merge" network. This change occurred because the Ethereum execution layer now delegates the responsibility of consensus to a separate component called the consensus client.


Execution clients handle block and transaction execution and validation, whereas consensus clients decide which of these valid blocks form part of the blockchain. Consequently, running both an execution client and a consensus client in tandem is vital to ensure synchronization and active participation in the network.

## Next Steps
 Delving deep into the codebase to understand the implementations of the ethereum specification and what allows Reth to be faster when measured against other clients.


### Reading Materials
- [Reth Book](https://paradigmxyz.github.io/reth/)
- [Reth Presentation at ETHCC](https://docs.google.com/presentation/d/1ZxEp6Go5XqTZxQFYTYYnzyd97JKbcXlA6O2s4RI9jr4/mobilepresent?pli=1&slide=id.g252bbdac496_0_0)
- [Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf)