week 8 & 9 updates Created a rough implementation without tests for one of the public API methods in peerDAS, compute_cells_and_kzg_proofs. It involves implementation of several other functions as well. Plan is to implement those three of the public functionalities one by one and in that way all of the necessary spec functions will be implemented themselves. In this week, made a draft PR Week 10 roadmap

I was a bit busy from last week, could not write much code other than applying suggestions on my already written code given by mentors. But kept updated with the discussion going on in the peerdas-testing discord channel, where there was mention of PeerDAS fork-choice, validator custody and parameter changes and EIP-7594: Decouple network subnets from das-core. Plan For Next Week Discuss with mentors more on implementations and proceed with writing remaining cryptography. Keep Updated with the discussions.

Goals Accomplished this week [x] Completed project proposal and presentation slides. [x] Implemented cryptography on my local repository and made branch on my local fork of Constantine. [x] Working on PolynomialCoef related functions During the next week I plan to write the unit tests using the consensus test vectors as data for the tests. Other than that, I will try to write something about Lagrange interpolation and KZG commitments. I listened to PeerDAS breakout room where there was discussion regarding updating the consensus specs to include https://github.com/ethereum/consensus-specs/pull/3832 Plan For Next Week

This week I majorly spent my time in learning nim and the coding style of the Constantine library. I implemented some cryptography in nim on my local repository, cryptography just to get an idea how things are working. In addition to that , I have been working on making the proposal for <b>Extending KZG implementation to include PeerDAS in constantine</b> and also worked a bit for making the presentation. Also I am trying to keep up with latest peerDAS related updates like this one, EIP-7594: Decouple network subnets from das-core Goals for the next week

This week I majorly spent my time in understanding the requirements for adding implementations realted to peerDAS in constantine. I found the following peerDAS implementations relevant and went through the rust implementation : ethereum/research (mainly focused on polynomial reconstruction and kzg) Rust implementation by IARC, though it says ,it is yet expermimental. Other than that I am learning Nim using Nim by example and Nim in Action book. I am currently going through the EIP-7594 and the Constantine codebase. I have confirmed with Agnish about the things needed in constantine to extend its implementation to include peerDAS.

Updates During this week , I did the following things: I talked to Brechy about his cohort-3 project, helios-cl-p2p.Tried to understand what its status is , what did he implement and what is more to do on this idea. I have contacted the Helios team to get more details on that. Read the 2D data availability with kate commitments to understand some math. Rewatched the 2nd part of 2D DA and data reconstruction Danksharding Workshop | Devcon Bogotá Tring to understand Fast amortized Kate proofs (not completed yet). Contacted the nimbus team regarding constantine and waiting for their resources to understand more on what things need to be implemented. week 3 roadmap

Hey, I am excited to join 5th cohort of the Ethereum Prtocol fellowship. Looking forward to learn more about the core protocol research and development. Updates During this week , I researched about the following topics: P2P networking in light clients I explored on the P2P networking in the light clients and took an overview of a cohort-3 project, helios-cl-p2p. Read the Consensus layer p2p networking blog to understand networking. I took an overview of Portal Network and completed the Portal Network | Devcon Bogotá

Introduction to Data Availability (DA) In blockchain technology, Data Availability (DA) ensures that all participants, including or excluding a supermajority of full nodes, can access the necessary data to validate transactions. DA guarantees that data is published and not withheld, which is crucial for maintaining blockchain integrity and security. Unlike data storage or continuous availability, DA focuses on ensuring data can be accessed when needed. Importance of Data Availability DA is critical for scaling solutions like rollups. For example: Optimistic Rollups: Rely on DA to create fraud proofs. Without data, fraud proofs can't be generated, compromising security. ZK Rollups: Require all data to generate zero-knowledge proofs. Missing data can mean missing account updates, potentially leading to loss of account access. Data Availability Solutions