跳至內容
Hero background

從 Google Blockchain Node Engine 遷移

12 月 15 日之前,切換到 Alchemy。 一次 URL 更換。可靠、低延遲、成本高效的 RPC。

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

或者讓程式代理來完成

貼到已連接 Alchemy MCP 的用戶端,把重活交給程式代理。

相容於你使用的工具

  • 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.

實用資源

常見問題

  • 2026 年 12 月 15 日。Google 的關閉公告說明,當天會刪除 Blockchain Node Engine 節點和 Blockchain RPC 端點,仍指向它們的工作負載會失敗。自 2026 年 6 月 15 日起,已無法新建節點和新的 Blockchain RPC 端點。現有的會運行到關閉日。

  • 不必。Google 的遷移文件推薦 QuickNode。改遷到 Alchemy。我們接收同樣的 JSON-RPC 流量。我們的比較顯示,在 Ethereum、Optimism 和 Arbitrum 上,平均延遲大約比 QuickNode 快 3.5 倍,並覆蓋 100+ 條鏈。我們還有業界領先、經過驗證的可靠性。

  • 在 我們的比較裡,Ethereum、Optimism 和 Arbitrum 上的平均延遲大約比 QuickNode 快 3.5 倍。我們還有業界領先、經過驗證的可靠性:加密貨幣史上最大清算期間仍保持 99.99% 的正常運作時間。Cash App 使用我們的 Node APIs 和 Webhooks,讓穩定幣餘額能對照鏈上狀態持續核驗。

  • 端點 URL。HTTP 變為 https://{network}.g.alchemy.com/v2/{API_KEY}。WebSockets 使用該主機的 wss:// 形式。方法和載荷保持不變。如果某條鏈的對應關係不清楚,切換前先在鏈目錄核對。這份指南說明這次更換包含什麼,以及先稽核什麼。

  • 可以,先連接 Alchemy MCP。本頁的提示詞會讓代理建立或選擇應用程式,在儲存庫裡找到 Google Blockchain Node Engine 的 URL,並起草替換。任何檔案寫入之前,你先審閱 diff。代理不會提交。Alchemy CLI 在終端機裡完成同樣的帳戶設定。

  • 把 WebSocket 主機換成 wss://{network}.g.alchemy.com/v2/{API_KEY}。訂閱方法保持不變。Smart Websockets 介紹這條連線,包括 new heads、logs 和待處理交易。

  • 共享端點不合適的時候:需要隔離、自選區域,或自訂節點設定。大多數遷移從共享 RPC 端點開始。如果一開始就需要這些,走 Dedicated Clusters。

Background gradient

在 12 月 15 日之前拿到端點。