Discover and read the best of Twitter Threads about #libp2p
Most recents (3)
1/20🧵
Let's take a deep dive into the intricacies of Internet Protocols (IPs) like TCP/IP, their history, and how these systems parallel to the Ethereum blockchain ecosystem.
This thread is technical - buckle up! #InternetProtocols #Ethereum
Let's take a deep dive into the intricacies of Internet Protocols (IPs) like TCP/IP, their history, and how these systems parallel to the Ethereum blockchain ecosystem.
This thread is technical - buckle up! #InternetProtocols #Ethereum
2/20
TCP/IP, the backbone of the internet, has its roots in the ARPANET project of the 1960s-70s.
It's a suite of protocols for data transmission and routing. TCP/IP is layered, each with its specific tasks:
Network Interface, Internet, Transport, and Application. #TCP_IP
TCP/IP, the backbone of the internet, has its roots in the ARPANET project of the 1960s-70s.
It's a suite of protocols for data transmission and routing. TCP/IP is layered, each with its specific tasks:
Network Interface, Internet, Transport, and Application. #TCP_IP
3/20
The Network Interface layer (eg, Ethernet) takes care of the physical transmission of data.
Internet layer (eg, IP) ensures data packets are routed correctly
Transport layer (eg, TCP) guarantees reliable transmission
Application layer (eg, HTTP) is for user interactions
The Network Interface layer (eg, Ethernet) takes care of the physical transmission of data.
Internet layer (eg, IP) ensures data packets are routed correctly
Transport layer (eg, TCP) guarantees reliable transmission
Application layer (eg, HTTP) is for user interactions
Curious what goes on inside an #eth2 client? Let's take a look at some colourful boxes loosely depicting the @ethnimbus implementation.. 
Small thread about a #rustlang #libp2p design mistake I made.
When you write, for example an HTTP server, each connection is handled on its own, and all of them are handled concurrently.
If multiple connections need mutable access to something, you lock a mutex.
When you write, for example an HTTP server, each connection is handled on its own, and all of them are handled concurrently.
If multiple connections need mutable access to something, you lock a mutex.
Using a mutex is not a problem, because you don't care in which order requests in multiple different connections are being handled, and therefore you don't care whether connection A locks the mutex first or connection B.
But in a peer to peer environment, it's different.
But in a peer to peer environment, it's different.
In peer to peer systems, you want to handle the network as a whole. When you receive a pubsub message from a node, you want to relay it to the others.
When you receive a peer discovery query, you need to return the nodes you're connected to, and so on.
When you receive a peer discovery query, you need to return the nodes you're connected to, and so on.
