Try   HackMD

Development Update 9

For a p2p network to exist, nodes need to be able to communicate (make requests and respond to one another). Remember: Each node is a client and server at the same time!

Message processing implements the server-side logic needed for a node to respond to another node's request.

Since my previous update I've set up some custom message processing for discv5 + overlay events within DAS Playground, have been digging into implementing message processing to support multiple overlay subnetworks, and continued writing within Summary of DAS Playground.

 

Overlay Message Processing

Message processing allows the server side of our DASNodes to filter through the different possible message requests (services) it provides and responds to requesters appropriately.

Our overlay networks utilize Discv5's TalkReq/TalkResp message to send data to others within their respective subnetwork. These messages usually pertain to information on peers in the network (routing table) or samples that a node needs.

Timofey and Eric's simulation only deals with one overlay subnetwork (DAS) and implements a single event loop to handle all message processing. My project creates two overlay subnetworks (DAS and Secure DAS): This is the first major deviation from DAS Prototype!

I'm currently figuring out how our DASNode should handle multiple overlay networks' requests.

I may have to implement some sort of proxy, like Trin, to handle all TalkRequests + TalkResponses within the two overlay subnetworks.

 

To Do

  • I recently discovered that our DASNode needs to implement a version of our overlay protocol for each subnetwork that we want to create. This means creating a new content key so message processing can know how to process data + store data.
  • Create our updated message processing task(s)
Last changed by 
 
Echo
0
251

Read more

Secure Kademlia Library

DAS Networking in Ethereum requires lots of small blob samples to be placed in a distributed network where arbitrary nodes can query “the network” to make sure these samples are available.

Aug 14, 2023
Aggregated DAS Content

This is a living document of my favorite Data Availability Sampling resources. 

Jul 5, 2023
Development Update #10

Before we get to the normal Dev Update... Over the past 4 months I dove deep into Danksharding, Ethereum Networking, and then p2p networking in rust + building out a discv5 overlay simulation. A few days back, I read a few "big-picture" Ethereum developer documents: Network Layer and Data Availability. Somewhere along the journey I lost the thread. I was building this Data Availability Sampling p2p network simulation without understanding the "why" behind it all.  

Apr 7, 2023
EPF Final Update

Tackling the DAS Networking problem requires a p2p network that has low-latency, is privacy preserving and is sybil-resistant. The idea behind Model DAS is to measure benchmarks on DAS querying via Secure Kademlia DHT Discv5 overlay network. This Secure K-DHT is a seperate validator-only overlay network that leverages validators' incentive alignment to create a robust DAS network if the primary network were to come under attack. Status Report The original vision for Model DAS didn't entail creating a new DAS simulation; the idea was just to extend the functionality of another. But seeing that I was new to gerenal networking concepts and the Rust programming language, it quickly became aparent that building a simplified version of DAS Prototype was an escential prerequisite to executing the vision behind Model DAS. Finished

Mar 1, 2023
Read more from Echo
Published on HackMD