quicknode-reference-architecture
/quicknode-reference-architecture
Analyze and design a QuickNode production boundary that separates control-plane API keys, data-plane endpoint tokens, chain reads and writes, event ingestion, durable state, and observability. Use when multiple services or QuickNode products need clear ownership and failure isolation. Trigger with: "analyze QuickNode architecture", "design QuickNode infrastructure", "audit QuickNode trust boundaries".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Analyze and design a QuickNode production boundary that separates control-plane API keys, data-plane endpoint tokens, chain reads and writes, event ingestion, durable state, and observability. Use when multiple services or QuickNode products need clear ownership and failure isolation. Trigger with: "analyze QuickNode architecture", "design QuickNode infrastructure", "audit QuickNode trust boundaries".
Triggers from the description
Arguments
/quicknode-reference-architecture [systems-and-chain-workloads]
Original author description
Analyze and design a QuickNode production boundary that separates control-plane API keys, data-plane endpoint tokens, chain reads and writes, event ingestion, durable state, and observability. Use when multiple services or QuickNode products need clear ownership and failure isolation. Trigger with: "analyze QuickNode architecture", "design QuickNode infrastructure", "audit QuickNode trust boundaries".
How it works
- Overview
- Prerequisites
- Instructions
- Tool Discipline
- Output
- Examples
- Error Handling
- Resources
SKILL.md preview
--- name: quicknode-reference-architecture description: 'Analyze and design a QuickNode production boundary that separates control-plane API keys, data-plane endpoint tokens, chain reads and writes, event ingestion, durable state, and observability. Use when multiple services or QuickNode products need clear ownership and failure isolation. Trigger with: "analyze QuickNode architecture", "design QuickNode infrastructure", "audit QuickNode trust boundaries".' allowed-tools: Read, Grep, Write, Edit version: 2.0.0 argument-hint: '[systems-and-chain-workloads]' model: inherit effort: high license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io> tags: - saas - quicknode - architecture - blockchain - governance compatibility: 'Product availability, destination counts, and endpoint capabilities depend on chain and plan' --- # QuickNode Production Reference Architecture ## Overview Separate provisioning and account governance from chain traffic, and separate synchronous reads/writes from asynchronous event ingestion. Give every credential, endpoint, cursor, queue, and recovery path one owner. ## Prerequisites - Service inventory and trust boundaries - Chain/network, method, history, write, and event requirements - SLO, recovery, compliance, and cost constraints ## Instructions ### Step 1: Map control and data planes Use Read and Grep to identify Admin API, unified SDK, `qn`, RPC/WSS endpoints, Streams, Webhooks, SQL Explorer, and KV Store usage. Mark credentials and mutation authority. ### Step 2: Isolate credentials Use separate API keys for control-plane automation and endpoint tokens for data-plane RPC. Separate applications and environments with multiple tokens; keep signing keys outside QuickNode clients. ### Step 3: Split synchronous workloads Route bounded reads through chain-specific adapters. Put transaction intent, signing, broadcast identity, confirmation, and reorg reconciliation behind a dedicated write service. ### Step 4: Build asynchronous ingestion Terminate Streams or Webhooks at an authenticated receiver, acknowledge after durable enqueue, and process idempotently. Persist a replay cursor and send large historical pipelines to an appropriate durable destination. ### Step 5: Define data capability Use Write or Edit to record chain, network, API family, add-ons, archive/pruning semantics, pagination, and block consistency. Do not assume feature parity across chains. ### Step 6: Close observability and recovery Correlate application requests with endpoint metrics and sanitized request IDs. Define endpoint/token cutover, chain-provider degradation, event replay, transaction reconciliation, and budget alerts. ## Tool Discipline Use Read and Grep for topology discovery and Write/Edit for architecture records, interfaces, and tests. This design workflow performs no account, endpoint, Stream, or production mutation. ## Output - Trust-boundary and credential map - Synchronous read/write interfaces - Durable event-ingestion and replay path - Observability, cost, and recovery contracts ## Examples An API serves cached finalized reads, a signer service owns transaction state, and a Stream receiver writes authenticated batches to a queue. Admin automation has no signer or endpoint token. ## Error Handling | Failure | Response | | --- | --- | | One key spans control and data planes | Split identity and rotate through overlap | | Event receiver performs business work inline | Insert a durable queue before acknowledgement | | Chain capability is assumed | Bind the interface to a verified chain/network contract | | Provider timeout can duplicate a write | Persist broadcast identity and reconcile before retry | ## Resources - [Architecture evidence and source notes](references/official-docs.md) - [QuickNode APIs](https://www.quicknode.com/docs/build-with-ai/quicknode-apis) - [Streams destinations](https://www.quicknode.com/docs/streams/destinations)
Files in this package (2)
- SKILL.md 4 KB
- references/official-docs.md 1 KB
Versions
The database has no other skills named quicknode-reference-architecture.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version c1d0332762e2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100quicknode-upgrade-migration
Migrate a QuickNode SDK, endpoint, chain API, token, or event product with inventory, compatibility tests, canary traffic, and rollback. Use when adopting the unified SDK, responding to a chain deprecation, or rotating infrastructure without losing writes or events. Trigger… - 100quicknode-deploy-integration
Deploy a QuickNode integration with environment-scoped endpoints, preflight reads, staged traffic, observability, and reversible credential cutover. Use when releasing a new RPC endpoint, SDK client, Stream, or Webhook consumer. Trigger with: "deploy QuickNode", "roll out a… - 100quicknode-webhooks
Receive and verify Quicknode Streams and Quicknode Webhooks deliveries. Use when setting up a Quicknode webhook handler, debugging X-QN-Signature verification, or processing block, transaction and log data streamed from a Quicknode Stream or Webhook. - 100quicknode
QuickNode is hosted RPC (HTTP + WebSocket) plus Streams, Webhooks and a testnet faucet for World Chain, Unichain, Hedera, Arc, 0G and 80+ other chains. Use this skill when you need a QuickNode endpoint URL, viem/ethers on QuickNode, eth_subscribe/WebSockets, Streams or Webhooks… - 91quicknode-skill
Quicknode blockchain infrastructure for 80+ chains: Core RPC API, Streams, Webhooks, Blazar WSS, Solana gRPC, HyperCore gRPC, SQL Explorer, Metaplex DAS API, Blockbook, Ordinals & Runes API, Swap API, x402, MPP, Agent Subscriptions, CLI, and MCP. Use for any Quicknode product,… - 91quicknode-skill
Quicknode blockchain infrastructure for 80+ chains: Core RPC API, Streams, Webhooks, Blazar WSS, Solana gRPC, HyperCore gRPC, SQL Explorer, Metaplex DAS API, Blockbook, Ordinals & Runes API, Swap API, x402, MPP, Agent Subscriptions, CLI, and MCP. Use for any Quicknode product,…