Fix/toms cleanup branch #3
Conversation
There was a problem hiding this comment.
Will go through properly but my initial worry is having a separate genesis file location , all you end up doing is keeping the fork and versions in line , and any issues with genessis.ssz (which is the only genesis beacon uses) is an output from the tolling using the genesis.json file anyway so i think it maybe doesn't want to be in the files under geth but they should be neutral , the issue then though is the files load in config (which i like to keep it tidy) won't work without symlinks
|
it is nice to clean it up , but it should be temporary anyway though as i don't think we should run a bootnode we should run a geth node as a boot nod e(so different helm install , values.yaml as we have ) but i only wanted the bootnode to replicate my local setup and see why it wasn't working , i've changed my lcoal to use geth as abootnode , hyou just pass a nodekey to the geth node , but sitll this is valuable as it means we can switch and use this , but i think it almsot want to be another helm install to spin up when we want to debug a geth bootnode issue |
No description provided.