As per Ethereum's rollup-centric roadmap, full-scale Danksharding requires extra blob data to be available for others to download. Efficient verification of a blob's availability can be achieved through the process of data availability sampling, allowing the network to come to consensus on this data's availability without increasing the computational resources required for a node.
Between this increase in information (from 90 KB to 128 MB per block!) and our new communication paradigm (data availability sampling), Ethereum's Consensus Layer P2P Network needs an upgrade.
Designs around how Ethereum's Consensus Layer P2P Network network can communicate this new information is an open question known as the Data Availability Sampling Networking problem.
One possible solution to part of the DAS Networking problem is to create a Secure Kademlia DHT overlay network atop Discv5, with the goal of facilitating a robust structured network where samples could be efficiently stored and retrieved throughout Ethereum's consensus layer network. This S/Kad overlay network would serve as a backup in case the primary network was attacked.
DAS Playground aims to combine Dankrad's idea of a Secure Kademlia DHT with the main data struct, DASNode, found within Timofey and Eric's discv5 overlay simulation, DAS Prototype, to create the networking stack nodes need for a DAS p2p networking design.
DAS Playground and DAS Prototype leverage Trin's overlay protocol + Sigma Prime's discv5 protocol to support these custom overlay networks.
DASNodes contain discv5, overlay, and secure overlay protocol structs, services and message processing. The discv5 protocol powers these overlay networks via its TalkReq/TalkResp message. DAS Playground's instance of discv5 seems to be supporting all base protocol Overlay Network functionality needed for overlay routing table maintenance.
Note: As of right now the overlay and secure overlay protocol structs are functionally the same. There is no updated secure kademlia routing table logic that allows for desired secure overlay properties: our DASNode just has two separate routing tables that can send and receive discv5 TalkReq/TalkResp messages to each individual subnetwork. I'm beginning work on a secure kademlia library that will (hopefully) integrate in with this repository.
- Send and receive samples via overlay and secure overlay networks
- Implement all other Portal Wire Protocol Message types:
- Ping/Pong
- FindNodes/FoundNodes
- FindContent/FoundContent
- Offer/Accept
- Combine overlay functions' logic
- Implement concurrent communication
- Integrate SecureDAS Overlay within Model DAS
- Create attacks and fallback network logic