跳至内容
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 日之前拿到端点。