How to Migrate from Infura to GetBlock — Step-by-Step

Switch from Infura to GetBlock in minutes. Migration guide covering endpoint URLs, SDK changes, feature mapping, and why teams are making the switch.

Infura was the original Ethereum RPC provider, but by 2026, the landscape had changed. If you're looking for more chain support, better pricing, or geographic endpoint control, migrating from Infura to GetBlock is straightforward. This migration only takes 5–10 minutes.

Why Teams Switch from Infura To GetBlock

Reason	Infura	GetBlock
Chain coverage	~15 networks	130+ blockchains
Free tier archive data	Paid plans only	All plans including Free
Region selection	No explicit choice	Frankfurt, New York, Singapore
Dedicated nodes	Custom pricing	From $1,000/mo, transparent
Solana support	Limited	Full: RPC + gRPC + StreamFirst + LandFirst
Non-EVM chains	Minimal (ETH-focused)	Bitcoin, Litecoin, Dogecoin, TRON, TON, etc.
Pricing clarity	Credit-based (varies by method)	CU-based with clear tiers

Infura is excellent for Ethereum-first projects, but if your stack is growing beyond Ethereum, GetBlock's 100+ chain coverage eliminates the need for multiple providers.

How to Switch From Infura To GetBlock

1

Create Your GetBlock Endpoint

1. Sign up at account.getblock.io

2. Go to Shared Nodes → Create New Endpoint

3. Select your blockchain, network, and API interface

4. Choose your region (closest to your servers)

5. Copy the endpoint URL

Infura format:

https://mainnet.infura.io/v3/YOUR_PROJECT_ID

GetBlock format:

https://go.getblock.io/YOUR_ACCESS_TOKEN/

2

Update Your Code

ethers.js

// Before (Infura)
const provider = new JsonRpcProvider(
  "https://mainnet.infura.io/v3/YOUR_PROJECT_ID"
);

// After (GetBlock)
const provider = new JsonRpcProvider(
  "https://go.getblock.io/YOUR_GETBLOCK_TOKEN/"
);

Viem

web3.py

Hardhat

Foundry

Websocket

3

Environment Variables (recommended)

Best practice: use environment variables to switch providers without code changes.

# .env
RPC_URL=https://go.getblock.io/YOUR_GETBLOCK_TOKEN/

const provider = new JsonRpcProvider(process.env.RPC_URL);

4

Verify Everything Works

Run a quick check:

curl -X POST $RPC_URL \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

If you get a valid response with a block number, you're good.

Multi-Chain Migration

If you're using Infura for multiple chains, you'll need a separate GetBlock endpoint for each chain. Create them all in one dashboard session:

# .env — Before (Infura)
ETH_RPC=https://mainnet.infura.io/v3/PROJECT_ID
POLYGON_RPC=https://polygon-mainnet.infura.io/v3/PROJECT_ID

# .env — After (GetBlock)
ETH_RPC=https://go.getblock.io/ETH_TOKEN/
POLYGON_RPC=https://go.getblock.io/POLYGON_TOKEN/
# Plus 90+ more chains you can now access:
SOLANA_RPC=https://go.getblock.io/SOL_TOKEN/
BSC_RPC=https://go.getblock.io/BSC_TOKEN/
TON_RPC=https://go.getblock.io/TON_TOKEN/

Feature Mapping: Infura → GetBlock

Infura Feature	GetBlock Equivalent
JSON-RPC	✅ Full JSON-RPC support
WebSocket	✅ WebSocket support
Archive data	✅ All plans (Infura: paid only)
IPFS	❌ Not available (use Pinata, nft.storage)
Gas API	✅ eth_gasPrice, eth_feeHistory methods
Ethereum Beacon API	✅ Available
MetaMask default	Can be configured as custom RPC
~15 chains	✅ 130+ chains
Dedicated Nodes	✅ From $1,000/mo

What You Gain

• 85+ additional blockchains — Bitcoin, Solana, BSC, TON, TRON, and more

• Archive data at no extra cost — even on the free plan

• Regional endpoints — control where your requests are processed

• Dedicated Nodes with clear pricing — unlimited requests from $1,000/mo

• Advanced Solana and BSC tooling — HFT infrastructure, private mempool

What You'll Need Alternatives For

• Infura IPFS → Pinata, nft.storage, or Fleek

• MetaMask default integration → Add GetBlock as custom RPC in MetaMask settings

Ready to switch? and have your new endpoints running in under 5 minutes.