Skip to content

docs: remove down community endpoints from mainnet and Mocha#2433

Merged
rootulp merged 2 commits intocelestiaorg:mainfrom
rootulp:rootulp/remove-down-mainnet-endpoints
Feb 26, 2026
Merged

docs: remove down community endpoints from mainnet and Mocha#2433
rootulp merged 2 commits intocelestiaorg:mainfrom
rootulp:rootulp/remove-down-mainnet-endpoints

Conversation

@rootulp
Copy link
Copy Markdown
Contributor

@rootulp rootulp commented Feb 26, 2026

Closes https://linear.app/celestia/issue/DA-1078/remove-down-rpc-endpoints-from-mainnet-beta-docs
Closes #2428

Summary

  • Remove 10 down community consensus endpoint providers from the mainnet-beta page: 0xcryptovestor, Brightly Stake, Chainode, Cumulo, Grove, Lava, Mzonder, NodeStake, Stakeflow, Trusted Point (11 active providers remain)
  • Remove down community endpoints from the Mocha testnet page across RPC, API, and gRPC sections: BrightlyStake, Trusted Point, Stakeflow, Cumulo archive, Mzonder, Grove, Lava, celestia-mocha.com API
  • Remove empty Community JSON-RPC Endpoints and Community Tendermint RPC Endpoints sections from Mocha (all entries were down)

Arabica

Arabica endpoints were also checked. The main HTTPS-proxied endpoints (rpc.celestia-arabica-11.com, api.celestia-arabica-11.com) are healthy. The direct validator port endpoints (26657/1317) refuse connections, but these are Celestia Labs infrastructure (not community-provided) and may intentionally be firewalled behind the HTTPS proxy.

Test plan

  • Verified all remaining mainnet endpoints return HTTP 200 on RPC /status and API /cosmos/base/tendermint/v1beta1/blocks/latest
  • Verified all remaining Mocha RPC and API endpoints return HTTP 200
  • Verify the mainnet-beta and Mocha testnet pages render correctly with the updated lists

🤖 Generated with Claude Code

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the documentation for Celestia nodes and client libraries by removing outdated information, updating node versions, and enhancing tutorials. It specifically addresses the removal of non-functional community RPC endpoints from the mainnet guide and provides a significantly improved Go client tutorial focused on transaction submission. The changes aim to ensure the documentation is accurate, up-to-date, and more helpful for developers interacting with Celestia networks.

Highlights

  • Documentation Updates: Removed outdated references to 'Mammoth testnet' and 'Full node' across various documentation files, streamlining content to focus on current node types (bridge and light nodes).
  • Community RPC Endpoint Pruning: Removed 10 unreachable community consensus RPC endpoint providers from the mainnet documentation, ensuring that only active and verified endpoints are listed.
  • Node Version Updates: Updated the latest application and node versions for Arabica devnet, Mainnet, and Mocha testnet in their respective constant files.
  • Go Client Tutorial Revamp: Completely rewrote the Go client tutorial to provide a more comprehensive guide for transaction client usage, including environment variable setup, new code examples, and updated dependency management.
  • Transaction Submission Strategies: Introduced a new section detailing various transaction submission strategies (default, synchronous, parallel) in the 'submit-data' guide, offering more advanced control over blob submission.
  • Dependency Updates: Updated numerous JavaScript package dependencies in package.json, package-lock.json, and yarn.lock to their latest versions, including v-tooltip, vue3-clipboard, and various @babel, @vue, and @esbuild related packages.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • .vitepress/config.ts
    • Removed 'Mammoth testnet' and 'Full node' from sidebar navigation.
    • Updated 'Celestia clients' to 'Celestia transaction (tx) clients' and 'Golang client guide' to 'Golang tx client guide'.
  • .vitepress/constants/arabica_versions.js
    • Updated 'app-latest-tag' to 'v6.2.2-arabica' and 'node-latest-tag' to 'v0.28.2-arabica', along with their corresponding SHAs.
  • .vitepress/constants/mainnet_versions.js
    • Updated 'app-latest-tag' to 'v6.2.4' and 'node-latest-tag' to 'v0.28.2', along with their corresponding SHAs.
  • .vitepress/constants/mocha_versions.js
    • Updated 'app-latest-tag' to 'v6.2.2-mocha' and 'node-latest-tag' to 'v0.28.2-mocha', along with their corresponding SHAs.
  • how-to-guides/celestia-node-store-structure.md
    • Clarified that the '/blocks' directory is present in datastores for bridge nodes, removing mention of 'full nodes'.
  • how-to-guides/celestia-node-troubleshooting.md
    • Removed 'full' from the ordered list of node types.
    • Updated example commands and descriptions to use 'bridge' instead of 'full' node types.
  • how-to-guides/celestia-node-trusted-hash.md
    • Added a note specifying 'no 0x prefix' for the 'SyncFromHash' configuration.
  • how-to-guides/celestia-node.md
    • Updated the curl script URL for installing Celestia node to use raw.githubusercontent.com.
  • how-to-guides/client/go.md
    • Rewrote the entire Go client tutorial to focus on transaction client usage, including environment variable setup, new code examples, and updated dependency management.
  • how-to-guides/client/overview.md
    • Updated titles and descriptions to refer to 'Celestia transaction (tx) clients'.
  • how-to-guides/config-toml.md
    • Removed the configuration file path reference for full DA nodes.
  • how-to-guides/decide-node.md
    • Removed references to 'full DA node' from the node decision guide.
  • how-to-guides/mainnet.md
    • Removed 10 community consensus endpoint providers that are no longer reachable.
    • Updated the WebSocket endpoint for Numia.
  • how-to-guides/mocha-testnet.md
    • Removed all references to 'Full storage node' and 'full node endpoints'.
  • how-to-guides/nodes-overview.md
    • Removed 'Full storage node' from the list of data availability node types and from the resource tables.
  • how-to-guides/quick-start.md
    • Updated the curl script URL for node installation.
    • Added a clarification about 'no 0x prefix' for the trusted hash.
    • Corrected a grammatical error in the text.
  • how-to-guides/submit-data.md
    • Replaced the section on 'Submitting multiple transactions in one block from the same account' with a detailed explanation of 'Transaction submission strategies' (default, synchronous, and parallel modes).
  • how-to-guides/systemd.md
    • Removed the entire section detailing systemd configuration for Celestia full storage nodes.
  • how-to-guides/validator-node.md
    • Added a new troubleshooting section for the 'App cannot be started without CometBFT when using the multiplexer' error.
  • learn/how-celestia-works/data-availability-faq.md
    • Replaced 'full node' with 'bridge node' in explanations regarding block reconstruction and fraud proofs.
  • learn/how-celestia-works/data-availability-layer.md
    • Updated terminology from 'full nodes' to 'bridge nodes' in descriptions of data share queries and block recovery.
  • learn/how-celestia-works/transaction-lifecycle.md
    • Replaced 'full node' with 'bridge node' in the description of the soundness property within the transaction lifecycle.
  • package-lock.json
    • Updated v-tooltip from ^2.1.3 to ^4.0.0-beta.17.
    • Updated vue-clipboard2 to vue3-clipboard ^1.0.0.
    • Updated various @babel, @jridgewell, @vue related packages, postcss, source-map, typescript, clipboard, commander, debug, execa, focus-trap, inherits, JSONStream, micromatch, ms, minimatch, postcss, readable-stream, resolve-from, semver, string_decoder, string-width, ts-node, typescript, vite, vue, vue-resize, vue3-clipboard versions and their integrity hashes.
    • Removed popper.js and vitepress/node_modules related entries.
  • package.json
    • Updated v-tooltip from ^2.1.3 to ^4.0.0-beta.17.
    • Updated vue-clipboard2 to vue3-clipboard ^1.0.0.
  • public/celestia-node.sh
    • Simplified the read -p command for user input.
    • Removed a trailing newline character at the end of the file.
  • tutorials/celestia-node-key.md
    • Removed all references and examples related to 'full' node type for the cel-key utility.
  • tutorials/golang-client-tutorial.md
    • Updated the title of the Golang client tutorial.
  • yarn.lock
    • Updated various @algolia, @babel, @esbuild, @jridgewell, @nodelib, @popperjs, @types, @typescript-eslint, @vitejs, @vue related packages, algoliasearch, ansi-styles, chalk, clipboard, commander, conventional-commits-parser, cosmiconfig, debug, execa, focus-trap, fsevents, inherits, JSONStream, magic-string, micromatch, ms, minimatch, postcss, readable-stream, resolve-from, resolve-global, search-insights, semver, split2, string_decoder, string-width, ts-node, typescript, vite, vue, vue-resize, vue3-clipboard versions and their integrity hashes.
    • Removed JSONStream and popper.js entries.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/preview.yml
Activity
  • The pull request was authored by rootulp.
  • The author provided a detailed summary of the changes in the pull request description.
  • A test plan was included, verifying the functionality of remaining endpoints and the correct rendering of the mainnet-beta page.
  • The pull request addresses and closes issue Update the RPC endpoints #2428.
  • The description indicates that the pull request was generated with Claude Code.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request primarily focuses on updating and clarifying documentation related to Celestia nodes and clients. Key changes include the deprecation and removal of references to 'Mammoth testnet' and 'Full nodes' across various guides, including sidebar navigation, node store structure, troubleshooting, config files, and node overviews. The Go client tutorial (how-to-guides/client/go.md) received a significant rewrite, changing its title to 'Celestia Go transaction client tutorial' and updating the example code to use environment variables for configuration, support read-only and full client modes, and include detailed instructions for running and understanding the code. This rewrite also updates Go module dependencies to newer versions. Additionally, the submit-data.md guide was substantially updated to introduce new transaction submission strategies, including synchronous and parallel modes using TxWorkerAccounts, and clarifies blob retrieval methods. Version numbers for Arabica, Mainnet, and Mocha networks were updated, and the celestia-node.sh script's curl source URL was changed. Minor corrections were made to trusted hash instructions and a typo in the quick start guide. Dependency updates in package.json, package-lock.json, and yarn.lock reflect these changes, including upgrading v-tooltip and vue-clipboard2 to vue3-clipboard. A review comment suggested improving the balance check in the Go client example by using balance.IsZero() instead of comparing string representations for robustness.

Comment thread how-to-guides/client/go.md Outdated
Comment on lines +134 to +135
balanceStr := balance.String()
if balanceStr == "0utia" || balanceStr == "0 utia" {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

Checking the balance by comparing its string representation is brittle. The format of balance.String() could change in future SDK versions, which would break this logic. A more robust approach is to use the IsZero() method provided by the Coin type.

Suggested change
balanceStr := balance.String()
if balanceStr == "0utia" || balanceStr == "0 utia" {
if balance.IsZero() {

@rootulp rootulp self-assigned this Feb 26, 2026
@rootulp rootulp marked this pull request as draft February 26, 2026 22:07
@rootulp rootulp changed the title docs: remove down community RPC endpoints from mainnet docs: remove down community endpoints from mainnet and Mocha Feb 26, 2026
rootulp and others added 2 commits February 26, 2026 15:06
Remove 10 community consensus endpoint providers that are no longer
reachable (returning 502, 403, or timing out): 0xcryptovestor, Brightly
Stake, Chainode, Cumulo, Grove, Lava, Mzonder, NodeStake, Stakeflow,
and Trusted Point. Integrate CitizenWeb3 into the table alphabetically.

Closes celestiaorg#2428

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Remove endpoints from providers that are completely unreachable:
- BrightlyStake (TLS cert mismatch, 404)
- Trusted Point (connection refused)
- Stakeflow (TLS handshake failure)
- Cumulo archive (connection refused)
- Mzonder (DNS resolution failure)
- Grove (DNS resolution failure)
- Lava (403 Forbidden on all endpoints)
- celestia-mocha.com API (TLS cert mismatch, 404)

Remove the Community JSON-RPC Endpoints and Community Tendermint RPC
Endpoints sections entirely since all entries (Lava, Grove) were down.

Keep cumulo.me gRPC (API confirmed working, gRPC likely functional).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@rootulp rootulp force-pushed the rootulp/remove-down-mainnet-endpoints branch from 9078e7e to c8eca52 Compare February 26, 2026 23:06
@rootulp rootulp marked this pull request as ready for review February 26, 2026 23:11
@rootulp rootulp enabled auto-merge February 26, 2026 23:11
Copy link
Copy Markdown
Member

@jcstein jcstein left a comment

Choose a reason for hiding this comment

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

LGTM - preview only failing because this is from a fork.

@rootulp rootulp merged commit a868bbc into celestiaorg:main Feb 26, 2026
3 of 5 checks passed
@rootulp rootulp deleted the rootulp/remove-down-mainnet-endpoints branch February 26, 2026 23:17
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.

Update the RPC endpoints

2 participants