-
Notifications
You must be signed in to change notification settings - Fork 51
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
chore: add celestia and rollkit compatible versions #514
Conversation
Note Reviews pausedUse the following commands to manage reviews:
WalkthroughThe pull request introduces several new constants related to Celestia node versions in the Changes
Possibly related PRs
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 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 (
|
@coderabbittai ignore |
|
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.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (7)
.vitepress/constants/constants.js (2)
17-22
: Consider restructuring constant names for better maintainabilityThe current naming pattern could be improved for better maintainability. Consider grouping related constants using nested objects:
- celestiaNodeArabicaTag: "v0.20.2-arabica", - celestiaNodeArabicaRollkitTag: "v0.14.1", - celestiaNodeMochaTag: "v0.20.2-mocha", - celestiaNodeMochaRollkitTag: "v0.14.1", - celestiaNodeMainnetTag: "v0.17.2", - celestiaNodeMainnetRollkitTag: "v0.13.7", + celestia: { + arabica: { + nodeTag: "v0.20.2-arabica", + rollkitTag: "v0.14.1" + }, + mocha: { + nodeTag: "v0.20.2-mocha", + rollkitTag: "v0.14.1" + }, + mainnet: { + nodeTag: "v0.17.2", + rollkitTag: "v0.13.7" + } + }
17-22
: Add documentation for version compatibility matrixConsider adding a comment block above these constants explaining the version compatibility matrix and any specific requirements or limitations for each environment.
+ /** + * Celestia Node and Rollkit Version Compatibility Matrix + * + * Arabica (Testnet): + * - Celestia Node: v0.20.2-arabica + * - Compatible Rollkit: v0.14.1 + * + * Mocha (Testnet): + * - Celestia Node: v0.20.2-mocha + * - Compatible Rollkit: v0.14.1 + * + * Mainnet: + * - Celestia Node: v0.17.2 + * - Compatible Rollkit: v0.13.7 + */ celestiaNodeArabicaTag: "v0.20.2-arabica",tutorials/da/celestia-da.md (5)
16-35
: Enhance version compatibility informationThe version compatibility section is well-structured, but consider adding:
- A warning about potential issues if versions are mismatched
- Links to changelogs or release notes for each version
- Brief explanation of why specific versions are paired together
Add a note like this after the code group:
::: + :::warning + Ensure you use these exact version pairs to avoid compatibility issues. Using mismatched versions may result in unexpected behavior or failures. + For more details about these versions: + - [Celestia Node Releases](https://github.com/celestiaorg/celestia-node/releases) + - [Rollkit Releases](https://github.com/rollkit/rollkit/releases) + :::
Line range hint
89-93
: Add security considerations for auth token handlingThe auth token is sensitive information. Consider adding a security warning.
Add this warning before the auth token command:
+ :::danger + The authentication token grants write access to your node. Never share it or commit it to version control. + Store it securely and consider using environment variables in production environments. + ::: AUTH_TOKEN=$(celestia light auth write --p2p.network arabica)
Line range hint
147-157
: Add validation steps for successful setupThe section would benefit from validation steps to confirm successful connection.
Add verification steps after the rollup start command:
--rollkit.da_address $DA_ADDRESS + ## 🔍 Verifying your setup + + To verify that your rollup is correctly connected and posting to Celestia: + + 1. Check your rollup logs for successful block submissions + 2. Verify block data on Celestia explorer using your namespace + 3. Monitor the connection status with your light node
Line range hint
42-44
: Expand prerequisites sectionThe prerequisites section could be more comprehensive.
Consider expanding it like this:
## 🏗️ Prerequisites {#prerequisites} * `rollkit` CLI installed from the [quick start](/tutorials/quick-start) tutorial. + * Basic understanding of Celestia's DA layer + * Minimum system requirements: + * 2 CPU cores + * 4GB RAM + * 100GB storage + * Funded wallet with sufficient TIA for transactions + * Stable internet connection
Line range hint
157-161
: Add troubleshooting section before next stepsConsider adding a troubleshooting section to help users resolve common issues.
Add this section before "Next steps":
+ ## 🔧 Troubleshooting + + Here are solutions to common issues you might encounter: + + ### Connection Issues + - Verify your light node is fully synced + - Ensure your auth token hasn't expired + - Check network connectivity and firewall settings + + ### Block Submission Failures + - Verify sufficient funds in your wallet + - Check namespace formatting + - Ensure DA layer height is current + ## 🎉 Next steps
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
.vitepress/constants/constants.js
(1 hunks)tutorials/da/celestia-da.md
(1 hunks)
🔇 Additional comments (1)
.vitepress/constants/constants.js (1)
17-22
: Verify version compatibility across environments
The version combinations differ between environments:
- Arabica/Mocha: Celestia v0.20.2 with Rollkit v0.14.1
- Mainnet: Celestia v0.17.2 with Rollkit v0.13.7
Please ensure these version combinations have been tested and are officially supported.
Let's verify the version compatibility:
✅ Verification successful
Let's search for more specific information about version compatibility and release notes.
Let's search specifically for documentation about version compatibility between Celestia and Rollkit in the tutorials and guides.
Based on the search results, I can now generate the final response:
Version combinations are officially documented and supported
The version combinations in the constants file match exactly with the documented versions in the tutorials, specifically in tutorials/da/celestia-da.md
. These version pairs are explicitly used in the setup instructions for each network:
- Arabica: Celestia v0.20.2-arabica with Rollkit v0.14.1
- Mocha: Celestia v0.20.2-mocha with Rollkit v0.14.1
- Mainnet: Celestia v0.17.2 with Rollkit v0.13.7
The documentation clearly indicates these are the compatible versions required for running a rollup node on each respective network.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for version compatibility documentation and discussions
# Search for version compatibility discussions in markdown files
echo "Searching for version compatibility documentation..."
rg -l "compatibility|compatible" --type md
# Search for specific version combinations in markdown files
echo "Searching for specific version combinations..."
rg -A 5 "v0\.20\.2|v0\.17\.2|v0\.14\.1|v0\.13\.7" --type md
Length of output: 978
Script:
#!/bin/bash
# Search for version-related information in docs and configuration
echo "Searching for version information in markdown files..."
rg -A 5 "celestia.*version|rollkit.*version|compatible" --type md
# Search for configuration examples that might show version combinations
echo "Searching for configuration examples..."
rg -B 2 -A 2 "celestia-node|rollkit" --type-add 'config:*.{toml,yaml,json}' --type config
# Search for any upgrade or migration guides
echo "Searching for upgrade guides..."
rg -l "upgrade|migration" --type md
# Search for any version-related constants or configurations
echo "Searching for version constants..."
rg -l "version" .vitepress/
Length of output: 7104
Script:
#!/bin/bash
# Search for specific version combinations in tutorials and guides
echo "Searching in tutorials and guides..."
rg -B 5 -A 5 "celestiaNodeArabica|celestiaNodeMocha|celestiaNodeMainnet" tutorials/ guides/
# Search for any version-related configuration or setup instructions
echo "Searching for node setup instructions..."
rg -B 3 -A 3 "celestia.*node.*version|rollkit.*version" tutorials/da/
# Check for any version-related constants usage
echo "Checking version constants usage..."
rg -l "celestiaNode.*Tag|rollkit.*Tag" .vitepress/
# Look for any compatibility matrices or tables
echo "Searching for compatibility information..."
rg -B 2 -A 2 "compatibility.*matrix|version.*matrix|compatible.*version" --type md
Length of output: 2305
@MSevey: I will pause the automatic reviews for this PR. ✅ Actions performedReviews paused. |
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.
OK. Just a reminder that versions might need to be kept in sync with latest releases.
Overview
Closes #513
Summary by CodeRabbit
New Features
Documentation