QuickNode Chain-Data Contract

Overview

Select an endpoint from required data semantics, not from a generic “Web3 RPC” label. Current state, historical block data, historical state, traces, token/NFT indexes, REST, gRPC, and WebSocket subscriptions have different availability and retention.

Prerequisites

• Chain, network, and protocol requirements
• Oldest required block, state, or epoch
• Required methods, consistency, pagination, latency, and recovery behavior

Authentication

Use an endpoint token for data-plane RPC, passed through the documented endpoint URL or x-token header. Use a separate account API key in x-api-key only for Admin API capability inspection. Never place either credential in the written data contract or its tests.

Instructions

Step 1: Inventory queries