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

chore: add celestia and rollkit compatible versions #514

Merged
merged 1 commit into from
Nov 19, 2024
Merged

Conversation

MSevey
Copy link
Contributor

@MSevey MSevey commented Nov 19, 2024

Overview

Closes #513

Summary by CodeRabbit

  • New Features

    • Added new constants related to Celestia node versions and tags for enhanced functionality.
  • Documentation

    • Updated deployment instructions for rollups on Celestia's data availability network, including new requirements and clearer guidance on node versions.
    • Improved formatting and clarity of instructions for querying the DA layer and setting up namespaces.

Copy link
Contributor

coderabbitai bot commented Nov 19, 2024

Note

Reviews paused

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Walkthrough

The pull request introduces several new constants related to Celestia node versions in the .vitepress/constants/constants.js file. Additionally, the tutorials/da/celestia-da.md document has been updated to enhance deployment instructions for rollups on Celestia's data availability network, emphasizing version compatibility for light nodes and clarifying configuration flags. These changes aim to provide clearer guidance for users.

Changes

File Change Summary
.vitepress/constants/constants.js Added new constants: celestiaNodeArabicaTag, celestiaNodeArabicaRollkitTag, celestiaNodeMochaTag, celestiaNodeMochaRollkitTag, celestiaNodeMainnetTag, celestiaNodeMainnetRollkitTag.
tutorials/da/celestia-da.md Enhanced instructions for deploying rollups, clarified light node version requirements, and improved formatting for existing sections.

Possibly related PRs

Suggested reviewers

  • yarikbratashchuk
  • jcstein
  • gupadhyaya
  • Manav-Aggarwal

🐰 In the land of code where rabbits hop,
New constants added, we’ll never stop!
With guidance clear, our rollups will soar,
Celestia shines, oh, we’ll explore!
So gather ‘round, let’s code and play,
In the world of tech, we’ll hop all day! 🌟


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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@MSevey
Copy link
Contributor Author

MSevey commented Nov 19, 2024

@coderabbittai ignore

Copy link
Contributor

PR Preview Action v1.4.8
🚀 Deployed preview to https://rollkit.github.io/docs-preview/./pr-514/
on branch main at 2024-11-19 18:56 UTC

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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 maintainability

The 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 matrix

Consider 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 information

The version compatibility section is well-structured, but consider adding:

  1. A warning about potential issues if versions are mismatched
  2. Links to changelogs or release notes for each version
  3. 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 handling

The 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 setup

The 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 section

The 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 steps

Consider 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

📥 Commits

Reviewing files that changed from the base of the PR and between b3d71c5 and fad69ef.

📒 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

Copy link
Contributor

coderabbitai bot commented Nov 19, 2024

@MSevey: I will pause the automatic reviews for this PR.

✅ Actions performed

Reviews paused.

Copy link
Contributor

@tuxcanfly tuxcanfly left a 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.

@MSevey MSevey merged commit 6a2eae8 into main Nov 19, 2024
10 checks passed
@MSevey MSevey deleted the celestia-verion branch November 19, 2024 20:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Verify Celestia Node version and add to docs
2 participants