-
Notifications
You must be signed in to change notification settings - Fork 972
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
Providing trusted-hash produces daser errors #3163
Comments
If we don't provide the trusted hash flag - no errors |
Same error with latest commit 2ebca8f @Wondertan
|
A little guide to running a celestia node on a public network without waiting for it to sync:
|
Works! Thanks for the review. The cli flag can help immensely devRel and external teams devX wise |
Celestia Node version
a7c49d2
OS
linux/amd64 and macos/arm64
Install tools
docker or vanilla install
Others
No response
Steps to reproduce it
Expected result
node starts at a non-genesis height without errors
Actual result
daser errors with failed to get header from header store
Relevant log output
Notes
I also see that the daser can fail the whole 100 batches instead of just 1 like in the shared log
The text was updated successfully, but these errors were encountered: