# Week 14 and 15 This week was extremely busy and also very important. Finally we were able to run the eest testsuite using hive and got all passed. # BAL works: To be honest most of the week we had our midterms in our college. Before that we have already refactored and rebased our codebases so we started working rightway. [Ishika](https://github.com/Rimeeeeee) generated the new fixture that has `engine_newPayloadV5` and added a new check but all the checks were failing. Upon inspecting the logs we saw that none of the state changes are being recorded. I found it super weird as it was all working a week before. We rechecked the code and I found that the component that matches all the hardforks with revm specid was moved from reth to alloy-evm. It didnt have Amsterdam (we had before when it was in reth) so upon adding that again, all was working accordingly. However the new fixture has some new checks and some of our tests were failing with a block access list mismatch error. Upon tabulating them we saw three things missing: 1. All BALs have one less entry then expected(coinbase) 2. Nonce change has a wrong balance change ( I looked at previous logs and it was correct so we figured it was due to new refactors) 3. Code change was not getting recorded ( it was a problem with how we were populating the BAL, I extracted the address and fixed it accordigly) However to avoid further bugs like this we cleaned up the evm impl by using a iterator over state. These were address specific bugs, after fixing all the consume-rlp tests were passing (tho it took both of us 14hrs that day). Consume-engine was still a mess. We tried a lot of things but they didnt pass. Finally we went through the existing code but didnt find any significant error. Later I was manually generating the **payload** and **block** from the json available in the fixture. Using **serde_json** I saw that the **block_access_list_hash** was **None**. It was an error while converting from payload to block, and upon fixing them all was working but with wrong error mappings. I pushed a commit to my fork of eest mapping all the reth errors with eest errors and finally after so many attempts [all tests passed](https://github.com/paradigmxyz/reth/actions/runs/18055613513/job/51385001065?pr=18432). Currently I am hoping to improve the perf a bit, run new sets of eest after release and give the branch to Toni and Felipe for interop with other clients. Along with these work I also had the chance to have a meet with Josh for the mid cohort meeting. It was a great experience talking with him. I also got sick this week so wasnt able to join the breakout but watched the recording. Now BAL will also feature precompiles. Hopefully we will be able to do it too. Next week is the Durga Puja, the biggest holidays of our culture, so will be a bit tough to work but hopefully we will manage. # Resources Since we commited directly without making prs, here are all the codes we added in all the repos so far : - [evm](https://github.com/Rimeeeeee/evm/pull/8) - [reth](https://github.com/paradigmxyz/reth/pull/18432) - [alloy](https://github.com/Soubhik-10/alloy/pull/15) - [eest](https://github.com/Soubhik-10/execution-spec-tests/commit/34fce6983a0646c260533c3802e7ff143186bdd1) - [revm](https://github.com/Soubhik-10/revm/pull/19)