{"id":4186,"date":"2026-07-01T10:54:03","date_gmt":"2026-07-01T10:54:03","guid":{"rendered":"https:\/\/drpc.org\/blog\/?p=4186"},"modified":"2026-07-01T11:01:02","modified_gmt":"2026-07-01T11:01:02","slug":"drpc-platform-updates-hypercore-tron-ton","status":"publish","type":"post","link":"https:\/\/drpc.org\/blog\/drpc-platform-updates-hypercore-tron-ton\/","title":{"rendered":"What’s New on dRPC: HyperCore Support, Tron and TON Upgrades, and More Platform Updates"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

What’s New on dRPC: HyperCore Support, Tron and TON Upgrades, and More Platform Updates<\/h1>

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.<\/p>

Access All Updates Through NodeCloud or NodeCore<\/h2>

Every improvement described below is available through NodeCloud<\/a>, 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?<\/p>

Teams running self-hosted infrastructure can access the same updates through NodeCore<\/a>, 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.<\/p>

Hyperliquid: HyperCore RPC Support<\/h2>

dRPC has expanded its Hyperliquid integration to include full HyperCore RPC support, providing developers with reliable infrastructure for building and scaling Hyperliquid dApps.<\/p>

Endpoint coverage<\/strong><\/h3>

Requests to both \/info<\/code> and \/exchange<\/code> endpoints can now be routed through your dRPC setup, covering the full range of HyperCore interactions.<\/p>

Custom archive flags<\/strong><\/h3>

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<\/strong> to include system transactions in blocks and receipts, or ?exclude_hl_native_tx=true<\/strong> to filter them out. One of the two flags is required to guarantee consistent routing behavior across nodes.<\/p>

\"\ud83d\udd17\" View Hyperliquid RPC endpoints<\/a><\/span><\/p>

Tron: Unified NodeCore API and TronGrid Compatibility<\/h2>

Tron is now powered by dRPC’s NodeCore architecture, delivering a significantly improved developer experience and broader API compatibility.<\/p>

Unified API access<\/strong><\/h3>

JSON-RPC, REST, and REST Solidity are now accessible under a single base URL, removing the need to manage separate endpoints per interface type.<\/p>

TronGrid compatibility<\/strong><\/h3>

dRPC now fully supports TronGrid-style endpoints, including \/wallet\/*<\/code> routes. Existing Tron workloads can be migrated to dRPC without refactoring your codebase.<\/p>

Archival depth<\/strong><\/h3>

Historical blocks, logs, and transactions are available instantly. Note that following Tron’s native node architecture, the eth_call<\/code> method is available for latest blocks only.<\/p>

\"\ud83d\udd17\" View Tron RPC endpoints<\/a><\/span><\/p>

TON: API v3 and EU-West Node Deployment<\/h2>

To support the scaling demands of Telegram Mini Apps and the broader TON ecosystem, dRPC has upgraded its TON infrastructure on two fronts.<\/p>

API v3<\/strong><\/h3>

dRPC now fully supports TON API v3, enabling more efficient data retrieval for account states and smart contract interactions.<\/p>

EU-West nodes<\/strong><\/h3>

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.<\/p>

\"\ud83d\udd17\" View TON RPC endpoints<\/a><\/span><\/p>

EVM: Expanded Debugging Methods<\/h2>

Two new methods have been added to dRPC’s EVM method support across all compatible networks.<\/p>

trace_rawTransaction<\/code><\/h3>

It enables transaction tracing before submission, useful for pre-execution analysis and debugging complex contract interactions.<\/p>

eth_getStorageValues<\/code><\/h3>

It allows direct inspection of smart contract storage slots, supporting deeper state analysis across supported EVM networks.<\/p>

Both methods are available now on Erigon-powered EVM networks, following the Erigon 3.4 release.<\/p>

Global Batch Request Optimization<\/h2>

JSON-RPC batch calls across all networks now support a batch_timeout<\/code> 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.<\/p>

Enterprise: SAML 2.0 SSO and Key Management API<\/h2>

Two additions for teams managing access and API keys at scale.<\/p>

SAML 2.0 SSO<\/strong> 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.<\/p>

Web API for Key Management<\/strong> 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.<\/p>

Get Started<\/h2>

All updates are live on NodeCloud<\/a> and NodeCore<\/a>. For setup details and method references, visit the dRPC documentation<\/a>.<\/p>

<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

Full HyperCore RPC support, unified Tron API, TON API v3 with EU-West nodes, new EVM debug methods, batch timeout control, and enterprise SSO. Live now on NodeCloud and NodeCore.<\/p>\n","protected":false},"author":2,"featured_media":4187,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15],"tags":[265,261,229,262,174,195,196,260,264,118,149,263],"class_list":["post-4186","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-product","tag-batch-rpc","tag-enterprise","tag-evm","tag-hypercore","tag-hyperliquid","tag-nodecloud","tag-nodecore","tag-platform-updates","tag-saml-sso","tag-ton","tag-tron","tag-trongrid"],"_links":{"self":[{"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/posts\/4186","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/comments?post=4186"}],"version-history":[{"count":4,"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/posts\/4186\/revisions"}],"predecessor-version":[{"id":4191,"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/posts\/4186\/revisions\/4191"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/media\/4187"}],"wp:attachment":[{"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/media?parent=4186"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/categories?post=4186"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/drpc.org\/blog\/wp-json\/wp\/v2\/tags?post=4186"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}