bug(base-config): Base Mainnet RPC intermittent timeout during high gas price periods

**Bug Description**
When testing dApp integration on Base Mainnet during periods of high network activity (gas prices >0.001 ETH), RPC calls to `eth_estimateGas` and `eth_sendTransaction` are experiencing intermittent timeouts. This appears to be specific to Base's configuration as the same code works reliably on Ethereum mainnet and other L2s.

**Steps to Reproduce**
1. Deploy a smart contract on Base Mainnet
2. Configure web3 provider to use Base RPC endpoint: `https://mainnet.base.org`
3. During high gas price periods (>0.001 ETH), attempt multiple `eth_estimateGas` calls
4. Observe timeout errors occurring approximately 30% of the time
5. Same issue occurs with `eth_sendTransaction` calls

**Expected behavior**
RPC calls should complete successfully within reasonable timeout periods (5-10 seconds), similar to behavior on Ethereum mainnet.

**Actual behavior**
- `eth_estimateGas` calls timeout after 30+ seconds
- Error: "Request timeout after 30000ms"
- Issue is intermittent but reproducible during high gas periods
- Affects Base Mainnet specifically - Base Sepolia testnet works fine

**Environment**
- Network: Base Mainnet (Chain ID: 8453)
- RPC Endpoint: https://mainnet.base.org
- Gas Price Range: >0.001 ETH (when issue occurs)
- Testing Framework: Hardhat with ethers.js
- Node Version: 18.17.0

**Additional Context**
This issue is impacting production dApp deployment on Base. The timeout behavior suggests potential sequencer load balancing issues during high throughput periods. Base developers would benefit from improved RPC reliability during network congestion.

Start by reproducing the intermittent failures against https://mainnet.base.org during the stated high-gas conditions, focusing on eth_estimateGas and eth_sendTransaction with Hardhat, ethers.js, and Node 18.17.0. Compare Base Mainnet with Base Sepolia and Ethereum mainnet, then use the results to determine whether the issue is in the RPC service or sequencer load balancing; done means a confirmed cause and reliable calls within the stated timeout.

Written by the indexing model from the issue text.