QuickNode Upgrade and Migration

Overview

Treat client, endpoint, token, chain API, and event-pipeline changes as contract migrations. Preserve a parallel read path or replay boundary until the target proves identity, correctness, capacity, and recovery.

Prerequisites

• Current and target SDK, endpoint, chain/network, and product inventory
• Compatibility tests and representative traffic
• Cutover owner, rollback window, and data-reconciliation plan

Authentication

Keep target credentials separate from the current path during the dual run. Endpoint tokens authenticate RPC through a protected URL or x-token header; Admin API inspection uses a distinct x-api-key, while qn uses its authenticated account session. Redact all three from matrices and receipts.

Instructions

Step 1: Build the change matrix