# Week 3

Hi everyone Rahul here again,
This week was more focused towards Light Clients than the grandine implementation of PeerDas.
#### PeerDas
Upgrading the Eth_libp2p for grandine is becoming very challenging. After having a chat with @sauliusgrigaitis , we realised that grandine has been constantly backporting and changing the code from the lighthouse libp2p code so a substantial amount of code is missing from [the eip7594 branch](https://github.com/grandinetech/eth2_libp2p/tree/eip_7594) that was imported from the [das branch of lighthouse](https://github.com/sigp/lighthouse/tree/das/beacon_node/lighthouse_network).Further upgrades to the libp2p crate needs to happen on the [electra branch of grandine](https://github.com/grandinetech/eth2_libp2p/tree/feature/electra).

#### Light Clients
After many hardware constraints , I managed to run a client pair (geth and prysm) to mainly check the beacon node light client endpoints (only 2 of them are working for prysm)
- [✅] [/eth/v1/beacon/light_client/bootstrap/{block_root}](https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Beacon/getLightClientBootstrap)
- [✅] [/eth/v1/beacon/light_client/updates](https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Beacon/getLightClientUpdatesByRange) (someone who wants to test this, set `start_period` = slot_no / (slots_per_epoch* 256))
- [❌][/eth/v1/beacon/light_client/finality_update](https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Beacon/getLightClientFinalityUpdate)
- [❌][/eth/v1/beacon/light_client/optimistic_update](https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Beacon/getLightClientOptimisticUpdate)

I have tried to run all the tests in Prysm , it seems like 10 of them are failing. I am still looking forward to hear from [Radek](https://github.com/rkapka) on these and discuss where it went wrong and fix them.Meanwhile [Bastin](https://github.com/Inspector-Butters) made this amazing [doc](https://hackmd.io/@Bastin/HyKnoHh8R) that highlights the to-dos on light clients and we are waiting on a review from Radek.
I've been learning Go and have also been going through Prysm by comparing it to CL specs to understand how things are working over there.
Also the light clients need some metric collection in Lodestar, so i am also learning some Devops
At the time of this writing , I am listing 4 prs that reference to light clients in prysm
1. [Light client sync protocol](https://github.com/prysmaticlabs/prysm/pull/12853)
2. [light client http api](https://github.com/prysmaticlabs/prysm/pull/12984)
3. [Light client events](https://github.com/prysmaticlabs/prysm/pull/13225)
4. [REST VC metrics](https://github.com/prysmaticlabs/prysm/pull/13588)

## What's next?
1. Add metric collection to Light clients
2. Figure out the problems with the LightClient endpoints and possibly even fix them