# Week1 Update

## Rethink implementation path
Because the project is basically selected, Implement FOCIL in the Grandine client. I continue to improve my [proposal](https://hackmd.io/@grapebaba/HkjNOK97gl) this week. Previously, it was planned to implement the modifications in Beacon, P2P, Forkchoice and Validator according to the modules in the consensus spec. With further understanding of EIP-7805 and familiarity with Grandine codebase, I slightly adjusted the implementation path, and changed my thinking to first implement the basic types and the parts that connect to the outside include P2P and Engine API, and then implement the remaining parts according to the duties of different roles.

## Read updated FOCIL spec
Because in the previous review process of the spec, many people discussed, the author collected some suggestions, recently resubmitted the update of the [spec](https://github.com/ethereum/consensus-specs/pull/4351), I also found a typo error in original PR and already fixed by the update.

I read the new PR checkout of the new spec locally, and found that it mainly modifies the content related to the `unsatisfied_inclusion_list_blocks` and deletes the fields that are not used. And [EIP-7782](https://ethereum-magicians.org/t/eip-7782-the-case-for-2x-shorter-slot-times-in-glamsterdam/24616) may affect EIP-7805 design.

## Dive into Grandine and other client impls
This week, I took a deeper look at the code of multiple modules of Grandine, and marked the code that needs to be modified and added in my [proposal](https://hackmd.io/@grapebaba/HkjNOK97gl). Meanwhile I also read the FOCIL implementation of prysm and lighthouse to check if I am missing anything. The current proposal is basically completed, and I hope to sort out the duties process of each role again next week.

## Next
I hope to send the proposal to Grandine's mentor review next week, collect feedback and revisit it.