Thread by @jcksie

Curious what goes on inside an #eth2 client? Let's take a look at some colourful boxes loosely depicting the @ethnimbus implementation..

#eth2 uses #libp2p to establish a peer-to-peer network - each node opens encrypted connections to other nodes using chronos and nim-libp2p, purpose-built networking libraries in @nim_lang, and multiplex several protocols like gossip and eth2/sync over that link using `mplex`

On top of #libp2p, we build the #eth2 network core - protocol details, serialization, peer scoring, discv5 to feed it with fresh peers etc - we get a little playful here with @nim_lang, using some of its niche features to good performance and readability advantage

The Beacon Core is the heart of the beacon node, keeping track of blocks and attestations, establishing consensus on what the head of the chain is based on the view that its given from the network layer - this is where we find #eth2 state transition and fork choice logic

The beacon core presents a view of the network and can be run by anyone - validators however also run the validator core to produce blocks and attestations (votes) - this is where your private keys go!

Finally the UX! Being a something of a server process, we interact with it through logs, RPC and metrics - the code is built as a library and can be embedded inside other applications or run stand-alone from a command line near you on a platform of your choice ;)

Like the software, the fancy diagrams are still in motion - feel free to drop by miro.com/app/board/o9J_… and leave a comment ;)