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

## Long term topic I'm working on
Rewrite the validator client code to be compatible with the Beacon API instead of prysmaticlabs' internal API.

Ticket [here](https://github.com/prysmaticlabs/prysm/issues/11580).

## Actions done
Not so much things done, since I was off the majority of this week.
- Fixed PR comments in this [pull request](https://github.com/prysmaticlabs/prysm/pull/11786) to replace usage of `eth/v1alpha1/validator/statuses` gRPC API in Prysm by the equivalent in Beacon API. `statuses` is useful when the Validator Client needs to know the status of multiple validator keys.
- Published this [pull request](https://github.com/prysmaticlabs/prysm/pull/11816) to replace usage of `eth/v1alpha1/validator/registration` gRPC API in Prysm by the equivalent in Beacon API. `registration` is useful when a validator wants to register for external block building (typically when using MEV-boost or equivalent, and relays)