# EPF - Week 4 ### Progress report This week I have been studying [ePBS specification notes](https://hackmd.io/uWVGcvcKSoqS4P5c5NHG3g). I also participated in ePBS breakout room and EPF office hours where potuz did a presentation on ePBS. I was happy to hear that potuz thinks implementing ePBS in other clients (like Lighthouse), while using prysm as a reference implementation, will be a valuable contribution, because that was exactly what I wanted to do. I also learned about some of the prerequisites to ePBS: [EIP-7251](https://eips.ethereum.org/EIPS/eip-7251), [EIP-7002](https://eips.ethereum.org/EIPS/eip-7002) and something similar to [EIP-7547](https://eips.ethereum.org/EIPS/eip-7547). EIP-7251 increases the max effective balance of validators. In the context of ePBS it's needed because we want to enshrine `builders` (that themselves are validators) who will pay to `proposers` from their staked balance - that balance should not be capped at 32 eth. EIP-7002 allows initiating a validator exit with a withdrawable credential. ePBS wants to use the same mechanism that would allow making withdrawals in EIP-7002 to make simple immediate transfers from builders to proposers. EIP-7547. ePBS itself adds an inclusion list mechanism that works in the same way as EIP-7547 known as *forward forced inclusion list*. [^1]: https://ethresear.ch/t/epbs-design-constraints/18728 ### Next week Next week I'm going to contact with mentors and write a project proposal. I need to find other people who might be interested in implementing ePBS in Lighthouse, or team up to implement ePBS in many clients under 1 project proposal.