QuickNode Deployment Gate

Overview

Release configuration before traffic, prove the selected chain and product contracts, then increase exposure in stages. Keep old endpoints or tokens available through a bounded rollback window.

Prerequisites

• Release commit, target environment, endpoint and product inventory
• Secret-manager references for environment-specific credentials
• SLO, canary cohort, rollback owner, and maximum cutover window

Instructions

Step 1: Audit the release

Use Read and Grep to find endpoint variables, literal URLs, chain IDs, network names, SDK versions, write paths, Stream/Webhook destinations, and timeout/retry changes.

Step 2: Validate control-plane state