Namespaces & Endpoints
Configure your Web3 provider or SDK using the following namespace routes. Each path forwards JSON-RPC queries directly to a high-speed, cached RPC provider.
| Chain | Gateway Endpoint |
|---|---|
| Ethereum Mainnet | https://eth.flashrouter.io/v1/ethereum |
| Base Mainnet | https://eth.flashrouter.io/v1/base |
| Base Sepolia Testnet | https://eth.flashrouter.io/v1/base-sepolia |
| Arbitrum One | https://eth.flashrouter.io/v1/arbitrum |
| Optimism Mainnet | https://eth.flashrouter.io/v1/optimism |
| Polygon PoS | https://eth.flashrouter.io/v1/polygon |
Safety & Compliance (OFAC Filtering)
FlashRouter is dedicated to compliant, secure on-chain operations. To ensure the integrity of the gateway:
- Every transaction payload submitted via the gateway is parsed and screened at the edge.
- Requests containing sanctioned addresses (e.g. Tornado Cash) or flagged exploit contracts will be rejected with an RFC-compliant JSON-RPC compliance error:
code: -32600(Invalid Request) and status403 Forbidden. - Counterfeit token contracts are prohibited and flagged directly in the router system.
Quick Start Code Example
Below is an example of instantiating a client using viem pointing directly to the Sovereign RPC Gateway:
TypeScript / Viem integration
import { createPublicClient, http } from "viem";
import { base } from "viem/chains";
const client = createPublicClient({
chain: base,
transport: http("https://eth.flashrouter.io/v1/base")
});
const blockNumber = await client.getBlockNumber();
console.log(`Current Base block: ${blockNumber}`);