# EPF5 Week 9 Updates (EIP-7732 implementation) This week I spent most of the time reviewing Prs from potuz , terence , Kira and also finally got my pr Process_withdrawal merged 😊after so many brain rackling hours trying to find out nil Pointer dereferencing error from the compiler. ### Process_withdrawal Testing Issue Resolution So the issue due to which it was throwing error was actually the way I designed it after getting some suggesstions and reviews from potuz.And my decision to just add epbs version into **existing test for process_withdrawal**. Basically it was taking the state.ExpectedWithdrawals() from the state and just setting the Withdrawal root with the hash of expectedwithdrawal as mentioned in my [previous week update](https://hackmd.io/UohIHCwRRQqeegIlMzbiRQ) which is why when it was not checking for any of the failing conditions like **Invalid withdrawal amount, Invalid validator index, Invalid withdrawal index, wrong number of partial withdrawal**,and others that were there for both electra and capella which is why it was panicking with a nil pointer seg fault because we were wanting it to error out for epbs as well. So the idea of reusing the same test suite for epbs failed. Also an exceptional Test case for **Parent Node is not full** in this case we are not throwing any err nor we send back state we just send a empty(nil)state and nil (err) from process_withdrawal fn so this needed special care. Taking all the above things into consideration I finally wrote a separate test for epbs fork even after writing that terence asked the same question I asked myself why can't we haave a integrated test instead of separate then after I shared my POV he approved it as well then had some deepsource issues in my pr which was to make it more simple by adding fns to it 1) For getting blinded payload and extracting root and comparing them in non-epbs states. 2) For decreasing balance and setting the next withdrawalIndex. After this it finally got merged got to learn a lot about how to choose test case and write them after truly understanding the edge cases and all the caveats when its a modification and how to write a code that is compatible with all the forks. #### Merged Pr (https://github.com/prysmaticlabs/prysm/pull/14297) Apart from this spent a lot of time in fixing my long standing pr for replacing mux with net/httpservemux its having a little difficulty in chaining middlewares and wrapping it around the router will share the complications of it oncce its merged into gateway-removal #### Replaced-Mux(https://github.com/prysmaticlabs/prysm/pull/14191) That's all for this week see you in the next one.