## EPF - Week 9 This week we got the changes to use 256-bit word size merged and was able to get some of the state opcodes implemented. No blockers. ### 256-bit word size This took a bit longer than planned, but we have [merged the changes](https://github.com/2xic/erigon-risc-v-executable-proof-sourcing/pull/3) to use 256-bit word size consistently throughout the transpilation module. We did not yet explore new ways of doing the testing setup so for now, there is some difference in code paths between what we run on Unicorn versus the OpenVM toolchain which would be nice to clean up, but it's not blocking anything. ### State opcodes We created a [draft PR](https://github.com/2xic/erigon-risc-v-executable-proof-sourcing/pull/4) which implements support for `CALLVALUE` and `CALLDATASIZE`, this is done by loading the state from the `.data` section. We will implement the remaining state opcodes needed for the [hello world contract](https://hackmd.io/rPta9aOqTmKauiLOh7rPYw#Opcodes-to-implement-for-next-week) next week. The remaining state (`CALLDATALOAD`, `SLOAD`, etc) opcodes will be implemented in a similar way using the `.data` section. One thing to note is that since we chose the `.data` section approach, even similar execution traces will need to be recompiled because of changes in state variables. This might change later on, but was decided to be easier for now. ### Next week By the end of next week we are done with the first milestone of this project and should be able to produce execution proofs for the [hello world contract](https://hackmd.io/rPta9aOqTmKauiLOh7rPYw#Opcodes-to-implement-for-next-week). I don't see any risk or blockers which would prevent us from hitting that milestone so the next update should include an execution proof of that example contract.