quicknode-security-basics
/quicknode-security-basics
Harden QuickNode endpoints with server-side token handling, separate credentials, least-privilege account roles, and plan-appropriate security filters. Use when reviewing exposure, isolating applications, or responding to a leaked endpoint. Trigger with: "secure QuickNode", "harden a QuickNode endpoint", "rotate a leaked QuickNode token".
- 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
Harden QuickNode endpoints with server-side token handling, separate credentials, least-privilege account roles, and plan-appropriate security filters. Use when reviewing exposure, isolating applications, or responding to a leaked endpoint. Trigger with: "secure QuickNode", "harden a QuickNode endpoint", "rotate a leaked QuickNode token".
Triggers from the description
Arguments
/quicknode-security-basics [endpoint-and-threat-model]
Original author description
Harden QuickNode endpoints with server-side token handling, separate credentials, least-privilege account roles, and plan-appropriate security filters. Use when reviewing exposure, isolating applications, or responding to a leaked endpoint. Trigger with: "secure QuickNode", "harden a QuickNode endpoint", "rotate a leaked QuickNode token".
How it works
- Overview
- Prerequisites
- Instructions
- Tool Discipline
- Output
- Examples
- Error Handling
- Resources
SKILL.md preview
--- name: quicknode-security-basics description: 'Harden QuickNode endpoints with server-side token handling, separate credentials, least-privilege account roles, and plan-appropriate security filters. Use when reviewing exposure, isolating applications, or responding to a leaked endpoint. Trigger with: "secure QuickNode", "harden a QuickNode endpoint", "rotate a leaked QuickNode token".' allowed-tools: Read, Grep, Write, Edit, Bash(qn:*) version: 2.0.0 argument-hint: '[endpoint-and-threat-model]' model: inherit effort: high license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io> tags: - saas - quicknode - security - authentication - hardening compatibility: 'JWT, referrer allowlists, domain masking, and advanced rate controls can be plan-specific' --- # QuickNode Endpoint Hardening ## Overview Protect endpoint tokens as credentials, isolate consumers with multiple tokens, and layer only controls that match the client threat model. A browser referrer rule is not a substitute for keeping privileged RPC or account keys on a server. ## Prerequisites - Endpoint inventory with owners, applications, and environments - Current plan and available endpoint-security controls - A threat model covering browser, server, CI, and operator access ## Instructions ### Step 1: Find exposure Use Read and Grep for `quiknode.pro`, `x-token`, `x-api-key`, JWT configuration, logs, examples, and client bundles. Stop and rotate any live credential committed to Git or shipped to an untrusted client. ### Step 2: Separate identities Create distinct endpoint tokens for applications and environments. Keep Admin API/SDK API keys separate from chain RPC tokens. Apply least-privilege team and account roles. ### Step 3: Choose layered controls Use token authentication for every endpoint. Add JWT for short-lived server authorization when supported, referrer allowlists for browser-origin reduction, and IP or method limits for known traffic patterns. Document plan dependencies. ### Step 4: Keep privileged calls server-side Use Write or Edit to route transaction submission, archive/debug methods, and account-control calls through a trusted backend. Do not embed endpoint or API tokens in public JavaScript. ### Step 5: Inspect configuration Use Bash(qn:*) to read endpoint security state with an approved authenticated operator identity. Compare actual tokens, filters, limits, domains, and team access to the declared policy without printing secret values. ### Step 6: Exercise response Prove that an unauthorized origin, token, method, or IP is rejected as designed. Revoke one test token and confirm other isolated consumers continue. Record recovery time and escalation owner. ## Tool Discipline Use Read and Grep for exposure discovery, Write/Edit for server-side boundaries and policy, and Bash(qn:*) for read-only security inspection. Credential creation, revocation, and production filter changes require an explicit checkpoint. ## Output - Endpoint threat model and credential map - Actual-versus-declared security control comparison - Negative authorization tests - Rotation and incident-response procedure ## Examples A public dApp calls a backend that holds the endpoint token. Production and staging use separate tokens, and a method limit prevents the public route from invoking debug methods. ## Error Handling | Failure | Response | | --- | --- | | Token exposed | Revoke, replace, sanitize history and logs, then investigate use | | Referrer rule blocks valid traffic | Roll back the specific rule; do not expose the token | | `-32611` rejection | Compare method and filter policy before retrying | | Security feature unavailable | Record the plan gap and enforce the boundary in the application | ## Resources - [Security evidence and source notes](references/official-docs.md) - [Multi-token authentication](https://www.quicknode.com/guides/quicknode-products/endpoint-security/how-to-set-up-multi-token-authentication-on-quicknode) - [Method rate limits](https://www.quicknode.com/guides/quicknode-products/endpoint-security/how-to-setup-method-rate-limits)
Files in this package (2)
- SKILL.md 4 KB
- references/official-docs.md 1 KB
Versions
The database has no other skills named quicknode-security-basics.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 7439d48e209f (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-install-auth
Choose and configure the correct QuickNode credential boundary for RPC endpoints, the Admin API, the unified SDK, and the qn CLI. Use when onboarding an endpoint, separating environments, or rotating access without exposing tokens. Trigger with: "authenticate QuickNode",… - 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-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… - 100defending-kubernetes
Harden and monitor a Kubernetes cluster against the attacks that actually happen — RBAC least privilege and escalation paths, Pod Security Admission enforcement, network policy default-deny, secrets and service-account token exposure, control-plane and kubelet exposure, and… - 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,…