Migrate from Google Blockchain Node Engine
Switch over to Alchemy before December 15th. One URL swap. Reliable, low-latency, cost-efficient RPC.
We make it easy
Simply swap out your RPC URL with a single line of code.
javascript
Copied
const rpcUrl = "https://eth-mainnet.g.alchemy.com/v2/YOUR_API_KEY";Chains we support
See 100+ chainsAbstract
ADI
Alpen
Anime
ApeChain
Aptos
Arbitrum
Arc
Astar
Avalanche
Base
Berachain
Bitcoin
Bitcoin Cash
BNB Smart Chain
BOB
Boba
CelestiaBridge
Celo
Citrea
Cronos
CrossFi
DATA Network
Dogecoin
Elysium
Ethereum
Flow EVM
Frax
Gensyn
Giwa
Gnosis
Humanity
Hyperliquid
Injective
Ink
Jovay
Kaia
Katana
Lens
Linea
Litecoin
Mantle
MegaETH
Metis
Mode
Monad
Mythos
OP Mainnet
opBNB
Pharos
Plasma
Polygon PoS
Rise
Robinhood Chain
Ronin
Rootstock
Scroll
Sei
Settlus
Shape
Solana
Soneium
Sonic
Stable
Starknet
Stellar
Sui
Superseed
Tempo
Tron
Unichain
World Chain
World Mobile Chain
X Layer
ZetaChain
ZKsync
Zora
Or let your coding agent do the work
Paste this into a client connected to Alchemy MCP and let your agent do the heavy lifting.
Works with your tools
Claude Code
Cursor
Codex
VS Code
Move this project off Google Cloud Blockchain Node Engine and Blockchain RPC before the December 15, 2026 shutdown.
Use the Alchemy MCP server (https://mcp.alchemy.com/mcp). If its tools aren't available, guide me through client setup and sign-in, including a restart if needed.
Plan first. Don't change files or Alchemy settings until I approve. Never print credentials. Don't commit or deploy.
1. Find Google blockchain endpoints in code, config, .env, and deployment files. Search blockchainnodeengine.com and blockchain.googleapis.com, and trace RPC settings supplied elsewhere. List each location, chain or Solana cluster, transport, and methods, with credentials redacted. Ask about unknown mappings.
2. Flag anything beyond a URL swap for review, including: Holesky/Goerli (Hoodi/Sepolia changes the chain), Beacon (separate hosts and REST paths), node-management/metrics APIs, Solana blockSubscribe (streaming endpoint), debug_*/trace_* (paid plans), and eth_getLogs ranges (Free-plan limits). Leave unresolved integrations unchanged.
3. Call list_apps and list_chains. Propose an existing app or a new one with all required networks enabled. For existing apps, call get_app and preserve current networks and restrictions. update_allowlist replaces the whole list: merge networks using Admin IDs such as ETH_MAINNET. create_app also accepts slugs such as eth-mainnet.
4. For standard RPC, use https://{slug}.g.alchemy.com/v2/<key> or wss://{slug}.g.alchemy.com/v2/<key>, using the RPC slug from list_chains. Handle approved exceptions separately. Load ALCHEMY_API_KEY using this project's secret-loading conventions; don't embed placeholder syntax literally. If the key would reach browser code, propose a server-side proxy or a separate restricted key.
5. Remove Google key query parameters and X-goog-api-key headers only from migrated requests, and old Google environment variables only when unused elsewhere.
6. Show the proposed redacted diff, Alchemy app changes, and deployment-secret updates. After approval, apply the changes and provide the app's dashboard link so I can set the real key privately; MCP tools mask it. Once configured, test representative read-only calls through the migrated app, including historical/log queries it uses, and verify each network. Test WebSocket event delivery after reconnect and resubscription where used. Report failures and untested paths; don't call the migration complete while required checks remain.Helpful resources
Overview
Alchemy vs. QuickNode
About 3.5x faster than QuickNode on average latency, from a dated comparison.
Blog
Always up through the biggest liquidation
99.99% uptime through the largest liquidation in crypto. Industry-leading proven reliability.
Case study
How Cash App moves stablecoin money
Cash App uses our Node APIs and Webhooks so every balance stays verifiable against chain state.
Guide
Migrate between RPC providers with zero downtime
What a URL swap covers, what to audit first, and how to cut over without downtime.
Frequently asked questions
