In the last week's update, I was talking about network config computation. I managed to implement this now in Reth, which, as an execution client, only needs this config to work, so outside of some testing and code clean-up, Ephemery in Reth seems to be working: PR.
I looked into the state generation tool that is used by the Ephemery genesis build script. With the knowledge about the proccess, I looked into how the genesis state and the tooling around it looks like in Lighthouse. I found some functions that could help me with creating a new BeaconState according to some information about the Eth1 block and the execution payload header. These structures would still need to be created, filled with information that is fixed or given in the genesis.json file, and also manually filled with the validators, which need to be in a special format according to Lighthouse and ssz specs. This seems doable, but could still take some time, so I'm going to start working on it and see how much time it takes. There still is the option to temporarily run my own node and download the genesis information from there or to download the ssz from github releases, but both of these would require to quite significantly change the download function or to create another one, so I would prefer to spend the time trying to implement the generation functionality first.