rpc_modules - Arc RPC Method

Returns the enabled JSON-RPC namespaces exposed by the connected Arc endpoint together with their version strings.

Non-standard method. rpc_modules is a client-introspection RPC that is commonly available on Geth-compatible stacks, but it is not part of the core Ethereum Execution API method set. Availability varies by client and operator policy.

Why Arc? Build on Circle's stablecoin-native Layer 1 where USDC is the gas token and BFT consensus gives sub-second deterministic finality with USDC as the native gas token, sub-second irreversible finality, an EWMA-smoothed fee market with a 20 Gwei floor, and EIP-7708 Transfer logs for native value movement.

When to Use This Method

rpc_modules is useful for payment platforms, stablecoin issuers, exchange and treasury teams, and Solidity developers building on Arc:

• Capability Discovery - Detect whether namespaces like debug, trace, txpool, or erigon are exposed before attempting those calls
• Client Diagnostics - Verify what the serving node has enabled when debugging environment-specific issues
• Infrastructure Audits - Compare public and private endpoints to confirm which RPC surfaces are intentionally exposed
• Runtime Feature Gating - Adjust tooling behavior dynamically based on the actual namespaces available on a node

Best Practices

• Call at startup to determine which features are available on a node
• Module availability varies by node client and provider configuration
• Use to gate feature access in applications before attempting unsupported calls
• This is a non-standard method; some endpoints may not expose it

Code Examples

Error Handling

Related Methods

• web3_clientVersion - Inspect the client software version string
• debug_traceTransaction - Debug namespace example
• trace_transaction - Trace namespace example