drpc-primary-sources-2026-04-25

dRPC primary-source snapshot

Fetched: 2026-04-25 UTC

1) Official homepage

Source: https://drpc.org/

Selected excerpts from the official site:

Modular RPC solutions to launch, scale, and monitor your Web3 infra

We’re not just another gateway — we’re the full stack.

4B+ requests served daily to power 4000+ dApps

Additional signals from the homepage:

• dRPC presents multiple product layers: managed multichain cloud RPC, an open-source/self-hosted stack, and custom infrastructure work for more complex teams
• The site emphasizes low latency, geo distribution, smart routing, cost transparency, and observability rather than only “fast endpoints” marketing
• Public customer quotes from Instadapp, SushiSwap, and Aerodrome support the claim that dRPC targets production applications and chains

2) Official chain directory

Source: https://drpc.org/chainlist

Selected signals from the chain directory:

• The site lists 175 networks across 107 chains at fetch time
• Entries expose chain IDs, gas tokens, and whether HTTP / WebSocket, archive, MEV, or premium access are available
• The breadth of first-party chain metadata is a useful primary source for understanding dRPC’s actual operating footprint

3) Docs surface

Source: https://docs.drpc.org/ Source: https://raw.githubusercontent.com/drpcorg/drpc-nextra/main/README.md

Selected excerpts from the docs repo:

DRPC documentation

This is DRPC documentation site…

Additional signals from the docs materials:

• dRPC maintains a dedicated docs site and public docs repository rather than only marketing pages
• The public docs codebase supports the claim that documentation is an actively maintained product surface
• Even when the rendered docs are heavy client-side pages, the repo itself is still a meaningful first-party source

4) NodeCore repository

Source: https://github.com/drpcorg/nodecore

Selected excerpts from the repo materials:

nodecore is a fault-tolerant RPC load balancer designed to work with any blockchain API.

It intelligently distributes requests across multiple providers or nodes, with a focus on optimizing performance metrics such as latency, throughput, and error rates.

Additional signals from NodeCore:

• The README documents support for EVM and Solana JSON-RPC over HTTP and WebSocket, method specs, caching, hedging, retries, scoped access controls, and flexible provider selection
• Deployment materials cover Docker, local builds, Kubernetes, and Tor hidden-service deployment, which is unusually operationally rich for an RPC vendor
• NodeCore makes dRPC look like an infrastructure/control-plane vendor with self-hosted options, not merely a hosted gateway brand

5) Dshackle and organization-level signals

Source: https://github.com/drpcorg/dshackle Source: https://github.com/drpcorg

Selected excerpts from the repo materials:

Dshackle is a Fault Tolerant Load Balancer for Blockchain API used at DRPC

Additional signals from the repos:

• The public organization includes nodecore, dshackle, public, drpc-nextra, and drpc-agent-skills, indicating breadth across routing, documentation, network metadata, and agent tooling
• Dshackle shows dRPC still relies on blockchain-aware fault-tolerant routing ideas at the provider side, with logic around node health, sync status, failover, and request execution consistency
• The repo mix suggests dRPC is building a reusable RPC infrastructure stack, not just a thin reseller layer over third-party nodes

Notes

• This pass did not locate a classic whitepaper or litepaper.
• dRPC appears best categorized as multichain RPC/control-plane infrastructure with both managed and self-hosted/open-source surfaces.
• The strongest primary materials were the official homepage, chain directory, docs repo, and public routing-software repositories.