# Introduction Hi everyone, I'm Rupam. Got accepted into EPF cohort five as a fellow. Before EPF, I had been contributing to [Reth](https://github.com/paradigmxyz/reth) mostly and a bit to [lambdaworks](https://github.com/lambdaclass/lambdaworks), [constantine](https://github.com/mratsim/constantine) and [alloy](https://github.com/alloy-rs/alloy). I was also a part of the EPF study group. Recently I have been looking into light clients which allow you to trade-off some of the benefits of running a full node for large performance improvements that allow nodes to run with very low hardware requirements. # The Current State of Light Clients As of now, Nimbus and Lodestar are some of the few client teams with decent enough light client support. I have been looking into Prysm and they have had some of the stuff from [CL specs for altair fork](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair/light-client) implemented, but they were never fully completed. I reached out to Radek and started with running a node in the Holesky testnet using Geth and Prysm as the execution and consensus clients respectively to see if the already implemented light client features are working properly. #### Some resources which helped me with the above: * https://docs.prylabs.network/docs/install/install-with-script * https://docs.prylabs.network/docs/prysm-usage/checkpoint-sync * https://docs.prylabs.network/docs/reading/bazel # Conclusion I have been going through [CL specs](https://github.com/ethereum/consensus-specs) which I personally find very readable to get started with. I am trying to get familiar with the Golang and the Prysm codebase and other than that I also plan to read more about sync committee, finalization and last but not the least, educate myself more on light clients.