Conversation
|
@RogerLamTd Could u give this a try? |
|
Hi @stdevMac sorry for the delay! I'm testing syncing this on Hekla at the moment and ran into the following log: I believe prometheus is having trouble scraping from the 6060 endpoint for the nethermind exec engine, but I see the port is exposed in the Another thing is that the taiko client driver doesn't seem to have access to the exec engine sync progress, the logs coming from that service indicate only the HighestBlock value despite the exec engine logging indicating it is syncing old headers. Not sure if this is intended, please correct me if I'm wrong! From what I can tell, after fully syncing the issues go away aside from the prometheus one, but I have yet to test proposing/proving. Will do so soon! EDIT: block batch iterator issue is gone with a newer version of the client, pls ignore! Prometheus scraping issue still persists |
This PR allows to run nethermind instead of taiko-geth only in this repo.
Updated:
Will be submitting a PR to the documentation also!
Let me know any possible issue