Skip to content
Hero background

Migrate from Google Blockchain Node Engine

Switch over to Alchemy before December 15th. One URL swap. Reliable, low-latency, cost-efficient RPC.

Alchemy RPC
  • Fidelity
  • Robinhood
  • Visa
  • Stripe
  • Circle
  • Coinbase
  • Fidelity
  • Robinhood
  • Visa
  • Stripe
  • Circle
  • Coinbase

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

Frequently asked questions

  • December 15, 2026. Google's shutdown announcement says Blockchain Node Engine nodes and Blockchain RPC endpoints are deleted that day, and workloads still pointing at them fail. New nodes and new Blockchain RPC endpoints have been disabled since June 15, 2026. Existing ones keep running until the shutdown date.

  • No. Google's migration docs recommend QuickNode. Move to Alchemy instead. We take the same JSON-RPC traffic. Our comparison shows Alchemy about 3.5x faster on average latency across Ethereum, Optimism, and Arbitrum, with coverage across 100+ chains. We also have industry-leading proven reliability.

  • Alchemy is about 3.5x faster than QuickNode on average latency in our comparison, across Ethereum, Optimism, and Arbitrum. We also have industry-leading proven reliability: 99.99% uptime through the largest liquidation in crypto. Cash App uses our Node APIs and Webhooks so stablecoin balances stay verifiable against chain state.

  • The endpoint URL. HTTP becomes https://{network}.g.alchemy.com/v2/{API_KEY}. WebSockets use the wss:// form of that host. Methods and payloads stay the same. If a chain mapping is unclear, check it on our chain directory before you cut over. This guide covers what the swap includes and what to audit first.

  • Yes, once Alchemy MCP is connected. The prompt on this page tells the agent to create or select an app, find Google Blockchain Node Engine URLs in the repo, and draft the replacement. You review the diff before any file is written. The agent does not commit. The Alchemy CLI covers the same account setup from a terminal.

  • Replace the WebSocket host with wss://{network}.g.alchemy.com/v2/{API_KEY}. Subscription methods stay the same. Smart Websockets covers that connection, including new heads, logs, and pending transactions.

  • When a shared endpoint is the wrong fit: isolation, a region you choose, or custom node config. Most migrations start on the shared RPC endpoint. Dedicated Clusters are the path when you need that from the start.

Background gradient

Get an endpoint before December 15.