## EPF Week 13 Update
Hi everyone, this week I focused on two things:
- respond to beacon api [PR](https://github.com/ethereum/beacon-APIs/pull/552) comments and modify accordingly
- implement the VC side epbs block production logic in lighthouse, which would hit the new beacon api endpoints, TODO: Add PR here once get greenlight from lighthouse to open it

I wanted to get as much eyes on the beacon api PR, so I first mentioned it in the `epbs` Eth R&D discord channel. Then, I added it as a discussion item for the epbs breakout room that took place on Friday. Discussing in the breakout room was great because I was able to get instantaneous feedback from various core devs on some interesting discussion points like whether we should just extend `produceBlockV3` vs make a new `produceBlockV4`. TLDR: `produceBlockV4` will be the path forward.

While the beacon api PR was being looked at, I figured it was a good time to start implementing the api's we need for the self-building block production flow. I figured this was a good way to ensure the endpoints I spec'd out were robust enough for actual use.

I started by adding the new `GET` and `POST` routes to the validator client. This entailed ensuring proper json and ssz deserialization. Then, I modified the existing block proposer logic to call the new endpoints in order to:
1. get a Gloas `BeaconBlock`
2. sign and publish a Gloas `BeaconBlock`
3. get a `ExecutionPayloadEnvelope`
4. sign and publish an `ExecutionPayloadEnvelope`

### TODO Next Week
- Discuss with mentor whether the next most important thing is to:
- build out the ptc duties on the VC side
- build out the new endpoints from my PR on the beacon node side
- start writing tests on the VC for the new endpoints