## TLDR
I did some research on the projects that I was interested in, and the result was that I will start with "Light client server support in Prysm".
I also would like to do the "implementation of `eth_getTransactionBySenderAndNonce` in Geth", after the prerequisites are developed by [Sina](https://github.com/s1na), as discussed with him.

I also made some progress in the EPS material and will continue to do so.

## Recap of last week
Last week I went through the list of proposed projects for this cohort and the previous one, and I managed to create a list of 6 projects that were suitable. here are the projects:

1. Specification and implementation of [eth_getTransactionBySenderAndNonce](https://github.com/ethereum/execution-apis/issues/494) [[1]](https://github.com/eth-protocol-fellows/cohort-five/blob/main/projects/project-ideas.md#json-rpc-in-geth)
2. Implementing trace_* namespace in Geth [[1]](https://github.com/eth-protocol-fellows/cohort-five/blob/main/projects/project-ideas.md#json-rpc-in-geth)
3. Benchmarking APIs via flood and optimizing the methods in various clients, compare across clients [[1]](https://github.com/eth-protocol-fellows/cohort-five/blob/main/projects/project-ideas.md#json-rpc-in-geth)
4. Custom libp2p go implementation in Prysm [[2]](https://hackmd.io/@6-HLeMXARN2tdFLKKcqrxw/rkU0eLmEC)
5. Light client server support in Prysm [[2]](https://hackmd.io/q8fe302MQIayhtb9Aj-BJQ)
6. Consensus-level eth supply calculation and exposing it as an opcode [[3]](https://github.com/eth-protocol-fellows/cohort-five/blob/main/projects/project-ideas.md#ipsilon)

## What happened this week
This week I tried to research all the above ideas, and try to find one to start with.
I saw that projects 2, 3, and 4 are already being worked on by some of the fellows who are more experienced than me.
I started to get more familiar with project 1, I talked to Sina about it and asked what was his thoughts on this. after discussing it for some time, the decision was that Sina will work on creating a general indexing framework in Geth, so that we will be able to easily create an index for implementing this feature. So I will come back later to this task (if applicable).
After that he mentioned [blsync](https://github.com/ethereum/go-ethereum/pull/30057/files), and how the only consensus clients that implement light client support are Loadstar and Nimbus, and how it would be beneficial to have Prysm also implement these APIs (project 5).
So now my plan is to start working on this topic.

## What's next
In the coming week I will dive deep into Prysm and how it works, and also the specifications for the light client APIs. I will try to reach out to a member of the Prysm team so that I can ask what the ideal implementation would look like from their point of view. Also I would like to take a look into the implementation of these APIs in Nimbus and Loadstar.

I will also try to advance in the EPS material. they should be done in a week or two.

## Other notes
- Implementation of `getTransactionBySenderAndNonce` in [Erigon](https://github.com/ledgerwatch/erigon/blob/main/turbo/jsonrpc/otterscan_transaction_by_sender_and_nonce.go)