# Week 8
Hi Rahul here, the last couple of weeks have been very strainous on my mental health and i couldnt get much work done.
I reviewed the three endpoints
1. `/eth/v1/beacon/light_client/finality_update`
2. `/eth/v1/beacon/light_client/optimistic_update`
3. `/eth/v1/beacon/light_client/bootstrap/{block_root}`

All the endpoints were giving satisfactory results with good benchmarks and they seem to take less then 0.5ms to return . I had some initial confusion on what the block root value should be, turns out it is the finalised checkpoint block i.e the latest block of the start of an epoch(example- [2177504 block of epoch 68047] (https://holesky.beaconcha.in/epoch/68047)). If the slot does not contain any blocks then we have to consider the prior slot (example - [2177664 block of epoch 68052](https://holesky.beaconcha.in/epoch/68052).

Speaking with Saulius for the peerDas , he gave us pointers to explore
1. If clients are disconnecting, figure about why?
2. If the messages are not being correctly propagated , figure out wht?

For the first one he told us that client show why they dont want to connect with grandine using metrics.
If the peers are connected and they dont send messages then we need to see where the problem exist with debugging