fix: explicit network config for Gravity Testnet RPC#14
Merged
Conversation
ethers v5 does not recognize Gravity Testnet (chain ID 7771625) and fails with NETWORK_ERROR during automatic network detection. Providing the network config explicitly skips the detection step. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
{ name: "gravity-testnet", chainId: 7671625 }to ethersJsonRpcProviderinstead of relying on auto-detectionNETWORK_ERROR: could not detect networkcrash on MCP server startup — ethers v5 doesn't recognize Gravity Testnet's chain ID (7771625)Test plan
just agent-start config/gravity.tomland verify MCP server starts without NETWORK_ERROR🤖 Generated with Claude Code