-
Notifications
You must be signed in to change notification settings - Fork 408
docs: add clarity to statesync #1958
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
base: main
Are you sure you want to change the base?
Conversation
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
2. Retrieve light blocks for verification | ||
::: | ||
|
||
In `$HOME/.celestia-app/config/config.toml`, set the RPC endpoints: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we'd also need to leave a note here to set trusted height and hash, because it isn't clear to me. if you set height/hash higher than 1, for example at 5000, do you not sync anything before that height 5000?
Overview
Statesync section needs more clarity around what the user needs to set. From what was written (and from not reading closely enough), I thought I didn't need to set up RPCs.