# EPF5 Week 12 Updates (EIP-7732 implementation)

GM Web3 🫡

I hope you guys are having a great time.

So, following up on Last week's updates, this week, I have successfully created a website in DocuSaurus and deployed it to GitHub pages.
[Website Link](https://redidacove.github.io/execution-api-specs/)

Still, lightclient didn't reply to any feedback on Discord literally created 68 pages but maybe it's not what he wanted maybe or needs some improvement we will know still it was a nice experience setting up and creating my first docusaurus website and got to learn so much about each API and input and output(req-resp).

Other than that opened a few prs on reth, execution-api repo, and prysm for replacing the hardcoded values that was done in config but not used anywhere as asked by prestonvanloon to replace the state function which used to compute it had to close the original as core members had argues inside to go slowly and to make it smooth
so currently just hardcoded rpc, slasher, and p2p packages asked if I could hardcode sync as well and they asked not to hardcode core packages like state, and blockchain.
[Pr link](https://github.com/prysmaticlabs/prysm/pull/14404)

Meanwhile also contributed to reth other than the previous week's pr which was closed due to being restructuring in the main code pr by matsee [this pr](https://github.com/paradigmxyz/reth/pull/10520) is approved by Emilia Hane just an unrelated lint issue left which she said will be fixed once it is merged with main.

Other than this also contributed to the execution api repo and got reviewed on this by lightclient and made changes to that as well it was an addition of 7702 txn type in schema asked by matsee waiting for its clearance and getting this [pr](https://github.com/ethereum/execution-apis/pull/575) merged.

As promised last week trying to learn LLD to understand ePBS's LLD and explain it in a blog or something just prysm implementation lld.

Also had the plan to create a website in Docusaurus which has different pages containing package details about what the specific package does in the consensus client and also contains some sort of explanation for each fn and its flow and role in the architecture this way it would be better for new comers to just learn about what each package do so that they can think of how to implement a specific idea to the client. Without getting overwhelmed with the code base kind of specific client implementation details.

So that if we want can search any fn or related keyword and easily find it and learn and think better on how to modify or create new fns kinda newBie's guide to it.

Not sure if it's a great idea and if will I get support from the community or not would like to give it a shot and if possible get a grant to do this so that more folks can collab and make it better.

Any Feedback is welcome on this not even sure if anyone has read this or not.

Show your presence by liking this blog or commenting below.

See Ya in the next one bubye 👋🏻