# Ethereum Protocol Fellowship - The Third Cohort (Update 1)

## Presentation
I'm currently working at Kiln.fi (staking company, node operator for LIDO), where I take care of our Ethereum infrastructure (few thousands of validators keys).

I use "heavily" Prysm/Teku BN/VC (often connected to Geth) for a part of our validator keys.

I would me more than happy to add contributions to "inside" of a Beacon Node and/or a Validator Client!

My background: Robotics / SW engineering / Infrastructure (Mainly Python / C++ as programming language).

Github: https://github.com/nalepae/

## Current topics of interest regarding ETH development
- Shanghai update (withdraw)
- PBS
- More generally, censorship fighting
- Secret Leader Election
- 1 slot finality
- ... and more

## Specific topic of interest during the EPF:
- Beacon API compliant validator client: Long term project of rewriting the validator client code to be compatible with the Beacon API instead of prysmaticlabs' internal API.
- But also OK to explore other topics as long as it deals with Beacon Node / Validator Client development

## Actions
- Created [this ticket](https://github.com/prysmaticlabs/prysm/issues/11580)
- Talking to Prysm developers and other cohort members about **Beacon API compliant validator client** on this newsly created [Discord channel](https://discord.com/channels/476244492043812875/1034494554461712456)

## Readings
- Consensus layer book from Ben Edginton https://eth2book.info/altair/ and especially the commented spec.
- [ETH Beacon API Swagger](https://ethereum.github.io/beacon-APIs/)
- [ETH Consensus spec](https://github.com/ethereum/consensus-specs/)
- [Specific gRPC Prysm documantation](https://docs.prylabs.network/docs/how-prysm-works/prysm-public-api)