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
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
Create Your GetBlock Endpoint
Sign up at account.getblock.io
Go to Shared Nodes → Create New Endpoint
Select your blockchain, network, and API interface
Choose your region (closest to your servers)
Copy the endpoint URL
Infura format:
https://mainnet.infura.io/v3/YOUR_PROJECT_IDGetBlock format:
https://shared.eu-central-1.getblock.io/YOUR_ACCESS_TOKEN/Update Your Code
// Before (Infura)
const provider = new JsonRpcProvider(
"https://mainnet.infura.io/v3/YOUR_PROJECT_ID"
);
// After (GetBlock)
const provider = new JsonRpcProvider(
"https://shared.eu-central-1.getblock.io/YOUR_GETBLOCK_TOKEN/"
);// Before
const client = createPublicClient({
chain: mainnet,
transport: http(
"https://mainnet.infura.io/v3/YOUR_PROJECT_ID"
);
});
// After
const client = createPublicClient({
chain: mainnet,
transport: http("https://shared.eu-central-1.getblock.io/YOUR_GETBLOCK_TOKEN/"),
});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://shared.eu-central-1.getblock.io/ETH_TOKEN/
POLYGON_RPC=https://shared.eu-central-1.getblock.io/POLYGON_TOKEN/
# Plus 90+ more chains you can now access:
SOLANA_RPC=https://shared.eu-central-1.getblock.io/SOL_TOKEN/
BSC_RPC=https://shared.eu-central-1.getblock.io/BSC_TOKEN/
TON_RPC=https://shared.eu-central-1.getblock.io/TON_TOKEN/Feature Mapping: Infura → GetBlock
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
Last updated
Was this helpful?