feat: Update mainnet.md with pops RPC rpc.celestia.pops.one#1418
feat: Update mainnet.md with pops RPC rpc.celestia.pops.one#1418
rpc.celestia.pops.one#1418Conversation
WalkthroughA new RPC endpoint, Changes
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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
|
There was a problem hiding this comment.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- nodes/mainnet.md (1 hunks)
Additional comments: 1
nodes/mainnet.md (1)
- 101-101: The addition of the new RPC endpoint
rpc.celestia.pops.oneto the list of Consensus RPC endpoints is correctly formatted and follows the established pattern of listing endpoints. This change enhances the document by providing users with more options for connecting to the Mainnet Beta. It's important to ensure that this endpoint is operational and correctly configured to serve its intended purpose for the network's users.
Overview
Checklist
Summary by CodeRabbit
rpc.celestia.pops.onefor Mainnet Beta participation nodes.