Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(docker): adds nethermind #348

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

stdevMac
Copy link

This PR allows to run nethermind instead of taiko-geth only in this repo.

Updated:

  • Readme
  • Env files
  • Docker compose files

Will be submitting a PR to the documentation also!

Let me know any possible issue

@stdevMac stdevMac changed the title Add nethermind to simple-taiko-node feat: add nethermind to simple-taiko-node Dec 17, 2024
@stdevMac stdevMac changed the title feat: add nethermind to simple-taiko-node feat: add nethermind to docker Dec 17, 2024
@stdevMac stdevMac changed the title feat: add nethermind to docker feat: Adds nethermind to docker Dec 17, 2024
@stdevMac stdevMac changed the title feat: Adds nethermind to docker feat(docker): Adds nethermind Dec 17, 2024
@stdevMac stdevMac changed the title feat(docker): Adds nethermind feat(docker): adds nethermind Dec 17, 2024
@davidtaikocha
Copy link
Member

@RogerLamTd Could u give this a try?

@RogerLamTd
Copy link
Contributor

RogerLamTd commented Jan 16, 2025

Hi @stdevMac sorry for the delay! I'm testing syncing this on Hekla at the moment and ran into the following log:

prometheus-1           | ts=2025-01-16T06:18:23.536Z caller=scrape.go:1347 level=debug component="scrape manager" scrape_pool=geth target=http://l2_execution_engine:6060/debug/metrics/prometheus msg="Scrape failed" err="server returned HTTP status 404 Not Found"

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 start-l2-execution-engine.sh script.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants