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

celestia-node v0.14.0: RPC port no longer necessary for nodes to query state #1558

Merged
merged 2 commits into from
May 2, 2024

Conversation

renaynay
Copy link
Member

@renaynay renaynay commented May 2, 2024

I tried to add all information I could here, but @jcstein maybe you can also help to make sure I've addressed all areas where rpc port is mentioned for state queries for DA nodes

What's important to note is that

LNs and FNs no longer need a --core.rpc.port period but BNs still need it for block syncing.

This feature will only be included in v0.14.0 of celestia-node!

Summary by CodeRabbit

  • New Features
    • Updated terminology from "Consensus RPC endpoints" to "consensus gRPC endpoint."
    • Simplified port configuration for Data Availability (DA) nodes, now requiring only one port for gRPC communication.
  • Documentation
    • Updated descriptions and configurations related to DA RPC and gRPC endpoints for Bridge Node sync and state access.
    • Added information about Bridge nodes syncing blocks from the Celestia network.
  • Refactor
    • Consolidated port configurations for easier setup and clarity.

Copy link
Contributor

coderabbitai bot commented May 2, 2024

Walkthrough

The update aims to standardize and simplify network communication protocols in the Celestia network by transitioning to a single gRPC endpoint for consensus and data availability functionalities, improving configuration clarity and efficiency.

Changes

File Path Change Summary
nodes/arabica-devnet.md Updated terminology to use "consensus gRPC endpoint" and simplified DA node port configuration.
nodes/docker-images.md Revised RPC endpoint setting instructions for different networks in the Docker image setup guide.
nodes/mainnet.md Enhanced descriptions and configurations for DA RPC and gRPC endpoints, focusing on Bridge Node sync.
nodes/mocha-testnet.md Refined DA RPC and gRPC endpoint definitions for bridge nodes syncing blocks in the Celestia network.

Possibly related issues

🐰🎉
A hop, a skip, a network tweak,
From dual ports to gRPC's peak.
Simplified, streamlined, oh so sleek,
Cheers to updates we proudly speak!
🌟🌌🚀


Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between c7c861d and 90498cc.
Files selected for processing (4)
  • nodes/arabica-devnet.md (1 hunks)
  • nodes/docker-images.md (1 hunks)
  • nodes/mainnet.md (1 hunks)
  • nodes/mocha-testnet.md (1 hunks)
Additional Context Used
LanguageTool (157)
nodes/arabica-devnet.md (72)

Near line 5: Possible spelling mistake found.
Context: ...guide to Arabica devnet. --- # Arabica devnet ![arabica-devnet](/img/arabica-devnet....


Near line 9: Possible spelling mistake found.
Context: ...vnet](/img/arabica-devnet.png) Arabica devnet is a testnet from Celestia Labs that is...


Near line 9: Possible spelling mistake found.
Context: ...rabica-devnet.png) Arabica devnet is a testnet from Celestia Labs that is focused excl...


Near line 9: Possible spelling mistake found.
Context: ....png) Arabica devnet is a testnet from Celestia Labs that is focused exclusively on pro...


Near line 11: Possible spelling mistake found.
Context: ...d the latest upgrades for testing their rollups and applications. Arabica does not foc...


Near line 14: Possible spelling mistake found.
Context: ...vel testing, rather, that is what Mocha testnet is used for. If you are a validator, we...


Near line 16: Possible spelling mistake found.
Context: ...your validator operations on the Mocha testnet. ## Network stabi...


Near line 20: Possible spelling mistake found.
Context: ...Arabica has the latest updates from all Celestia's products deployed on it, it can be su...


Near line 25: Possible spelling mistake found.
Context: .... Developers can still deploy on Mocha testnet their sovereign rollups if they chose t...


Near line 25: Possible spelling mistake found.
Context: ...deploy on Mocha testnet their sovereign rollups if they chose to do so, it just will al...


Near line 26: ‘lag behind’ might be wordy. Consider a shorter alternative.
Context: ...hey chose to do so, it just will always lag behind Arabica devnet until Mocha undergoes Ha...


Near line 26: Possible spelling mistake found.
Context: ... it just will always lag behind Arabica devnet until Mocha undergoes Hardfork Upgrades...


Near line 27: Possible spelling mistake found.
Context: ...nd Arabica devnet until Mocha undergoes Hardfork Upgrades in coordination with Validator...


Near line 46: Possible spelling mistake found.
Context: ... sections for how to connect to Arabica devnet, depending on the type of node you are ...


Near line 49: Consider a shorter alternative to avoid wordiness.
Context: ...guide will link to the relevant network in order to show you how to connect to them. Learn ...


Near line 55: Consider a shorter alternative to avoid wordiness.
Context: ...ndpoints and types of nodes you can run in order to participate in Arabica devnet: <!-- ma...


Near line 56: Possible spelling mistake found.
Context: ... run in order to participate in Arabica devnet: ...


Near line 60: Possible typo: you repeated a whitespace
Context: ...kdownlint-disable MD013 --> | Node type | Endpoint type | End...


Near line 60: Possible typo: you repeated a whitespace
Context: ... | Endpoint type | Endpoint ...


Near line 60: Possible typo: you repeated a whitespace
Context: ...point type | Endpoint | | ------------------------------------...


Near line 62: Possible typo: you repeated a whitespace
Context: ...full) | Consensus RPC | `ht...


Near line 62: Possible typo: you repeated a whitespace
Context: ... | Consensus RPC | https://rpc.celestia-arabica-11.com ...


Near line 62: Possible typo: you repeated a whitespace
Context: ... | https://rpc.celestia-arabica-11.com | | ...


Near line 63: Possible typo: you repeated a whitespace
Context: ... | | | API | `ht...


Near line 63: Possible typo: you repeated a whitespace
Context: ... | API | https://api.celestia-arabica-11.com ...


Near line 63: Possible typo: you repeated a whitespace
Context: ... | https://api.celestia-arabica-11.com | | ...


Near line 64: Possible typo: you repeated a whitespace
Context: ... | | | gRPC | `gr...


Near line 64: Possible typo: you repeated a whitespace
Context: ... | gRPC | grpc.celestia-arabica-11.com:443 ...


Near line 64: Possible typo: you repeated a whitespace
Context: ... | grpc.celestia-arabica-11.com:443 | | ...


Near line 65: Possible typo: you repeated a whitespace
Context: ... | | | Direct endpoints with open ports | Ope...


Near line 65: Possible typo: you repeated a whitespace
Context: ...p), 26657 (RPC), 1317 (API), 9090 (GRPC) | | ...


Near line 66: Possible typo: you repeated a whitespace
Context: ... | | | | `va...


Near line 66: Possible typo: you repeated a whitespace
Context: ... | | validator-1.celestia-arabica-11.com ...


Near line 66: Possible typo: you repeated a whitespace
Context: ... | validator-1.celestia-arabica-11.com | | ...


Near line 67: Possible typo: you repeated a whitespace
Context: ... | | | | `va...


Near line 67: Possible typo: you repeated a whitespace
Context: ... | | validator-2.celestia-arabica-11.com ...


Near line 67: Possible typo: you repeated a whitespace
Context: ... | validator-2.celestia-arabica-11.com | | ...


Near line 68: Possible typo: you repeated a whitespace
Context: ... | | | | `va...


Near line 68: Possible typo: you repeated a whitespace
Context: ... | | validator-3.celestia-arabica-11.com ...


Near line 68: Possible typo: you repeated a whitespace
Context: ... | validator-3.celestia-arabica-11.com | | ...


Near line 69: Possible typo: you repeated a whitespace
Context: ... | | | | `va...


Near line 69: Possible typo: you repeated a whitespace
Context: ... | | validator-4.celestia-arabica-11.com ...


Near line 69: Possible typo: you repeated a whitespace
Context: ... | validator-4.celestia-arabica-11.com | | ...


Near line 70: Possible typo: you repeated a whitespace
Context: ... | | | | ...


Near line 70: Possible typo: you repeated a whitespace
Context: ... | | ...


Near line 70: Possible typo: you repeated a whitespace
Context: ... | | | | Data availability nodes ...


Near line 71: Possible typo: you repeated a whitespace
Context: ... | | Data availability nodes | DA Bridge Node Endpoints | `/d...


Near line 71: Possible typo: you repeated a whitespace
Context: ... | DA Bridge Node Endpoints | `/dns4/da-bridge-1.celestia-arabica-11...


Near line 72: Possible typo: you repeated a whitespace
Context: ...e.md), full) | | `/dns4/da-bridge-2.celestia-arabica-11...


Near line 73: Possible typo: you repeated a whitespace
Context: ...fCN9ZLAViGfLUWAfXP5pCm78NFKb9jpBtua| | | |/d...


Near line 73: Possible typo: you repeated a whitespace
Context: ... | | `/dns4/da-bridge-3.celestia-arabica-11...


Near line 74: Possible typo: you repeated a whitespace
Context: ...NpukDFGVoHW3RoeUU53Ec9t9v5cwW3MkVdQ| | | |/d...


Near line 74: Possible typo: you repeated a whitespace
Context: ... | | `/dns4/da-bridge-4.celestia-arabica-11...


Near line 75: Possible typo: you repeated a whitespace
Context: ...XWSBjh7tU1HQanF5M64dHV6AuM6cYEJxMPk| | |--core.ip string` endpoints | Ref...


Near line 75: Possible spelling mistake found.
Context: ... | --core.ip string endpoints | Refer to "Direc...


Near line 75: Possible typo: you repeated a whitespace
Context: ... | --core.ip string endpoints | Refer to "Direct endpoints with open p...


Near line 75: Possible typo: you repeated a whitespace
Context: ..."Direct endpoints with open ports" above | Y...


Near line 85: Possible spelling mistake found.
Context: ...ow bridge nodes to sync blocks from the Celestia network. For users, they will need to p...


Near line 86: Possible spelling mistake found.
Context: ... For users, they will need to provide a –core.ip string from a consensus node’s URL or ...


Near line 93: Possible spelling mistake found.
Context: ...sactions (balances, blobs, etc.) to the Celestia network. For users, they will need to p...


Near line 94: Possible spelling mistake found.
Context: ... For users, they will need to provide a –core.ip string from a consensus node’s URL or ...


Near line 106: Possible spelling mistake. ‘initialise’ is British English.
Context: ...t ``` ::: RPCs for DA nodes to initialise or start your celestia-node to Arabica ...


Near line 106: Possible spelling mistake found.
Context: ...or DA nodes to initialise or start your celestia-node to Arabica devnet with can be found in ...


Near line 107: Possible spelling mistake found.
Context: ... or start your celestia-node to Arabica devnet with can be found in the table in the "...


Near line 119: Consider removing “of” to be more concise
Context: ...com ``` :::tip Bridge node runners Not all of the RPC endpoints do not guarantee the full...


Near line 125: Possible spelling mistake found.
Context: ...g for your bridge node. ::: ## Arabica devnet faucet :::danger WARNING USING THIS FA...


Near line 128: Possible spelling mistake found.
Context: ...TO ANY AIRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SA...


Near line 129: Possible spelling mistake found.
Context: ...IRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SALES OF AN...


Near line 129: Possible spelling mistake found.
Context: ...OKENS. THERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS. ::: ### Discord You ...


Near line 129: Possible spelling mistake found.
Context: ...HERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS. ::: ### Discord You can reque...


Near line 135: Possible spelling mistake found.
Context: ...# Discord You can request from Arabica devnet Faucet on the #arabica-faucet channel o...


Near line 135: Possible spelling mistake found.
Context: ...aucet on the #arabica-faucet channel on Celestia's Discord server with the following com...

nodes/docker-images.md (30)

Near line 17: Possible spelling mistake found.
Context: ...ipt> This page has instructions to run celestia-node using Docker. If you are looking for in...


Near line 18: Possible spelling mistake found.
Context: ...you are looking for instructions to run celestia-node using a binary, please refer to the [ce...


Near line 19: Possible spelling mistake found.
Context: ...de using a binary, please refer to the celestia-node page. Using Docke...


Near line 21: Possible spelling mistake found.
Context: ... Using Docker is the easiest way to run celestia-node for most users. Docker is a containeriz...


Near line 22: Possible spelling mistake found.
Context: ...ization platform that allows you to run celestia-node in an isolated environment. This means...


Near line 25: Possible spelling mistake found.
Context: ...vironment. This means that you can run celestia-node on your machine without having to worry...


Near line 26: Consider removing “of” to be more concise
Context: ... worry about installing and configuring all of the dependencies required to run the node. ...


Near line 31: Possible spelling mistake found.
Context: ...gement in Docker, visit the [Docker and cel-key section](../developers/celestia-node-k...


Near line 31: Possible spelling mistake found.
Context: ... visit the Docker and cel-key section. The easiest way to install Docker is...


Near line 39: Unpaired symbol: ‘[’ seems to be missing
Context: ...es - Docker Desktop for Mac or Windows and...


Near line 40: Possible typo: you repeated a word
Context: ...-docker) and a basic understanding of Docker - [Docker Engine for Linux](https://docs.docker.c...


Near line 41: Unpaired symbol: ‘[’ seems to be missing
Context: ...ing of Docker - [Docker Engine for Linux](https://docs.docker.com/engine/install/...


Near line 82: Possible spelling mistake found.
Context: ...::: 3. Set an RPC endpoint for either [Mainnet Beta](./mainnet.md#data-availability-da...


Near line 82: Possible spelling mistake found.
Context: ...an RPC endpoint for either Mainnet Beta, [Mocha](./mocha-testnet.md#rpc-end...


Near line 83: Possible spelling mistake found.
Context: ...c-endpoints-for-state-access), Mocha, or [Arabica](./arabica-devnet.md#r...


Near line 84: Possible spelling mistake found.
Context: ...estnet.md#rpc-endpoints), or Arabica using the bare URL (without http or...


Near line 85: Possible spelling mistake found.
Context: ...dpoints) using the bare URL (without http or https): ```bash export RPC_UR...


Near line 85: Possible spelling mistake found.
Context: ... using the bare URL (without http or https): ```bash export RPC_URL=this-is...


Near line 115: Possible spelling mistake found.
Context: ... ::: Congratulations! You now have a celestia-node running! If you would like to run the ...


Near line 119: Possible spelling mistake found.
Context: ...ith custom flags, you can refer to the [celestia-node tutorial](../developers/node-tutorial.m...


Near line 120: Possible spelling mistake found.
Context: ...age. Refer to [the ports section of the celestia-node troubleshooting page](./celestia-node-t...


Near line 156: Consider a shorter alternative to avoid wordiness.
Context: ... ### Initialize the node store and key In order to mount a volume to the container, you ne...


Near line 157: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...to mount a volume to the container, you need to specify the path to the volume. When yo...


Near line 169: Possible spelling mistake found.
Context: ...ODE_TYPE init [args...] ``` An example init command will look similar to below: ::...


Near line 259: A comma might be missing here.
Context: .../div> ## Troubleshooting For security purposes Celestia expects to interact with the y...


Near line 259: Possible spelling mistake found.
Context: ... Troubleshooting For security purposes Celestia expects to interact with the your node'...


Near line 259: A determiner cannot be combined with a possessive pronoun. Did you mean simply “the” or “your”?
Context: ...poses Celestia expects to interact with the your node's keys in a read-only manner. This...


Near line 260: Possible spelling mistake found.
Context: ...ead-only manner. This is enforced using linux style permissions on the filesystem. Wi...


Near line 261: Possible spelling mistake found.
Context: ...ed using linux style permissions on the filesystem. Windows NTFS does not support these ty...


Near line 262: Consider adding a comma after this introductory phrase.
Context: ...upport these types of permissions. As a result the recommended path for Windows users ...

nodes/mainnet.md (32)

Near line 3: Possible spelling mistake found.
Context: # Mainnet Beta <script setup> import MainnetVers...


Near line 12: Possible spelling mistake found.
Context: ...net-Beta.png) Welcome to the guide for Celestia’s Mainnet Beta, the production network ...


Near line 12: Possible spelling mistake found.
Context: ...g) Welcome to the guide for Celestia’s Mainnet Beta, the production network that marks...


Near line 13: Possible spelling mistake found.
Context: ...tion network that marks the pinnacle of Celestia’s evolution since its inception in 2019...


Near line 14: Possible spelling mistake found.
Context: ... network is where all components of the Celestia ecosystem come to life in a real-world ...


Near line 16: Possible spelling mistake found.
Context: ...e to life in a real-world environment. Mainnet Beta is the culmination of rigorous com...


Near line 18: Possible spelling mistake found.
Context: ...It serves as the platform for deploying mainnet rollups and applications. ## Network s...


Near line 19: Possible spelling mistake found.
Context: ...s as the platform for deploying mainnet rollups and applications. ## Network stability...


Near line 22: Possible spelling mistake found.
Context: ...ns. ## Network stability and upgrades Mainnet Beta is a stable network, but will stil...


Near line 25: Possible spelling mistake found.
Context: ...ted with node operators and the broader Celestia community to ensure seamless integratio...


Near line 29: Possible spelling mistake found.
Context: ...sampling, it's crucial to remember that Mainnet Beta remains experimental at this stage...


Near line 45: Possible spelling mistake found.
Context: ...s.md?plain=1#L30), can be found in the [celestia-app specifications](https://celestiaorg.git...


Near line 47: Unpaired symbol: ‘[’ seems to be missing
Context: ...elestia-app/specs/params.html). [CIP-13](https://github.com/celestiaorg/CIPs/blo...


Near line 60: Possible missing comma found.
Context: ...ximum square size is 64x64, which gives us 4096 shares. - One share is reserved fo...


Near line 79: Possible spelling mistake found.
Context: ...arameter and a hard-coded constant in CometBFT. - The number of shares occupied by the...


Near line 87: Possible spelling mistake found.
Context: ...relevant sections for how to connect to Mainnet Beta, depending on the type of node you...


Near line 90: Consider a shorter alternative to avoid wordiness.
Context: ...guide will link to the relevant network in order to show you how to connect to them. Learn ...


Near line 94: Consider a shorter alternative to avoid wordiness.
Context: ...tions of the types of nodes you can run in order to participate in Mainnet Beta: ### Conse...


Near line 95: Possible spelling mistake found.
Context: ... you can run in order to participate in Mainnet Beta: ### Consensus nodes - [Full con...


Near line 180: Possible spelling mistake found.
Context: ...estia-grpc.noders.services:11090 #### WebSocket endpoints -wss://celestia-ws.chainod...


Near line 192: Possible spelling mistake found.
Context: ...ow bridge nodes to sync blocks from the Celestia network. For users, they will need to p...


Near line 193: Possible spelling mistake found.
Context: ... For users, they will need to provide a –core.ip string from a consensus node’s URL or ...


Near line 200: Possible spelling mistake found.
Context: ...sactions (balances, blobs, etc.) to the Celestia network. For users, they will need to p...


Near line 201: Possible spelling mistake found.
Context: ... For users, they will need to provide a –core.ip string from a consensus node’s URL or ...


Near line 219: Possible spelling mistake. ‘initialise’ is British English.
Context: ... bridge node. ::: RPCs for DA nodes to initialise or start your celestia-node to Mainnet ...


Near line 219: Possible spelling mistake found.
Context: ...or DA nodes to initialise or start your celestia-node to Mainnet Beta with: - `public-celest...


Near line 219: Possible spelling mistake found.
Context: ...itialise or start your celestia-node to Mainnet Beta with: - `public-celestia-consensu...


Near line 240: Possible spelling mistake found.
Context: .../uptime status of DA bootstrappers (now celestia network only). You can [find the stat...


Near line 253: Possible spelling mistake found.
Context: ... endpoints You can [provision your own Celestia Archival endpoint on Grove](https://gro...


Near line 254: Possible spelling mistake found.
Context: ...(https://grove.city). [Learn more about Celestia on Grove](https://docs.grove.city/celes...


Near line 263: Possible spelling mistake found.
Context: ... are multiple explorers you can use for Mainnet Beta: - [https://celenium.io](https://...


Near line 275: Possible spelling mistake found.
Context: ...ollowing websites provide analytics for Celestia: - [https://analytics.smartstake.io/ce...

nodes/mocha-testnet.md (23)

Near line 5: Possible spelling mistake found.
Context: ...nect to the Mocha network. --- # Mocha testnet mocha-testnet This...


Near line 10: Possible spelling mistake found.
Context: ...the type of node you are running. Mocha testnet is designed to help validators test out...


Near line 13: Possible spelling mistake found.
Context: ...re encouraged to deploy their sovereign rollups on Mocha, but we also recommend [Arabic...


Near line 13: Possible spelling mistake found.
Context: ...n Mocha, but we also recommend Arabica devnet for that as it is...


Near line 14: Possible missing comma found.
Context: ...rabica devnet](./arabica-devnet.md) for that as it is designed for development purpo...


Near line 16: Possible spelling mistake found.
Context: ...ment purposes. Mocha is a milestone in Celestia, allowing everyone to test out core fun...


Near line 59: Possible spelling mistake found.
Context: ...ow bridge nodes to sync blocks from the Celestia network. For users, they will need to p...


Near line 60: Possible spelling mistake found.
Context: ... For users, they will need to provide a –core.ip string from a consensus node’s URL or ...


Near line 67: Possible spelling mistake found.
Context: ...sactions (balances, blobs, etc.) to the Celestia network. For users, they will need to p...


Near line 68: Possible spelling mistake found.
Context: ... For users, they will need to provide a –core.ip string from a consensus node’s URL or ...


Near line 72: Only proper nouns start with an uppercase character (there are exceptions for headlines).
Context: ...espective DA node. :::tip Bridge nodes Mentioned below RPC endpoints do not guarantee yo...


Near line 75: Consider a shorter alternative to avoid wordiness.
Context: ...nsensus node](./full-consensus-node.md) in order to download full blocks from it. ::: - `p...


Near line 87: Possible spelling mistake found.
Context: ...oint is to allow users to interact with Celestia's nodes by querying the node's state an...


Near line 88: Possible spelling mistake found.
Context: ...te and broadcasting transactions on the Celestia network. The default port is 26657. - ...


Near line 108: Possible missing comma found.
Context: ...to interact with the REST API in Cosmos SDK which is implemented using gRPC-gateway...


Near line 130: Possible spelling mistake found.
Context: ...nt is to allow users to interact with a Celestia Node using gRPC, a modern open-source a...


Near line 178: Possible spelling mistake found.
Context: ...mocha-4.da.celestia-mocha.com ## Mocha testnet faucet :::danger WARNING USING THIS FA...


Near line 181: Possible spelling mistake found.
Context: ...TO ANY AIRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SA...


Near line 182: Possible spelling mistake found.
Context: ...IRDROP OR OTHER DISTRIBUTION OF MAINNET CELESTIA TOKENS. THERE ARE NO PUBLIC SALES OF AN...


Near line 182: Possible spelling mistake found.
Context: ...OKENS. THERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS. ::: You can request f...


Near line 182: Possible spelling mistake found.
Context: ...HERE ARE NO PUBLIC SALES OF ANY MAINNET CELESTIA TOKENS. ::: You can request from Mocha...


Near line 186: Possible spelling mistake found.
Context: ...TOKENS. ::: You can request from Mocha testnet Faucet on the #mocha-faucet channel on ...


Near line 186: Possible spelling mistake found.
Context: ... Faucet on the #mocha-faucet channel on Celestia's Discord server with the following com...

Additional comments not posted (1)
nodes/mainnet.md (1)

197-203: The updates to the gRPC endpoints are clear and align with the PR's objectives to simplify network configurations.


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

@jcstein
Copy link
Member

jcstein commented May 2, 2024

thank you for this PR as well @renaynay. It looks like you found the 2 occurrences of this in docs. Can you confirm that a bridge node can be started with --core.ip <RPC-URL>:<PORT>? I think that is why there is no --core.rpc.port in the bridge node docs? example: celestia bridge start --core.ip rpc-mocha.pops.one:26657 --p2p.network mocha

@liamsi
Copy link
Member

liamsi commented May 2, 2024

but BNs still need it for block syncing.

This will change once this lands and node adopts it: celestiaorg/celestia-app#3421

@jcstein
Copy link
Member

jcstein commented May 2, 2024

note to self to add

  • modified description on mocha page

@jcstein jcstein merged commit 878e4c0 into celestiaorg:main May 2, 2024
1 check failed
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: 5

Out of diff range and nitpick comments (1)
nodes/mocha-testnet.md (1)

Line range hint 94-95: Replace the en dash with a hyphen - in –core.ip string to avoid potential issues in command execution.

- –core.ip string
+ --core.ip string


:::tip

```bash
celestia <da_type> start --core.ip <url> –core.rpc.port <port> \
–core.grpc.port <port>
celestia <da_type> start --core.ip <url> -–core.grpc.port <port>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct the command syntax error.

- celestia <da_type> start --core.ip <url> -–core.grpc.port <port>
+ celestia <da_type> start --core.ip <url> --core.grpc.port <port>

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
celestia <da_type> start --core.ip <url> -core.grpc.port <port>
celestia <da_type> start --core.ip <url> --core.grpc.port <port>

Comment on lines +60 to +62
For users, they will need to provide a `–core.ip string`
from a consensus node’s URL or IP that populates a default RPC port at 26657
to their respective DA node.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace the en dash with a hyphen - in –core.ip string to avoid potential issues in command execution.

- –core.ip string
+ --core.ip string

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
For users, they will need to provide a `core.ip string`
from a consensus node’s URL or IP that populates a default RPC port at 26657
to their respective DA node.
For users, they will need to provide a `--core.ip string`
from a consensus node’s URL or IP that populates a default RPC port at 26657
to their respective DA node.

@@ -79,7 +79,7 @@ Ubuntu. You can

:::

3. Set an RPC endpoint for either [Mainnet Beta](./mainnet.md#da-rpc-endpoints),
3. Set an RPC endpoint for either [Mainnet Beta](./mainnet.md#data-availability-da-grpc-endpoints-for-state-access),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace the en dash with a hyphen - in –core.ip string to avoid potential issues in command execution.

- –core.ip string
+ --core.ip string

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
3. Set an RPC endpoint for either [Mainnet Beta](./mainnet.md#data-availability-da-grpc-endpoints-for-state-access),
3. Set an RPC endpoint for either [Mainnet Beta](./mainnet.md#data-availability-da-grpc-endpoints-for-state-access),

Comment on lines +86 to +87
For users, they will need to provide a `–core.ip string`
from a consensus node’s URL or IP that populates a default RPC port at 26657
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace the en dash with a hyphen - in –core.ip string to avoid potential issues in command execution.

- –core.ip string
+ --core.ip string

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
For users, they will need to provide a `core.ip string`
from a consensus node’s URL or IP that populates a default RPC port at 26657
For users, they will need to provide a `--core.ip string`
from a consensus node’s URL or IP that populates a default RPC port at 26657

Comment on lines +94 to +95
Celestia network. For users, they will need to provide a `–core.ip string`
from a consensus node’s URL or IP that populates a default gRPC port at 9090
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace the en dash with a hyphen - in –core.ip string to avoid potential issues in command execution.

- –core.ip string
+ --core.ip string

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
Celestia network. For users, they will need to provide a `core.ip string`
from a consensus node’s URL or IP that populates a default gRPC port at 9090
Celestia network. For users, they will need to provide a `--core.ip string`
from a consensus node’s URL or IP that populates a default gRPC port at 9090

renaynay added a commit to celestiaorg/celestia-node that referenced this pull request May 9, 2024
…for state reads (#3359)

Resolves #3357 

Blocked on patch release from app including
celestiaorg/celestia-app#3424

Corresponding docs PR celestiaorg/docs#1558
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants