Summary I started to look at the pyspec project. It's a work related to consensus-specs test generators. The [consensus-specs] is repository that describe in python what must be done by consensus clients. To ensure there are doing the same things for the same objects, there are test generators. The run is super slow, I am not sure why but most likely du to many I/O operations. I haven't worked much this week because I had hard time with my work, lo siento. I am working on fixing some redundant generator tests on consensus-specs; not a complicated fix but ask me a lot of time to understand the generator structure. Ressources project wishlist

Summary This first week was consacred to things I forget/didn’t known/not well understand about Ethereum. I also started to think about the project to work on. I wanted a micro-economics one (RIG opened questions) but I think I would not have enough time for that kind of subjects (research topics). Ressources RLP serialization: already know about that, but I needed a reminded. RLPx transport protocol: I didn't there was a dedicated protocol for node communicatio. Honestly I am not an expert of transport protocols so it like a pain-in-the-*** to read. I found a python implementation that is not much clearer. ephemery.pk910: one of the project is an ephemery testnet; and I remember that for my job, we needed to find a testnet that give users a lot of ETH; an intern find this project, so I re-took a look at it. It centralized (1 person manage the node) but a good starting point. It seems to be the current implementation of the ephemery-testnet from Ethereum. Engine API: after Mario presentation about Ethereum, I discovered a new service I didn't know: the engine API which make the CL to communicate with the EL; like to get payloads, block hashes etc. Engine API geth implementation: that's the go code for the interface design here. It refer to the EL here and may be called by the CL. I also understood how it lives along side with the execution API. I was wondering if the node.Node could facilitate the deployment of a REST API wrapper of the JSON-RPC API but it requires a rpc.API type, so it might not help. I found a TODO that may interest some people that might read this note :panda_face:.