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

I've instantiated both overlay network protocol structs and message processing within DAS Playground (the simplified DAS simulation), implementing the major architectural designs behind our Secure Kademlia DHT for DAS Netowrking.

The first step to creating my secure overlay network within Model DAS has also been taken: I've created the SecureDAS Content Key and Validator trait (needed for creating an overlay protocol struct).

Unfinished

I still have to encorperate the remaining secure overlay logic into Model DAS!

This includes:

• Implementing the secondary "SecureDAS" overlay network into the DASNode struct
• Create additional message processing within the DASNode struct
• Populating the SecureDAS routing tables for each node
• Measuring benchmarks on how this secondary routing table performs

Future of the Project

Now that I've got a deep understanding of Timofey and Eric's simulation and how to create this secondary overlay network, it's time to create the secondary overlay network within Model DAS.

Self-Evaluation

Four months ago I was riddled with imposter syndrome and was almost paralyzed with fear of "messing up". Despite uncertainties within myself, I pressed on!

Between Data Availability Sampling, Ethereum Networking, and Rust, there was a ton of prerequisite knowledge needed to take on my project for the EPF. I've learned so much about each of these topics and how they all harmonize to facilitate scaling within the Ethereum Protocol.

Waves of uncertainty still come up, but they're smaller and more managable.

I'm no longer scared to ask brilliant developers hard questions and now believe that I'm someone who can meaningfully contribute to the success of the Protocol.