docs: remove down community endpoints from mainnet and Mocha#2433
docs: remove down community endpoints from mainnet and Mocha#2433rootulp merged 2 commits intocelestiaorg:mainfrom
Conversation
Summary of ChangesHello, 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
🧠 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
Ignored Files
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
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.
| balanceStr := balance.String() | ||
| if balanceStr == "0utia" || balanceStr == "0 utia" { |
There was a problem hiding this comment.
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.
| balanceStr := balance.String() | |
| if balanceStr == "0utia" || balanceStr == "0 utia" { | |
| if balance.IsZero() { |
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>
9078e7e to
c8eca52
Compare
jcstein
left a comment
There was a problem hiding this comment.
LGTM - preview only failing because this is from a fork.
Closes https://linear.app/celestia/issue/DA-1078/remove-down-rpc-endpoints-from-mainnet-beta-docs
Closes #2428
Summary
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
/statusand API/cosmos/base/tendermint/v1beta1/blocks/latest🤖 Generated with Claude Code