What’s New on dRPC: HyperCore Support, Tron and TON Upgrades, and More Platform Updates
dRPC has shipped a series of infrastructure updates across NodeCloud and NodeCore. This post covers what changed, what it means for developers, and how to start using each update today.
Access All Updates Through NodeCloud or NodeCore
Every improvement described below is available through NodeCloud, dRPC’s hosted multichain RPC platform. NodeCloud provides instant access to 120+ chains with AI-powered load balancing across 50+ providers, pay-as-you-go pricing with no monthly limits, built-in MEV front-run protection, advanced analytics, and up to 5,000 requests per second. Did we mention no infrastructure setup required?
Teams running self-hosted infrastructure can access the same updates through NodeCore, dRPC’s open-source RPC load balancer. NodeCore is free, provider-agnostic, and built on the same stack as NodeCloud. It gives engineering teams full control over routing logic, caching, retry strategies, and cost optimization across multiple upstreams, with Prometheus-ready observability out of the box.
Hyperliquid: HyperCore RPC Support
dRPC has expanded its Hyperliquid integration to include full HyperCore RPC support, providing developers with reliable infrastructure for building and scaling Hyperliquid dApps.
Endpoint coverage
Requests to both /info and /exchange endpoints can now be routed through your dRPC setup, covering the full range of HyperCore interactions.
Custom archive flags
Parsing historical data is now more precise. Both Mainnet and Testnet endpoints support custom URL flags to filter transaction data in blocks and receipts. Use ?include_hl_native_tx=true to include system transactions in blocks and receipts, or ?exclude_hl_native_tx=true to filter them out. One of the two flags is required to guarantee consistent routing behavior across nodes.
View Hyperliquid RPC endpoints
Tron: Unified NodeCore API and TronGrid Compatibility
Tron is now powered by dRPC’s NodeCore architecture, delivering a significantly improved developer experience and broader API compatibility.
Unified API access
JSON-RPC, REST, and REST Solidity are now accessible under a single base URL, removing the need to manage separate endpoints per interface type.
TronGrid compatibility
dRPC now fully supports TronGrid-style endpoints, including /wallet/* routes. Existing Tron workloads can be migrated to dRPC without refactoring your codebase.
Archival depth
Historical blocks, logs, and transactions are available instantly. Note that following Tron’s native node architecture, the eth_call method is available for latest blocks only.
TON: API v3 and EU-West Node Deployment
To support the scaling demands of Telegram Mini Apps and the broader TON ecosystem, dRPC has upgraded its TON infrastructure on two fronts.
API v3
dRPC now fully supports TON API v3, enabling more efficient data retrieval for account states and smart contract interactions.
EU-West nodes
New Mainnet Full Nodes are live within dRPC’s eu-west cluster, reducing latency for European-based backend servers and improving response times for TON applications serving European users.
EVM: Expanded Debugging Methods
Two new methods have been added to dRPC’s EVM method support across all compatible networks.
trace_rawTransaction
It enables transaction tracing before submission, useful for pre-execution analysis and debugging complex contract interactions.
eth_getStorageValues
It allows direct inspection of smart contract storage slots, supporting deeper state analysis across supported EVM networks.
Both methods are available now on Erigon-powered EVM networks, following the Erigon 3.4 release.
Global Batch Request Optimization
JSON-RPC batch calls across all networks now support a batch_timeout parameter. By setting a custom low timeout, slow individual queries within a batch no longer block the entire request. This allows faster retries on failing calls and meaningfully reduces overall batch latency for high-throughput workloads.
Enterprise: SAML 2.0 SSO and Key Management API
Two additions for teams managing access and API keys at scale.
SAML 2.0 SSO is now live, enabling secure team access through your organization’s existing identity provider. This covers standard enterprise SSO flows with no custom integration required on the dRPC side.
Web API for Key Management provides programmatic control over API key creation, rotation, and access restrictions. Teams can now manage keys as part of their existing infrastructure automation workflows rather than through the dashboard.
Get Started
All updates are live on NodeCloud and NodeCore. For setup details and method references, visit the dRPC documentation.
