Carlos Bermudez Porto

Hi @MaxTeiger, thanks for the report. I'm running a node to see if I can reproduce your error with the config you shared. Still, can you share the docker command...

One thing I have noticed its that the node struggles to find peers in Sokol. At least for me. Are you using bootnodes? I don't see those in your configs....

@MaxTeiger Thanks for the details, will review them. The resources I find about sokol testnet are the ones here: https://forum.poa.network/t/sokol-testnet-resources/1776

Sorry for the long time without updates. I'm having the same issues with the Nethermind archive I setup. So far I was unnable to find anything in the logs that...

@MaxTeiger Thanks for the rpcs. About your question, thats the purpose of the `enode://...`. And then use them as `--Discovery.Bootnodes` or `--Network.StaticPeers`. You can get a Nethermind node for its...

Hi @GLCNI @tharune . Thanks for reporting. Sadly this is a know issue an should be fixed in the next release. The problem is with a non existing generation path...

Hi @mtr980 and thanks for reporting. Did you install the docker compose plugin? That dependency is required for Sedge. In any case, will recommend you to update Sedge to the...

Right, the latest version can sometimes give that error. You can fix it with this command `export DOCKER_API_VERSION=1.41`.

Also, if Sedge command continues to give an error when running docker-compose commands copy it and run it separately. Share the logs here. That may have some more information about...

Hi @mdszn and thanks for reporting. About the jwtsecret issue in our newer version is something we are aware of. A quick fix for that should be adding the `-p...