<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Product &#8211; dRPC Blog</title>
	<atom:link href="https://drpc.org/blog/category/product/feed/" rel="self" type="application/rss+xml" />
	<link>https://drpc.org/blog</link>
	<description>Learn about decentralized RPC infrastructure</description>
	<lastBuildDate>Wed, 01 Jul 2026 11:01:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://drpc.org/blog/wp-content/uploads/2024/08/cropped-drpc-logo-32x32.png</url>
	<title>Product &#8211; dRPC Blog</title>
	<link>https://drpc.org/blog</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>What&#8217;s New on dRPC: HyperCore Support, Tron and TON Upgrades, and More Platform Updates</title>
		<link>https://drpc.org/blog/drpc-platform-updates-hypercore-tron-ton/</link>
		
		<dc:creator><![CDATA[Fito Benitez]]></dc:creator>
		<pubDate>Wed, 01 Jul 2026 10:54:03 +0000</pubDate>
				<category><![CDATA[Product]]></category>
		<category><![CDATA[Batch RPC]]></category>
		<category><![CDATA[Enterprise]]></category>
		<category><![CDATA[EVM]]></category>
		<category><![CDATA[HyperCore]]></category>
		<category><![CDATA[hyperliquid]]></category>
		<category><![CDATA[NodeCloud]]></category>
		<category><![CDATA[NodeCore]]></category>
		<category><![CDATA[Platform Updates]]></category>
		<category><![CDATA[SAML SSO]]></category>
		<category><![CDATA[TON]]></category>
		<category><![CDATA[tron]]></category>
		<category><![CDATA[TronGrid]]></category>
		<guid isPermaLink="false">https://drpc.org/blog/?p=4186</guid>

					<description><![CDATA[<p>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>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/drpc-platform-updates-hypercore-tron-ton/">What&#8217;s New on dRPC: HyperCore Support, Tron and TON Upgrades, and More Platform Updates</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="4186" class="elementor elementor-4186" data-elementor-post-type="post">
				<div class="elementor-element elementor-element-9bfab90 e-flex e-con-boxed e-con e-parent" data-id="9bfab90" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-bee23ce elementor-widget elementor-widget-text-editor" data-id="bee23ce" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<h1>What&#8217;s New on dRPC: HyperCore Support, Tron and TON Upgrades, and More Platform Updates</h1><p>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><h2>Access All Updates Through NodeCloud or NodeCore</h2><p>Every improvement described below is available through <a href="https://drpc.org/nodecloud-multichain-rpc-management">NodeCloud</a>, dRPC&#8217;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><p>Teams running self-hosted infrastructure can access the same updates through <a href="https://drpc.org/nodecore-open-source-rpc-infrastructure">NodeCore</a>, dRPC&#8217;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><h2>Hyperliquid: HyperCore RPC Support</h2><p>dRPC has expanded its Hyperliquid integration to include full HyperCore RPC support, providing developers with reliable infrastructure for building and scaling Hyperliquid dApps.</p><h3><strong>Endpoint coverage</strong></h3><p>Requests to both <code>/info</code> and <code>/exchange</code> endpoints can now be routed through your dRPC setup, covering the full range of HyperCore interactions.</p><h3><strong>Custom archive flags</strong></h3><p>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 <strong>?include_hl_native_tx=true</strong> to include system transactions in blocks and receipts, or <strong>?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><p><img decoding="async" class="emoji" role="img" draggable="false" src="https://s.w.org/images/core/emoji/17.0.2/svg/1f517.svg" alt="&#x1f517;" /> <span style="text-decoration: underline;"><a href="https://drpc.org/chainlist/hyperliquid">View Hyperliquid RPC endpoints</a></span></p><h2>Tron: Unified NodeCore API and TronGrid Compatibility</h2><p>Tron is now powered by dRPC&#8217;s NodeCore architecture, delivering a significantly improved developer experience and broader API compatibility.</p><h3><strong>Unified API access</strong></h3><p>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><h3><strong>TronGrid compatibility</strong></h3><p>dRPC now fully supports TronGrid-style endpoints, including <code>/wallet/*</code> routes. Existing Tron workloads can be migrated to dRPC without refactoring your codebase.</p><h3><strong>Archival depth</strong></h3><p>Historical blocks, logs, and transactions are available instantly. Note that following Tron&#8217;s native node architecture, the <code>eth_call</code> method is available for latest blocks only.</p><p><img decoding="async" class="emoji" role="img" draggable="false" src="https://s.w.org/images/core/emoji/17.0.2/svg/1f517.svg" alt="&#x1f517;" /><span style="text-decoration: underline;"> <a href="https://drpc.org/chainlist/tron">View Tron RPC endpoints</a></span></p><h2>TON: API v3 and EU-West Node Deployment</h2><p>To support the scaling demands of Telegram Mini Apps and the broader TON ecosystem, dRPC has upgraded its TON infrastructure on two fronts.</p><h3><strong>API v3</strong></h3><p>dRPC now fully supports TON API v3, enabling more efficient data retrieval for account states and smart contract interactions.</p><h3><strong>EU-West nodes</strong></h3><p>New Mainnet Full Nodes are live within dRPC&#8217;s eu-west cluster, reducing latency for European-based backend servers and improving response times for TON applications serving European users.</p><p><img decoding="async" class="emoji" role="img" draggable="false" src="https://s.w.org/images/core/emoji/17.0.2/svg/1f517.svg" alt="&#x1f517;" /> <span style="text-decoration: underline;"><a href="https://drpc.org/chainlist/ton">View TON RPC endpoints</a></span></p><h2>EVM: Expanded Debugging Methods</h2><p>Two new methods have been added to dRPC&#8217;s EVM method support across all compatible networks.</p><h3><code>trace_rawTransaction</code></h3><p>It enables transaction tracing before submission, useful for pre-execution analysis and debugging complex contract interactions.</p><h3><code>eth_getStorageValues</code></h3><p>It allows direct inspection of smart contract storage slots, supporting deeper state analysis across supported EVM networks.</p><p>Both methods are available now on Erigon-powered EVM networks, following the Erigon 3.4 release.</p><h2>Global Batch Request Optimization</h2><p>JSON-RPC batch calls across all networks now support a <code>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><h2>Enterprise: SAML 2.0 SSO and Key Management API</h2><p>Two additions for teams managing access and API keys at scale.</p><p><strong>SAML 2.0 SSO</strong> is now live, enabling secure team access through your organization&#8217;s existing identity provider. This covers standard enterprise SSO flows with no custom integration required on the dRPC side.</p><p><strong>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><h2>Get Started</h2><p>All updates are live on <a href="https://drpc.org/nodecloud-multichain-rpc-management">NodeCloud</a> and <a href="https://drpc.org/nodecore-open-source-rpc-infrastructure">NodeCore</a>. For setup details and method references, visit the <a href="https://drpc.org/docs">dRPC documentation</a>.</p><p><!-- notionvc: e0da163b-fd79-47c7-ae6f-c0bb5f2edb24 --></p>								</div>
					</div>
				</div>
				</div>
		<p>The post <a rel="nofollow" href="https://drpc.org/blog/drpc-platform-updates-hypercore-tron-ton/">What&#8217;s New on dRPC: HyperCore Support, Tron and TON Upgrades, and More Platform Updates</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Crypto Wallet API: Balances, DeFi Positions, and PnL in One Call</title>
		<link>https://drpc.org/blog/crypto-wallet-api/</link>
		
		<dc:creator><![CDATA[Fito Benitez]]></dc:creator>
		<pubDate>Thu, 25 Jun 2026 07:27:49 +0000</pubDate>
				<category><![CDATA[APIs]]></category>
		<category><![CDATA[Product]]></category>
		<category><![CDATA[wallet]]></category>
		<guid isPermaLink="false">https://drpc.org/blog/?p=4178</guid>

					<description><![CDATA[<p>The dRPC Data API is a crypto wallet API that returns wallet balances, DeFi positions, transaction history, and historical PnL across 8,000+ protocols, 35+ EVM chains, and Solana from a single REST endpoint. It removes the indexing layer most teams build themselves, so you query high-level portfolio data directly instead of parsing logs and running [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/crypto-wallet-api/">Crypto Wallet API: Balances, DeFi Positions, and PnL in One Call</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="4178" class="elementor elementor-4178" data-elementor-post-type="post">
				<div class="elementor-element elementor-element-df75305 e-flex e-con-boxed e-con e-parent" data-id="df75305" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-d269eaa elementor-widget elementor-widget-text-editor" data-id="d269eaa" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="12:1-12:371;552-922">The dRPC Data API is a crypto wallet API that returns wallet balances, DeFi positions, transaction history, and historical PnL across 8,000+ protocols, 35+ EVM chains, and Solana from a single REST endpoint. It removes the indexing layer most teams build themselves, so you query high-level portfolio data directly instead of parsing logs and running your own databases.</p><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="14:1-14:84;924-1007">If you are already on a paid dRPC plan, it is live in your existing API keys today.</p><h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="16:1-16:45;1009-1053">Why raw RPC is not enough for wallet data</h2><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="18:1-18:205;1055-1259">Standard RPC nodes are built to broadcast transactions and read chain state. They are not built to answer &#8220;what does this wallet hold right now, across every chain, with USD values and spam filtered out.&#8221;</p><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="20:1-20:299;1261-1559">To get that, teams usually build a custom indexing stack: subgraphs, databases, log parsers, and price feeds. It takes months, costs real money in server time, and breaks when a node desyncs. A crypto wallet API removes that work by serving the aggregated, decoded result instead of the raw inputs.</p><h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="22:1-22:45;1561-1605">What you can build with the dRPC Data API</h2><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="24:1-24:111;1607-1717">A wallet balance API call returns structured JSON, so you ship features instead of maintaining infrastructure:</p><ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3" data-sourcepos="26:1-29:82;1719-2193"><li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="26:1-26:155;1719-1873"><strong>Unified wallets and portfolios.</strong> Real-time balances and prices across 35+ EVM chains and Solana in one call. Spam tokens are filtered out by default.</li><li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="27:1-27:131;1874-2004"><strong>DeFi portfolio tracking.</strong> Position-level data for 8,000+ protocols, covering supply, borrow, LP tokens, staking, and rewards.</li><li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="28:1-28:107;2005-2111"><strong>Transaction history.</strong> Decoded, human-readable transfers and contract interactions instead of raw hex.</li><li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="29:1-29:82;2112-2193"><strong>Tax and accounting.</strong> Historical PnL, cost-basis data, and reward breakdowns.</li></ul><h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="31:1-31:43;2195-2237">How this crypto wallet API is different</h2><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="33:1-33:143;2239-2381">There are other indexed data APIs. Two gaps separate most of them from production needs: how fast coverage expands, and how fresh the data is.</p>								</div>
		<div class="elementor-element elementor-element-ba29e3d e-grid e-con-full e-con e-child" data-id="ba29e3d" data-element_type="container" data-e-type="container">
				<div class="elementor-element elementor-element-18dd307 elementor-widget elementor-widget-heading" data-id="18dd307" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
					<h2 class="elementor-heading-title elementor-size-default"><b>CONCERN</b></h2>				</div>
				<div class="elementor-element elementor-element-c65efb6 elementor-widget elementor-widget-heading" data-id="c65efb6" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
					<h2 class="elementor-heading-title elementor-size-default"><b>COMMON PROVIDERS</b></h2>				</div>
				<div class="elementor-element elementor-element-75b4141 elementor-widget elementor-widget-heading" data-id="75b4141" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
					<h2 class="elementor-heading-title elementor-size-default"><b>dRPC DATA API</b></h2>				</div>
				<div class="elementor-element elementor-element-36c536b elementor-widget elementor-widget-text-editor" data-id="36c536b" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>New DeFi protocol added</p>								</div>
				<div class="elementor-element elementor-element-59e271f elementor-widget elementor-widget-text-editor" data-id="59e271f" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>Weeks, on the provider&#8217;s roadmap</p>								</div>
				<div class="elementor-element elementor-element-92cc991 elementor-widget elementor-widget-text-editor" data-id="92cc991" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>2 days on request</p>								</div>
				<div class="elementor-element elementor-element-5ae3604 elementor-widget elementor-widget-text-editor" data-id="5ae3604" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>New EVM chain added</p>								</div>
				<div class="elementor-element elementor-element-9fd9f3d elementor-widget elementor-widget-text-editor" data-id="9fd9f3d" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>Variable, often months</p>								</div>
				<div class="elementor-element elementor-element-49aa97f elementor-widget elementor-widget-text-editor" data-id="49aa97f" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>5 days</p>								</div>
				<div class="elementor-element elementor-element-367304e elementor-widget elementor-widget-text-editor" data-id="367304e" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>DeFi position freshness</p>								</div>
				<div class="elementor-element elementor-element-ff6a9b2 elementor-widget elementor-widget-text-editor" data-id="ff6a9b2" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>Cached on a timer</p>								</div>
				<div class="elementor-element elementor-element-cb325ff elementor-widget elementor-widget-text-editor" data-id="cb325ff" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>Transaction-triggered cache</p>								</div>
				<div class="elementor-element elementor-element-122a418 elementor-widget elementor-widget-text-editor" data-id="122a418" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>Reliability</p>								</div>
				<div class="elementor-element elementor-element-c636bf0 elementor-widget elementor-widget-text-editor" data-id="c636bf0" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>Best effort-uptime</p>								</div>
				<div class="elementor-element elementor-element-681d35a elementor-widget elementor-widget-text-editor" data-id="681d35a" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>99.9% compensated uptime SLA</p>								</div>
				<div class="elementor-element elementor-element-07fe46d elementor-widget elementor-widget-text-editor" data-id="07fe46d" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>Coverage</p>								</div>
				<div class="elementor-element elementor-element-635eca9 elementor-widget elementor-widget-text-editor" data-id="635eca9" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>Single ecosystem common</p>								</div>
				<div class="elementor-element elementor-element-55d2063 elementor-widget elementor-widget-text-editor" data-id="55d2063" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p>35+ EVM chains plus Solana</p>								</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-f4d9bbb e-flex e-con-boxed e-con e-parent" data-id="f4d9bbb" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-71a6b1e elementor-widget elementor-widget-text-editor" data-id="71a6b1e" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<h3 class="text-text-100 mt-2 -mb-1 text-base font-bold" data-sourcepos="43:1-43:37;2800-2836">Coverage that keeps up with DeFi</h3><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="45:1-45:238;2838-3075">Web3 moves faster than most API roadmaps. If you need a protocol that is not yet covered, you submit a request and it is live in 48 hours. A new EVM chain takes 5 days. Your integration code does not change; the backend scales behind it.</p><h3 class="text-text-100 mt-2 -mb-1 text-base font-bold" data-sourcepos="47:1-47:38;3077-3114">Real-time data, not a stale cache</h3><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="49:1-49:306;3116-3421">Many providers refresh DeFi positions on a timer. A user can close an Aave position and still see it as active in your app hours later. The dRPC Data API uses a transaction-triggered cache that updates the moment an on-chain transaction settles, so users see current positions rather than an old snapshot.</p><h3 class="text-text-100 mt-2 -mb-1 text-base font-bold" data-sourcepos="51:1-51:38;3423-3460">An SLA that is backed financially</h3><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="53:1-53:91;3462-3552">Production workloads run under a 99.9% uptime SLA. If dRPC misses it, you are compensated.</p><h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="55:1-55:27;3554-3580">Make your first request</h2><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="57:1-57:110;3582-3691">There is no separate onboarding. If you are on a paid dRPC plan, the Data API is already active on your keys.</p><ol class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-decimal flex flex-col gap-1 pl-8 mb-3" data-sourcepos="59:1-60:70;3693-3931"><li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="59:1-59:169;3693-3861">Log into your dashboard, open an active API key, and copy the base URL from the Data API card. It follows the pattern <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">https://lb.drpc.live/lambda/&lt;YOUR_API_TOKEN&gt;</code>.</li><li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="60:1-60:70;3862-3931">Pull balances for a wallet. Example using vitalik.eth on Ethereum:</li></ol>								</div>
				<div class="elementor-element elementor-element-a7fbe15 elementor-widget elementor-widget-code-highlight" data-id="a7fbe15" data-element_type="widget" data-e-type="widget" data-widget_type="code-highlight.default">
							<div class="prismjs-default copy-to-clipboard ">
			<pre data-line="" class="highlight-height language-javascript line-numbers">
				<code readonly="true" class="language-javascript">
					<xmp>curl "https://lb.drpc.live/lambda/<YOUR_API_TOKEN>/ethereum/balances?address=vitalik.eth"</xmp>
				</code>
			</pre>
		</div>
						</div>
				<div class="elementor-element elementor-element-a2215a8 elementor-widget elementor-widget-text-editor" data-id="a2215a8" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<ol class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-decimal flex flex-col gap-1 pl-8 mb-3" start="3" data-sourcepos="66:1-66:98;4036-4133"><li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="66:1-66:98;4036-4133">You receive a structured array with total net worth, USD values, balances, and token metadata.</li></ol><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="68:1-68:103;4135-4237">To query every supported network at once, remove <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">ethereum/</code> from the path to hit the global endpoint.</p>								</div>
				<div class="elementor-element elementor-element-bee2907 elementor-blockquote--skin-boxed elementor-widget elementor-widget-blockquote" data-id="bee2907" data-element_type="widget" data-e-type="widget" data-widget_type="blockquote.default">
							<blockquote class="elementor-blockquote">
			<p class="elementor-blockquote__content">
				Example shapes above are illustrative. Confirm exact paths and response fields against the live quickstart docs before publishing.			</p>
					</blockquote>
						</div>
				<div class="elementor-element elementor-element-c032e95 elementor-widget elementor-widget-text-editor" data-id="c032e95" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="72:1-72:30;4373-4402">Frequently asked questions</h2><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="74:1-75:225;4404-4661"><strong>What is a crypto wallet API?</strong> A crypto wallet API returns wallet-level data such as token balances, DeFi positions, transaction history, and portfolio value through a single interface, instead of requiring you to index and decode raw chain data yourself.</p><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="77:1-78:81;4663-4792"><strong>Which chains does the dRPC Data API support?</strong> 35+ EVM chains and Solana, with new EVM chains added in about 5 days on request.</p><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="80:1-81:67;4794-4901"><strong>How many DeFi protocols are covered?</strong> Over 8,000, with new protocols added within 48 hours of a request.</p><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="83:1-84:123;4903-5066"><strong>How fresh is the DeFi position data?</strong> The cache is transaction-triggered, so positions update when an on-chain transaction settles rather than on a fixed timer.</p><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="86:1-87:88;5068-5194"><strong>Do I need a new account to use it?</strong> No. If you are on a paid dRPC plan, the Data API is already live in your existing keys.</p><h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="89:1-89:15;5196-5210">Get started</h2><p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="91:1-91:147;5212-5358">Your engineers should be writing product logic, not maintaining indexers. If you have a dRPC account, the Data API is sitting in your active keys.</p><ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3" data-sourcepos="93:1-95:34;5360-5464"><li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="93:1-93:44;5360-5403">Go to your dashboard to get your endpoint</li><li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="94:1-94:27;5404-5430">Read the quickstart docs</li><li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="95:1-95:34;5431-5464">Learn more at drpc.org/data-api</li></ul>								</div>
					</div>
				</div>
				</div>
		<p>The post <a rel="nofollow" href="https://drpc.org/blog/crypto-wallet-api/">Crypto Wallet API: Balances, DeFi Positions, and PnL in One Call</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How to Use Agent Skills for RPC: Connect Your AI Agent to Blockchain Data</title>
		<link>https://drpc.org/blog/how-to-use-agent-skills-for-rpc-blockchain/</link>
		
		<dc:creator><![CDATA[Fito Benitez]]></dc:creator>
		<pubDate>Wed, 22 Apr 2026 09:58:49 +0000</pubDate>
				<category><![CDATA[Product]]></category>
		<category><![CDATA[AI agent skills]]></category>
		<guid isPermaLink="false">https://drpc.org/blog/?p=4166</guid>

					<description><![CDATA[<p>Introduction Accessing blockchain data typically requires: setting up RPC endpoints managing API keys writing and debugging queries With agent skills for RPC, this process changes. Instead of writing requests manually, your AI agent can query blockchain data directly using natural language. This guide walks through how to: connect your agent run your first queries get [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/how-to-use-agent-skills-for-rpc-blockchain/">How to Use Agent Skills for RPC: Connect Your AI Agent to Blockchain Data</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="4166" class="elementor elementor-4166" data-elementor-post-type="post">
				<div class="elementor-element elementor-element-c8eaeae e-flex e-con-boxed e-con e-parent" data-id="c8eaeae" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-3af1816 elementor-widget elementor-widget-text-editor" data-id="3af1816" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<h2><strong>Introduction</strong></h2><p>Accessing blockchain data typically requires:</p><ul><li>setting up RPC endpoints</li><li>managing API keys</li><li>writing and debugging queries</li></ul><p>With <strong>agent skills for RPC</strong>, this process changes.</p><p>Instead of writing requests manually, your AI agent can query blockchain data directly using natural language.</p><p>This guide walks through how to:</p><ul><li>connect your agent</li><li>run your first queries</li><li>get the most out of dRPC Agent Skills</li></ul><h2><strong>What You Need Before Starting</strong></h2><p>Before using dRPC Agent Skills, make sure you have:</p><ul><li>an AI agent environment (ChatGPT, Claude, Gemini, or MCP-compatible tools like Cursor or Claude Code)</li><li>a wallet capable of signing transactions</li><li>access to the dRPC Agent Skills repository</li></ul><p><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f449.png" alt="👉" class="wp-smiley" style="height: 1em; max-height: 1em;" /> Repository: <a href="https://github.com/drpcorg/drpc-agent-skills" target="_blank" rel="noopener">https://github.com/drpcorg/drpc-agent-skills</a></p><p>No prior RPC knowledge is required.</p><h3><strong>Step 1: Connect Your AI Agent to dRPC Agent Skills</strong></h3><p>Unlike traditional RPC setups, there is no manual configuration.</p><p>The connection process is handled by the agent itself:</p><ol><li>The agent discovers available skills</li><li>It initiates authentication</li><li>You approve via wallet signature</li><li>The agent receives access credentials</li></ol><p>Once complete, the agent is ready to query blockchain data.</p><p><strong>Typical setup time: ~30 seconds</strong></p><p><strong>Step 2: Run Your First Blockchain Query</strong></p><p>After connecting, you can start with simple natural language queries:</p><p><strong>Example queries:</strong></p><ul><li>“What is the balance of this wallet: 0x…?”</li><li>“Show the last 10 transactions for this address”</li><li>“Compare gas fees between Ethereum and Arbitrum”</li><li>“What tokens does this wallet hold?”</li></ul><p>The agent will:</p><ul><li>determine which RPC methods to call</li><li>structure the request</li><li>return readable results</li></ul><p>Here’s what that looks like in practice:</p><p><!-- notionvc: d1923b8a-4bdd-417a-ba3b-bde987198e98 --></p>								</div>
				<div class="elementor-element elementor-element-26905cf elementor-widget elementor-widget-image" data-id="26905cf" data-element_type="widget" data-e-type="widget" data-widget_type="image.default">
															<img fetchpriority="high" decoding="async" width="800" height="397" src="https://drpc.org/blog/wp-content/uploads/2026/04/agent-skills-rpc-query-to-result-diagram-drpc-1024x508.webp" class="attachment-large size-large wp-image-4169 not-transparent" alt="Example of using dRPC Agent Skills to query blockchain data via RPC with natural language and receive structured output." srcset="https://drpc.org/blog/wp-content/uploads/2026/04/agent-skills-rpc-query-to-result-diagram-drpc-1024x508.webp 1024w, https://drpc.org/blog/wp-content/uploads/2026/04/agent-skills-rpc-query-to-result-diagram-drpc-300x149.webp 300w, https://drpc.org/blog/wp-content/uploads/2026/04/agent-skills-rpc-query-to-result-diagram-drpc-768x381.webp 768w, https://drpc.org/blog/wp-content/uploads/2026/04/agent-skills-rpc-query-to-result-diagram-drpc.webp 1511w" sizes="(max-width: 800px) 100vw, 800px" data-has-transparency="false" data-dominant-color="f2f4f2" style="--dominant-color: #f2f4f2" />															</div>
				<div class="elementor-element elementor-element-f2341b8 elementor-widget elementor-widget-text-editor" data-id="f2341b8" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<h3><strong>Step 3: Use Built-in Skills and Recipes</strong></h3><p>dRPC Agent Skills include predefined logic for common use cases.</p><p>These “recipes” allow agents to perform more advanced queries without additional input.</p><p><strong>Examples:</strong></p><ul><li>DeFi portfolio analysis</li><li>cross-chain comparisons</li><li>gas optimization insights</li></ul><p>Instead of chaining multiple RPC calls manually, the agent executes them automatically.</p><h3><strong>Step 4: Use MCP-Compatible Tools (Optional)</strong></h3><p>If you are using MCP-enabled environments, dRPC Agent Skills integrate directly.</p><p>Supported environments include:</p><ul><li>Claude Code</li><li>Cursor</li><li>Gemini CLI</li></ul><p>This allows you to:</p><ul><li>embed blockchain queries into workflows</li><li>automate analysis pipelines</li><li>combine on-chain data with other tools</li></ul><h3><strong>Step 5: Refine Queries for Better Results</strong></h3><p>While no prompt engineering is required, better queries improve output quality.</p><p><strong>Best practices:</strong></p><ul><li>be specific (e.g. include wallet address, chain)</li><li>ask comparative questions for insights</li><li>break complex queries into steps if needed</li></ul><h2><strong>Common Use Cases</strong></h2><h3><strong>1. Wallet Analysis</strong></h3><ul><li>track balances</li><li>review transaction history</li><li>identify token holdings</li></ul><h3><strong>2. Cross-Chain Comparisons</strong></h3><ul><li>compare gas costs</li><li>evaluate network activity</li><li>analyze differences between L2s</li></ul><h3><strong>3. Developer Prototyping</strong></h3><ul><li>test ideas without writing code</li><li>validate data quickly</li><li>reduce integration overhead</li></ul><h2><strong>Troubleshooting</strong></h2><h3><strong>1. Agent not connecting</strong></h3><ul><li>ensure wallet signature is completed</li><li>verify agent environment supports external tools</li></ul><h3><strong>2. Incomplete or unclear responses</strong></h3><ul><li>refine query with more context</li><li>specify chain or address</li></ul><h3><strong>3. Unsupported queries</strong></h3><ul><li>try breaking into smaller steps</li><li>use simpler phrasing</li></ul><h2><strong>Best Practices for Using Agent Skills RPC</strong></h2><ul><li>start with simple queries</li><li>leverage built-in recipes</li><li>validate outputs for critical use cases</li><li>combine with MCP tools for automation</li></ul><h2><strong>Key Takeaway</strong></h2><p>Agent skills for RPC remove the need to manually interact with blockchain infrastructure.</p><p>Instead of:</p><ul><li>configuring endpoints</li><li>writing queries</li><li>parsing responses</li></ul><p>You can connect your agent and start asking questions.</p><h2><strong>Get Started</strong></h2><p><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f449.png" alt="👉" class="wp-smiley" style="height: 1em; max-height: 1em;" /> <a href="https://drpc.org/agent-skills">https://drpc.org/agent-skills</a></p><p><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f449.png" alt="👉" class="wp-smiley" style="height: 1em; max-height: 1em;" /> <a href="https://github.com/drpcorg/drpc-agent-skills" target="_blank" rel="noopener">https://github.com/drpcorg/drpc-agent-skills</a></p><h2><strong>Frequently Asked Questions (FAQS)</strong></h2><h3><strong>How do I connect an AI agent to blockchain RPC?</strong></h3><p>You can connect an AI agent to blockchain RPC using dRPC Agent Skills. The agent handles discovery, authentication via wallet signature, and access provisioning automatically, without requiring manual setup.</p><h3><strong>Do I need coding experience to use agent skills?</strong></h3><p>No. Agent skills for RPC are designed to work with natural language queries. Developers can benefit from faster workflows, but non-technical users can also access blockchain data.</p><h3><strong>What types of queries can I run?</strong></h3><p>You can run queries related to:</p><ul><li>wallet balances</li><li>transactions</li><li>token holdings</li><li>gas fees</li><li>cross-chain comparisons</li></ul><h3><strong>How does the agent know which RPC methods to call?</strong></h3><p>dRPC Agent Skills include structured definitions that map user intent to RPC methods. The agent uses these to generate correct queries and interpret responses.</p><h3><strong>Can I use this with MCP tools?</strong></h3><p>Yes. dRPC Agent Skills are compatible with MCP-enabled tools, allowing integration into AI workflows and development environments.</p><h3><strong>Is this production-ready?</strong></h3><p>Yes. Agent Skills operate on top of dRPC’s existing infrastructure, which supports 100+ blockchains and includes decentralized routing and failover.</p><h3><strong>Does this replace traditional RPC usage?</strong></h3><p>No. Traditional RPC remains available. Agent Skills provide an additional interface optimized for AI-driven workflows.</p><p><!-- notionvc: 5e0f980c-77bf-485b-858c-dbb674f3df69 --></p>								</div>
					</div>
				</div>
				</div>
		<p>The post <a rel="nofollow" href="https://drpc.org/blog/how-to-use-agent-skills-for-rpc-blockchain/">How to Use Agent Skills for RPC: Connect Your AI Agent to Blockchain Data</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Agent Skills for RPC: Access Blockchain Data via AI Agents with dRPC</title>
		<link>https://drpc.org/blog/agent-skills-rpc-blockchain-ai/</link>
		
		<dc:creator><![CDATA[Fito Benitez]]></dc:creator>
		<pubDate>Thu, 16 Apr 2026 13:07:08 +0000</pubDate>
				<category><![CDATA[Product]]></category>
		<category><![CDATA[AI agent skills]]></category>
		<guid isPermaLink="false">https://drpc.org/blog/?p=4152</guid>

					<description><![CDATA[<p>Agent Skills for RPC: Access Blockchain Data via AI Agents with dRPC What Are Agent Skills in Blockchain? Agent skills RPC are a new way for AI agents to interact with blockchain data. Instead of: writing RPC calls integrating SDKs parsing JSON responses → AI agents can now retrieve blockchain data using natural language queries [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/agent-skills-rpc-blockchain-ai/">Agent Skills for RPC: Access Blockchain Data via AI Agents with dRPC</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="4152" class="elementor elementor-4152" data-elementor-post-type="post">
				<div class="elementor-element elementor-element-1e8cea2 e-flex e-con-boxed e-con e-parent" data-id="1e8cea2" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-f8d4a40 elementor-widget elementor-widget-text-editor" data-id="f8d4a40" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<h1><strong>Agent Skills for RPC: Access Blockchain Data via AI Agents with dRPC</strong></h1><h2><strong>What Are Agent Skills in Blockchain?</strong></h2><p><strong>Agent skills RPC</strong> are a new way for AI agents to interact with blockchain data.</p><p>Instead of:</p><ul><li>writing RPC calls</li><li>integrating SDKs</li><li>parsing JSON responses</li></ul><p>→ <span class="s1">AI agents can now </span><b>retrieve blockchain data using natural language queries through agent skills RPC</b><span class="s1">.</span></p><p>In practice, this means:</p><ul><li>“Check this wallet’s balance”</li><li>“Compare gas fees across L2s”</li><li>“Analyze recent transactions”</li></ul><p>→ and the agent handles the underlying RPC logic automatically.</p><h2><strong>Why Traditional RPC Access Is Limiting</strong></h2><p>Accessing blockchain data has historically required:</p><ul><li>manual endpoint configuration</li><li>API key management</li><li>knowledge of RPC methods</li><li>custom parsing logic</li></ul><p>This creates friction for:</p><ul><li>developers building fast</li><li>analysts needing quick insights</li><li>teams without dedicated infra resources</li></ul><p>Even with modern tooling, the workflow still revolves around <strong>humans understanding RPC</strong>.</p><p>This is exactly the type of friction that <span class="s1"><b>agent skills RPC</b></span> aim to eliminate.</p><h2><strong>Agent Skills for RPC: A New Interface Layer</strong></h2><p>dRPC Agent Skills introduce a different model:</p><p>&#8220;Instead of learning how to query blockchain, your agent already knows how.&#8221;</p><p>This is not a new infrastructure product.</p><p>It’s a <strong>new interface to dRPC’s existing RPC layer</strong>, designed for AI-native workflows.</p><p><!-- notionvc: a1494983-c58e-435e-9b41-d724dfaaa477 --></p>								</div>
				<div class="elementor-element elementor-element-a924ccc elementor-widget elementor-widget-image" data-id="a924ccc" data-element_type="widget" data-e-type="widget" data-widget_type="image.default">
															<img decoding="async" width="800" height="534" src="https://drpc.org/blog/wp-content/uploads/2026/04/agent-skills-rpc-flow-diagram-drpc-1024x683.webp" class="attachment-large size-large wp-image-4155 not-transparent" alt="Horizontal diagram showing how dRPC Agent Skills enable AI agents to access blockchain data via RPC using natural language queries" srcset="https://drpc.org/blog/wp-content/uploads/2026/04/agent-skills-rpc-flow-diagram-drpc-1024x683.webp 1024w, https://drpc.org/blog/wp-content/uploads/2026/04/agent-skills-rpc-flow-diagram-drpc-300x200.webp 300w, https://drpc.org/blog/wp-content/uploads/2026/04/agent-skills-rpc-flow-diagram-drpc-768x512.webp 768w, https://drpc.org/blog/wp-content/uploads/2026/04/agent-skills-rpc-flow-diagram-drpc.webp 1536w" sizes="(max-width: 800px) 100vw, 800px" data-has-transparency="false" data-dominant-color="f7f9f8" style="--dominant-color: #f7f9f8" />															</div>
				<div class="elementor-element elementor-element-61504e4 elementor-widget elementor-widget-text-editor" data-id="61504e4" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<h2><strong>How dRPC Agent Skills Work</strong></h2><p>dRPC Agent Skills allow AI agents (ChatGPT, Claude, Gemini, MCP-compatible tools) to:</p><ol><li>Discover available blockchain skills</li><li>Authenticate via wallet signature</li><li>Receive access credentials</li><li>Start querying blockchain data</li></ol><p>All without manual configuration.</p><p>This workflow is enabled by <span class="s1"><b>agent skills RPC</b></span>, which abstract the complexity of interacting with blockchain infrastructure.</p><p><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f449.png" alt="👉" class="wp-smiley" style="height: 1em; max-height: 1em;" /> Explore the implementation: <a href="https://github.com/drpcorg/drpc-agent-skills" target="_blank" rel="noopener">https://github.com/drpcorg/drpc-agent-skills</a></p><h2><strong>Key Features of dRPC Agent Skills</strong></h2><h3><strong>1. Self-Onboarding Agents</strong></h3><p>The agent handles setup autonomously:</p><ul><li>discovers the skill</li><li>authenticates</li><li>provisions access</li></ul><p>No dashboards. No copy-pasting API keys.</p><p><strong>Result: </strong>From zero to live blockchain queries in seconds.</p><h3><strong>2. Built-in Skills and Recipes</strong></h3><p>dRPC provides structured “skills” that define:</p><ul><li>which RPC methods to use</li><li>how to format requests</li><li>how to parse responses</li><li>how to handle errors</li></ul><p>Predefined recipes include:</p><ul><li>DeFi portfolio checks</li><li>cross-chain comparisons</li><li>gas optimization</li></ul><p><strong>Result: </strong>The agent understands blockchain data without reading documentation.</p><h3><strong>3. Natural Language → RPC Execution</strong></h3><p>Users interact with blockchain data through plain English.</p><p>The agent translates:</p><ul><li>intent → RPC calls</li><li>responses → structured outputs</li></ul><p><strong>Result: </strong>No need to understand RPC methods or schemas.</p><p>This is one of the core advantages of <span class="s1"><b>agent skills RPC</b></span>, enabling seamless translation from intent to execution.</p><h3><strong>4. Full dRPC Infrastructure Coverage</strong></h3><p>Agent Skills operate on top of dRPC’s infrastructure:</p><ul><li>100+ blockchains</li><li>200+ networks</li><li>decentralized routing</li><li>automatic failover</li></ul><p><strong>Result: </strong>No trade-off between usability and reliability.</p><h2><strong>Where Agent Skills Fit in the dRPC Stack</strong></h2><p>dRPC Agent Skills sit on top of:</p><ul><li>existing RPC endpoints</li><li>NodeCloud infrastructure</li><li>decentralized node network</li></ul><p>They do not change:</p><ul><li>billing</li><li>authorization</li><li>performance guarantees</li></ul><p>They simply change <strong>how users interact with the system</strong>.</p><h2><strong>Use Cases for Agent Skills RPC</strong></h2><h3><strong>Developers</strong></h3><ul><li>prototype faster without writing RPC calls</li><li>reduce integration complexity</li></ul><h3><strong>Traders &amp; Analysts</strong></h3><ul><li>query wallets and transactions instantly</li><li>compare metrics across chains</li></ul><h3><strong>Business Teams</strong></h3><ul><li>access on-chain data without technical setup</li><li>generate insights through AI tools</li></ul><h2><strong>Why Agent Skills Matter for Blockchain UX</strong></h2><p>Blockchain infrastructure has improved significantly.</p><p>But access patterns have not.</p><p>Agent Skills represent a shift toward:</p><ul><li><strong>AI-native interfaces</strong></li><li><strong>intent-based queries</strong></li><li><strong>abstraction of protocol complexity</strong></li></ul><p>Instead of improving dashboards or APIs, the focus moves to <span style="font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, 'Helvetica Neue', Arial, 'Noto Sans', sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji';">removing the need to understand RPC altogether.</span></p><h2><strong>Getting Started</strong></h2><ul><li><p>Explore the agent repository:</p><p><a href="https://github.com/drpcorg/drpc-agent-skills" target="_blank" rel="noopener">https://github.com/drpcorg/drpc-agent-skills</a></p></li><li><p>Access the feature:</p><p><a href="https://drpc.org/agent-skills">https://drpc.org/agent-skills</a></p></li></ul><h2><strong>Take Away</strong></h2><p>Agent Skills don’t change what RPC does.</p><p>They change <strong>who can use it, and how easily</strong>.</p><h2><strong>Frequently Asked Questions (FAQs)</strong></h2><h3><strong>What are agent skills in RPC</strong></h3><p><b>Agent skills RPC</b><span class="s1"> are </span>structured capabilities that allow AI agents to interact with RPC endpoints. They define how to construct requests, interpret responses, and handle blockchain-specific logic without requiring user input or manual coding.</p><h3><strong>How do AI agents access blockchain data?</strong></h3><p>AI agents access blockchain data by connecting to RPC infrastructure through predefined skills. These skills translate natural language queries into RPC calls and return structured results to the user.</p><h3><strong>Do I still need to configure RPC endpoints?</strong></h3><p>No. With dRPC Agent Skills, the agent handles discovery, authentication, and access automatically. There is no need to manually configure endpoints or manage API keys.</p><h3><strong>What makes dRPC Agent Skills different?</strong></h3><p>dRPC Agent Skills focus on:</p><ul><li>autonomous onboarding</li><li>built-in blockchain understanding</li><li>structured query execution</li></ul><p>This reduces the need for documentation, prompt engineering, or custom integrations.</p><h3><strong>Is this compatible with MCP tools?</strong></h3><p>Yes. dRPC Agent Skills include MCP-compatible tooling, allowing integration with platforms like Claude Code, Cursor, and other agent-based environments.</p><h3><strong>Which blockchains are supported?</strong></h3><p>dRPC supports:</p><ul><li>100+ blockchains</li><li>200+ networks</li></ul><p>Agent Skills operate across all supported networks.</p><h3><strong>Is this only for developers?</strong></h3><p>No. While developers benefit from faster integration, Agent Skills are also useful for:</p><ul><li>analysts</li><li>traders</li><li>business teams</li></ul><p>Anyone who needs blockchain data without dealing with infrastructure.</p><h3><strong>How secure is the authentication process?</strong></h3><p>Authentication is handled via wallet signature, ensuring secure and verifiable access without exposing API keys manually.</p><h3><strong>Does this replace traditional RPC usage?</strong></h3><p>No. Traditional RPC access remains available.</p><p>Agent Skills provide an <strong>additional interface layer</strong>, optimized for AI-driven workflows.</p><p><!-- notionvc: 67d7ff99-4572-405a-9d77-c838dd0da2a4 --></p>								</div>
					</div>
				</div>
				</div>
		<p>The post <a rel="nofollow" href="https://drpc.org/blog/agent-skills-rpc-blockchain-ai/">Agent Skills for RPC: Access Blockchain Data via AI Agents with dRPC</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Open Source RPC Stack: When Self-Hosted Infrastructure Beats Managed RPC</title>
		<link>https://drpc.org/blog/open-source-rpc-stack-self-hosted-vs-managed/</link>
		
		<dc:creator><![CDATA[Fito Benitez]]></dc:creator>
		<pubDate>Thu, 15 Jan 2026 14:55:45 +0000</pubDate>
				<category><![CDATA[Education]]></category>
		<category><![CDATA[Product]]></category>
		<category><![CDATA[on-premise]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[OSS stack]]></category>
		<category><![CDATA[rpc oss stack]]></category>
		<category><![CDATA[rpc stack]]></category>
		<category><![CDATA[self-hosted]]></category>
		<guid isPermaLink="false">https://drpc.org/blog/?p=3708</guid>

					<description><![CDATA[<p>As Web3 infrastructure matures, more teams are questioning a default assumption: &#8220;should RPC always be managed by a third party?&#8221; Managed RPC platforms undeniably lower the barrier to entry. They abstract away node operations, scaling, and routing so teams can ship faster. But as applications grow, or when infrastructure becomes mission-critical, those same abstractions often [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/open-source-rpc-stack-self-hosted-vs-managed/">Open Source RPC Stack: When Self-Hosted Infrastructure Beats Managed RPC</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="3708" class="elementor elementor-3708" data-elementor-post-type="post">
				<div class="elementor-element elementor-element-50f71ae e-flex e-con-boxed e-con e-parent" data-id="50f71ae" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-3a1681f elementor-widget elementor-widget-text-editor" data-id="3a1681f" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
									<p class="p1">As Web3 infrastructure matures, more teams are questioning a default assumption:</p><p class="p1"><i>&#8220;should RPC always be managed by a third party?&#8221;</i><i></i></p><p class="p1">Managed RPC platforms undeniably lower the barrier to entry. They abstract away node operations, scaling, and routing so teams can ship faster. But as applications grow, or when infrastructure becomes mission-critical, those same abstractions often turn into constraints.</p><p class="p1">This is where <span class="s1"><b>self-hosted RPC infrastructure</b></span> comes back into focus.</p><p class="p1">In this article, we’ll explore what self-hosted RPC stacks offer that managed platforms don’t, why more teams are revisiting this model, and how <span style="text-decoration: underline;"><a href="https://drpc.org/nodecore-open-source-rpc-infrastructure"><span class="s1"><b>NodeCore</b></span></a></span>, dRPC’s open-source RPC stack, fits into that shift.</p><h2><b>Managed RPC vs Self-Hosted RPC: Where the Tradeoffs Begin</b></h2><p><img data-dominant-color="efefef" data-has-transparency="false" style="--dominant-color: #efefef;" decoding="async" class="aligncenter size-large wp-image-3709 not-transparent" src="https://drpc.org/blog/wp-content/uploads/2026/01/managed-versus-self-hoted-RPC-1024x683.webp" alt="Self-hosted RPC stack vs managed RPC architecture diagram" width="800" height="534" srcset="https://drpc.org/blog/wp-content/uploads/2026/01/managed-versus-self-hoted-RPC-1024x683.webp 1024w, https://drpc.org/blog/wp-content/uploads/2026/01/managed-versus-self-hoted-RPC-300x200.webp 300w, https://drpc.org/blog/wp-content/uploads/2026/01/managed-versus-self-hoted-RPC-768x512.webp 768w, https://drpc.org/blog/wp-content/uploads/2026/01/managed-versus-self-hoted-RPC.webp 1536w" sizes="(max-width: 800px) 100vw, 800px" /></p><p class="p1">Managed RPC services are optimized for convenience:</p><ul><li><p class="p1">One endpoint</p></li><li><p class="p1">Minimal setup</p></li><li><p class="p1">No node maintenance</p></li><li><p class="p1">Usage-based pricing</p></li></ul><p class="p1">For many teams, especially early on, this is the right choice.</p><p class="p1">However, as traffic grows and system requirements become more specific, teams often encounter recurring limitations:</p><ul><li><p class="p1"><b>Opaque routing logic</b><b></b></p><p class="p2">You don’t control how requests are balanced, retried, or failed over.</p></li><li><p class="p1"><b>Limited observability</b><b></b></p><p class="p2">Metrics are often coarse-grained, delayed, or abstracted behind dashboards you can’t extend.</p></li><li><p class="p1"><b>Vendor-defined constraints</b><b></b></p><p class="p2">Rate limits, method restrictions, or pricing tiers that don’t map cleanly to real workloads.</p></li><li><p class="p1"><b>Reduced sovereignty</b><b></b></p><p class="p2">Infrastructure decisions, from geography to redundancy models, are made externally.</p></li></ul><p class="p1">At this stage, infrastructure stops being “plumbing” and becomes part of the product itself.</p><h2><b>What a Self-Hosted RPC Stack Actually Gives You</b></h2><p class="p1">A self-hosted RPC stack flips the model.</p><p class="p1">Instead of adapting your system to a provider’s architecture, you adapt the infrastructure to <span class="s1"><b>your</b></span> needs.</p><p class="p1">Key advantages include:</p><h3><b>Full Control Over Routing Logic</b></h3><p class="p1">Self-hosting means you decide:</p><ul><li><p class="p1">How requests are distributed across nodes</p></li><li><p class="p1">How failover works</p></li><li><p class="p1">Which nodes serve which methods</p></li><li><p class="p1">How latency, sync state, or block height affect routing</p></li></ul><p class="p1">This is especially valuable for teams running:</p><ul><li><p class="p1">Latency-sensitive applications</p></li><li><p class="p1">Read-heavy workloads</p></li><li><p class="p1">Region-specific traffic</p></li><li><p class="p1">Internal tools with strict guarantees</p></li></ul><h3><b>First-Class Observability</b></h3><p class="p1">With a self-hosted stack, observability isn’t an add-on, it’s part of the architecture.</p><p class="p1">You can:</p><ul><li><p class="p1">Instrument at the RPC method level</p></li><li><p class="p1">Trace requests end-to-end</p></li><li><p class="p1">Correlate infra metrics with application behavior</p></li><li><p class="p1">Feed data directly into your own monitoring and alerting systems</p></li></ul><p class="p1">This level of visibility is hard to achieve with black-box managed services.</p><h3><b>Infrastructure Sovereignty</b></h3><p class="p1">Self-hosting allows you to:</p><ul><li><p class="p1">Choose node providers</p></li><li><p class="p1">Control geographic distribution</p></li><li><p class="p1">Mix your own nodes with third-party ones</p></li><li><p class="p1">Avoid hard dependencies on a single vendor</p></li></ul><p class="p1">For teams operating in regulated environments, or those building critical financial infrastructure, this sovereignty isn’t a “nice to have”. It is a requirement.</p><h2><b>Introducing NodeCore: dRPC’s Open-Source Self-Hosted RPC Stack</b></h2><p class="p1"><span class="s1"><b>NodeCore</b></span> is dRPC’s answer to teams that want the benefits of self-hosted RPC infrastructure without rebuilding everything from scratch.</p><p class="p1">NodeCore is:</p><ul><li><p class="p1"><b>Open source</b><b></b></p></li><li><p class="p1"><b>Self-hosted</b><b></b></p></li><li><p class="p1"><b>Designed specifically for RPC routing and proxying</b><b></b></p></li><li><p class="p1"><b>Focused on EVM JSON-RPC workloads</b></p></li></ul><p class="p1">Rather than being a general-purpose node manager, NodeCore is intentionally scoped to do one thing well<b>, </b>and that&#8217;s to <b>act as a smart, transparent RPC layer you fully control.</b></p><p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f449.png" alt="👉" class="wp-smiley" style="height: 1em; max-height: 1em;" /> <span class="s1"><b>Github repository:</b></span> <span style="text-decoration: underline;"><a href="https://github.com/drpcorg/nodecore" target="_blank" rel="noopener">https://github.com/drpcorg/nodecore</a></span></p><p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f449.png" alt="👉" class="wp-smiley" style="height: 1em; max-height: 1em;" /> <span class="s1"><b>Documentation:</b></span> <span style="text-decoration: underline;"><a href="https://drpc.org/docs/nodecore">https://drpc.org/docs/nodecore</a></span></p><h2><b>A Focused Design Philosophy (and Why That Matters)</b></h2><p class="p1">One of the most common failures in infrastructure tooling is overreach. Projects try to solve every possible problem and end up difficult to operate, reason about, or extend.</p><p class="p1">NodeCore takes the opposite approach.</p><p class="p1">As the team at <a href="https://www.nethermind.io/" target="_blank" rel="noopener"><span class="s3"><b><span style="text-decoration: underline;">Nethermind</span></b></span></a> noted after testing the project:</p><blockquote><p><i>“At Nethermind, we enjoyed testing the NodeCore open source project and appreciate its simplicity from the beginning. It addresses common EVM JSON RPC smart proxying challenges in small environments with just the right set of features, nothing more and nothing less. We hope it maintains this focused approach as it grows, and we’re excited to see where the project goes.”</i></p></blockquote><blockquote><p>— Team Angkor, <span style="text-decoration: underline;"><a href="https://www.nethermind.io/" target="_blank" rel="noopener">Nethermind</a></span></p></blockquote><p class="p1">That “nothing more and nothing less” philosophy is deliberate.</p><p class="p1">NodeCore focuses on:</p><ul><li><p class="p1">Smart RPC proxying</p></li><li><p class="p1">Deterministic routing behavior</p></li><li><p class="p1">Operational clarity</p></li><li><p class="p1">Minimal moving parts</p></li></ul><p class="p1">This makes it particularly attractive for:</p><ul><li><p class="p1">Teams building internal platforms</p></li><li><p class="p1">Foundations or infra teams that want control without complexity</p></li></ul><h2><b>Where NodeCore Fits Best Today</b></h2><p class="p1">NodeCore is not a replacement for every managed RPC use case, and it’s not meant to be.</p><p class="p1">It shines when:</p><ul><li><p class="p1"><span class="s1">You want </span><b>control without vendor lock-in</b><b></b></p></li><li><p class="p1"><span class="s1">You need </span><b>predictable RPC behavior</b><b></b></p></li><li><p class="p1">You care about <span class="s1"><b>how</b></span> requests are routed, not just that they succeed</p></li><li><p class="p1">You’re building infrastructure as part of your product, not just consuming it</p></li></ul><p class="p1">Common scenarios include:</p><ul><li><p class="p1">Internal RPC gateways for engineering teams</p></li><li><p class="p1">Custom routing in front of multiple node providers</p></li><li><p class="p1">Testnet or staging environments with production-like behavior</p></li><li><p class="p1">Early foundations of larger, sovereign infra stacks</p></li></ul><h2><b>Open Source as a Strategic Choice</b></h2><p class="p1">NodeCore being open source isn’t just a licensing decision. It is an architectural one.</p><p class="p1">Open source enables:</p><ul><li><p class="p1">Auditable behavior (critical for infra)</p></li><li><p class="p1">Community feedback and extensions</p></li><li><p class="p1">Internal forks and customization</p></li><li><p class="p1">Long-term confidence that the stack won’t disappear behind a pricing change</p></li></ul><p class="p1">It also aligns with a broader shift we’re seeing across Web3, and that&#8217;s that teams increasingly want <span class="s1"><b>composable, inspectable infrastructure</b></span>, not opaque APIs.</p><h2><b>How NodeCore Relates to dRPC’s Broader Stack</b></h2><p class="p1">It’s worth being explicit: NodeCore doesn’t replace dRPC’s managed offerings.</p><p class="p1">Instead, it complements them.</p><p class="p1">Many teams:</p><ul><li><p class="p1">Start with managed RPC to move fast</p></li><li><p class="p1">Adopt NodeCore when infra becomes strategic</p></li><li><p class="p1">Combine self-hosted and decentralized RPC approaches over time</p></li></ul><p class="p1">This flexibility is intentional. dRPC isn’t pushing a single “right” model, but it’s supporting the full spectrum from convenience to sovereignty.</p><h2><b>Getting Started with NodeCore</b></h2><p class="p1">If you’re curious to explore NodeCore:</p><ul><li><p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f4d8.png" alt="📘" class="wp-smiley" style="height: 1em; max-height: 1em;" /> <span class="s1"><b>Documentation:</b></span> <span style="text-decoration: underline;"><a href="https://drpc.org/docs/nodecore">https://drpc.org/docs/nodecore</a></span></p></li><li><p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f9e9.png" alt="🧩" class="wp-smiley" style="height: 1em; max-height: 1em;" /> <span class="s1"><b>Source code:</b></span> <span style="text-decoration: underline;"><a href="https://github.com/drpcorg/nodecore" target="_blank" rel="noopener">https://github.com/drpcorg/nodecore</a></span></p></li></ul><p class="p1">And if you’re evaluating whether a self-hosted RPC stack makes sense for your team or ecosystem:</p><p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f449.png" alt="👉" class="wp-smiley" style="height: 1em; max-height: 1em;" /> <a href="mailto:craci@drpc.org"><span style="text-decoration: underline;"><span class="s1"><b>Get in touch with the dRPC team</b></span></span></a> for deeper technical discussions, architecture reviews, or guidance on hybrid setups.</p><h2><b>Final Thoughts</b></h2><p class="p1">Managed RPC platforms are excellent at solving common problems.</p><p class="p1">Self-hosted RPC stacks are about solving <span class="s1"><b>your</b></span> problems.</p><p class="p1">NodeCore exists for teams that have reached the point where routing logic, observability, and infrastructure choices are no longer abstract concerns, but core product decisions.</p><p class="p1">If that sounds familiar, it’s probably time to look under the hood.</p>								</div>
					</div>
				</div>
				</div>
		<p>The post <a rel="nofollow" href="https://drpc.org/blog/open-source-rpc-stack-self-hosted-vs-managed/">Open Source RPC Stack: When Self-Hosted Infrastructure Beats Managed RPC</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Monad Mainnet RPC Endpoints Now Available via dRPC NodeCloud</title>
		<link>https://drpc.org/blog/monad-mainnet-rpc-endpoints/</link>
		
		<dc:creator><![CDATA[dRPC Team]]></dc:creator>
		<pubDate>Mon, 24 Nov 2025 12:00:00 +0000</pubDate>
				<category><![CDATA[APIs]]></category>
		<category><![CDATA[Product]]></category>
		<category><![CDATA[mainnet]]></category>
		<category><![CDATA[monad]]></category>
		<guid isPermaLink="false">https://drpc.org/blog/?p=3441</guid>

					<description><![CDATA[<p>As the Monad blockchain officially launches its long-anticipated mainnet on November 24, developers building on Monad can now count on dRPC for fast, reliable, and scalable Monad mainnet RPC endpoints — live from day one. dRPC is proud to support the Monad mainnet launch with public RPC endpoints available across both free and paid NodeCloud [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/monad-mainnet-rpc-endpoints/">Monad Mainnet RPC Endpoints Now Available via dRPC NodeCloud</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p class="p1">As the Monad blockchain officially launches its long-anticipated mainnet on November 24, developers building on Monad can now count on dRPC for fast, reliable, and scalable Monad mainnet RPC endpoints — live from day one.</p>
<p class="p1">dRPC is proud to support the <span class="s1"><b>Monad mainnet launch</b></span> with public RPC endpoints available across both free and paid <span class="s1"><b>NodeCloud</b></span> accounts. Whether you’re testing or scaling in production, our infrastructure gives you the confidence to deploy with low latency, zero downtime, and no surprises.</p>
<p class="p3"><span class="s2">→ <a href="https://drpc.org/chainlist/monad"><span class="s3"><b><span style="text-decoration: underline;">Access Monad Mainnet RPC</span></b></span></a></span></p>
<h2><b>What Is Monad?</b></h2>
<p class="p3"><span style="text-decoration: underline;"><span class="s2"><a href="https://monad.xyz/" target="_blank" rel="noopener"><b>Monad</b></a></span></span> is a new Layer 1 blockchain that reimagines Ethereum compatibility through a radical focus on parallel execution, low-latency performance, and full EVM equivalence.</p>
<p class="p3">Monad’s core differentiator lies in its <span class="s4"><b>parallel optimistic execution engine</b></span> — capable of running thousands of smart contract operations simultaneously while preserving full determinism. Instead of single-threaded execution like on Ethereum, Monad breaks blocks into transaction DAGs, maximizing throughput without compromising EVM behavior.</p>
<p class="p3">Combined with its custom consensus (HotStuff-based), transaction parallelization, and end-to-end pipelining, Monad is pushing the frontier on what performant L1 chains can deliver to developers today.</p>
<p class="p3">With Monad mainnet now live, builders finally have access to a next-gen EVM chain that delivers:</p>
<ul>
<li>
<p class="p1">True parallel execution</p>
</li>
<li>
<p class="p1">Near-instant finality</p>
</li>
<li>
<p class="p1">Full Solidity + EVM compatibility</p>
</li>
<li>
<p class="p1">Built-in composability with existing toolchains</p>
</li>
</ul>
<p><img data-dominant-color="ededed" data-has-transparency="false" style="--dominant-color: #ededed;" loading="lazy" decoding="async" class="alignnone wp-image-3443 not-transparent" src="https://drpc.org/blog/wp-content/uploads/2025/11/monad-architecture-drpc-blog-300x300.webp" alt="Monad mainnet rpc endpoints" width="492" height="492" srcset="https://drpc.org/blog/wp-content/uploads/2025/11/monad-architecture-drpc-blog-300x300.webp 300w, https://drpc.org/blog/wp-content/uploads/2025/11/monad-architecture-drpc-blog-150x150.webp 150w, https://drpc.org/blog/wp-content/uploads/2025/11/monad-architecture-drpc-blog.webp 480w" sizes="(max-width: 492px) 100vw, 492px" /></p>
<h2><b>Why Monad Matters for Builders</b></h2>
<p class="p1">For developers, Monad unlocks a rare combination: the speed and scale of a high-performance execution layer with the familiarity and tooling of the EVM. Its parallelism model means smart contracts no longer compete for block space, and composability isn’t sacrificed for speed.</p>
<p class="p1">This makes Monad ideal for apps that need high throughput and reliability — like onchain trading engines, liquid staking platforms, or prediction markets with real-time user interaction. And because Monad maintains strict EVM equivalence, developers can migrate existing codebases or use standard Solidity libraries and tooling without rewriting for a custom VM.</p>
<p class="p1">In a crowded L1 landscape, Monad stands out by solving for performance <i>without</i> breaking developer expectations — giving teams confidence to deploy at scale.</p>
<h2><b>Monad RPC: Powered by NodeCloud</b></h2>
<p class="p3">dRPC provides ready-to-use <span class="s2"><b>Monad mainnet RPC endpoints</b></span>, instantly available through <span class="s2"><b>NodeCloud</b></span>, our infrastructure platform trusted by high-performance L1s, L2s, and appchains.</p>
<p class="p3">You can start building today without spinning up your own nodes — whether on a <span class="s2"><b>free account</b></span> or scaling traffic via a <span class="s2"><b>paid plan</b></span> with zero rate limits.</p>
<p class="p3">With NodeCloud, you get:</p>
<ul>
<li>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/26a1.png" alt="⚡" class="wp-smiley" style="height: 1em; max-height: 1em;" /> AI-powered load balancing</p>
</li>
<li>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f30d.png" alt="🌍" class="wp-smiley" style="height: 1em; max-height: 1em;" /> 9 global geo clusters</p>
</li>
<li>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f504.png" alt="🔄" class="wp-smiley" style="height: 1em; max-height: 1em;" /> Auto-failover and routing logic</p>
</li>
<li>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f517.png" alt="🔗" class="wp-smiley" style="height: 1em; max-height: 1em;" /> 180+ network RPCs under one interface</p>
</li>
<li>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f4ca.png" alt="📊" class="wp-smiley" style="height: 1em; max-height: 1em;" /> Access to logs, usage metrics, and observability</p>
</li>
<li>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f193.png" alt="🆓" class="wp-smiley" style="height: 1em; max-height: 1em;" /> Free plans + flat-rate paid plans from $10/month</p>
</li>
</ul>
<p class="p4"><span class="s3">→ <span style="text-decoration: underline;"><a href="https://drpc.org/chainlist/monad"><span class="s4"><b>Get started with Monad RPC</b></span></a></span></span><b></b><b></b></p>
<p class="p4"><span class="s3">→ <a href="https://drpc.org/nodecloud-multichain-rpc-management"><span class="s4"><b><span style="text-decoration: underline;">Explore NodeCloud</span></b></span></a></span><b></b></p>
<h2><b>Ready for Mainnet? Let’s Build.</b></h2>
<p class="p1">Monad’s mainnet launch signals more than just another L1 going live — it’s the arrival of a new design pattern for scaling Ethereum-style smart contracts with real performance gains.</p>
<p class="p1">dRPC’s support for Monad mainnet rpc endpoints means you can skip node ops and backend bottlenecks, and instead plug directly into high-performance RPC from day one — whether you’re building:</p>
<ul>
<li>
<p class="p1">A perpetuals DEX needing real-time updates</p>
</li>
<li>
<p class="p1">An NFT marketplace with high mint volume</p>
</li>
<li>
<p class="p1">A DeFi protocol exploring cross-chain liquidity</p>
</li>
<li>
<p class="p1">Or a data-heavy analytics tool leveraging DAG structure</p>
</li>
</ul>
<p class="p1">With dRPC’s NodeCloud platform, builders on Monad get reliability, routing intelligence, and infrastructure that scales as fast as Monad’s blocks.</p>
<p class="p4"><span class="s2">→ <a href="https://drpc.org/chainlist/monad"><span class="s3"><b><span style="text-decoration: underline;">Access the Monad RPC endpoint</span></b></span></a></span><b></b><b></b></p>
<p class="p4"><span class="s2">→<span style="text-decoration: underline;"> <a href="https://drpc.org/nodecloud-multichain-rpc-management"><span class="s3"><b>Build with NodeCloud</b></span></a></span></span><b></b><b></b></p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/monad-mainnet-rpc-endpoints/">Monad Mainnet RPC Endpoints Now Available via dRPC NodeCloud</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Custom RPC Infrastructure Without the Overhead</title>
		<link>https://drpc.org/blog/custom-rpc-infrastructure/</link>
		
		<dc:creator><![CDATA[Fito Benitez]]></dc:creator>
		<pubDate>Mon, 20 Oct 2025 16:34:09 +0000</pubDate>
				<category><![CDATA[Product]]></category>
		<category><![CDATA[custom]]></category>
		<category><![CDATA[NodeCraft]]></category>
		<guid isPermaLink="false">https://drpc.org/blog/?p=3281</guid>

					<description><![CDATA[<p>When open-source alone isn’t enough, NodeCraft, dRPC&#8217;s custom RPC infrastructure fills the gap. NodeCraft by dRPC delivers tailored RPC infrastructure built on the modular NodeCore stack — optimized for your architecture, use cases, and traffic profile. From custom routing to observability pipelines, we help dApps, chains, and infra teams deploy exactly what they need — [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/custom-rpc-infrastructure/">Custom RPC Infrastructure Without the Overhead</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p class="p1">When open-source alone isn’t enough, NodeCraft, dRPC&#8217;s custom RPC infrastructure fills the gap.</p>
<p class="p1">NodeCraft by dRPC delivers <span class="s1"><b>tailored RPC infrastructure</b></span> built on the modular <a href="https://drpc.org/docs/nodecore">NodeCore</a> stack — optimized for your architecture, use cases, and traffic profile. From custom routing to observability pipelines, we help dApps, chains, and infra teams deploy exactly what they need — without spinning up an internal RPC division.</p>
<h2><b>Why You Might Need Custom RPC Infrastructure</b></h2>
<p class="p1">You could build it yourself… but should you?</p>
<p class="p1">Many teams start with off-the-shelf RPC solutions or self-host the open-source <a href="https://drpc.org/docs/nodecore">NodeCore</a> stack. But when <span class="s1"><b>security</b></span>, <span class="s1"><b>compliance</b></span>, or <span class="s1"><b>specialised routing</b></span> become critical, extending the stack requires time, expertise, and ongoing maintenance.</p>
<p class="p1">That’s where NodeCraft comes in.</p>
<p class="p1">It’s a service for teams who know what they want — but not how to build it fast or securely enough.</p>
<h3 class="p4"><b>With NodeCraft, you can:</b><b></b></h3>
<ol start="1">
<li>
<p class="p1">Meet compliance and security requirements with expert-built extensions.</p>
</li>
<li>
<p class="p1">Offload integration work that your team doesn’t have bandwidth for.</p>
</li>
<li>
<p class="p1">Deploy custom routing logic inside your infrastructure.</p>
</li>
<li>
<p class="p1">Add observability without building it from scratch.</p>
</li>
<li>
<p class="p1">Connect internal systems with a modular RPC gateway — without deep custom dev.</p>
</li>
</ol>
<h2><b>What NodeCraft Customises</b></h2>
<p class="p1">No two dApps or chains are the same. NodeCraft gives you the flexibility to adapt the RPC stack to your unique requirements.</p>
<p class="p4">Popular <strong>customisation modules</strong> include:</p>
<ul>
<li>
<p class="p1"><span class="s1"><b>Custom Auth Systems</b></span> — Integrate with your internal auth, usage limits, or billing logic.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Advanced Monitoring &amp; Alerts</b></span> — Custom Grafana dashboards, Prometheus integration, webhook alerts, or log pipelines.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Geographic Routing + Regional Scaling</b></span> — Ideal for teams deploying NodeCraft in multiple regions.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Provider Preference Logic</b></span> — Route traffic based on latency, geography, or even business constraints.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Multi-Tenant Access Management</b></span> — Isolated API keys and per-user tracking for ecosystems or multi-product apps.</p>
</li>
</ul>
<h2><b>Example Use Cases</b></h2>
<p class="p1">Here’s how real teams are using NodeCraft today:</p>
<ul>
<li>
<p class="p1"><span class="s1"><b>Dynamic Fallback System</b></span> – A high-throughput DeFi dApp deployed with per-region fallbacks for maximum uptime.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Low-Latency Game Routing</b></span> – A Web3 game studio needed low-latency performance for users in Asia and Europe.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Regional Rollup Scaling</b></span> – A chain-integrated regional failover and scaling with NodeCraft deployments in 3 data centres.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Real-Time Usage Enforcement</b></span> – A DePIN protocol built custom auth + alerting for API abuse prevention.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Deep Observability</b></span> – A rollup used NodeCraft to track uptime, errors, and node/provider distribution in Grafana.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>On-Prem Compliance Setup</b></span> – A compliance-heavy protocol runs NodeCraft on-prem with internal log routing and alerting.</p>
</li>
</ul>
<h2><b>How It Works</b></h2>
<p class="p1">Working with NodeCraft custom RPC infrastructure is simple and fast.</p>
<ol start="1">
<li>
<p class="p1"><span class="s1"><b>Discovery Call</b></span> – Share your requirements.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Proposal + Estimate</b></span> – We define the scope and budget.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Implementation</b></span> – We build it in close collaboration.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Delivery + Optimisation</b></span> – Production-ready, with testing and tuning.</p>
</li>
</ol>
<h2><b>Frequently Asked Questions</b></h2>
<h3 class="p4"><b>What’s the difference between NodeCore and NodeCraft?</b><b></b></h3>
<p class="p1">NodeCore is dRPC’s <span class="s1"><b>open source, self‑hosted RPC load balancer</b></span> — modular, chain‑agnostic, and designed for teams who want full control of their RPC stack. It’s the same <span class="s1"><b>battle‑tested engine</b></span> that powers thousands of requests per second across the dRPC ecosystem, giving developers a proven foundation to self‑host at scale.</p>
<p class="p1">NodeCraft builds <span class="s1"><b>on top of NodeCore</b></span>, offering <span class="s1"><b>custom modules, expert integrations, and deployment support</b></span> for teams that need more than a standard setup. While NodeCore is open and community‑driven, NodeCraft delivers production‑grade extensions — tailored auth systems, observability stacks, and routing logic — built and tuned by the same engineers who maintain the NodeCore codebase.</p>
<h3 class="p4"><b>Can we deploy NodeCraft custom RPC infrastructure in multiple regions?</b><b></b></h3>
<p class="p1">Yes. NodeCraft is <span class="s1"><b>built for multi‑region and latency‑aware scaling</b></span> from day one. You can deploy it in multiple data centers worldwide and route traffic automatically to the lowest‑latency endpoint. Regional failover, traffic segmentation, and capacity planning are part of the design — ensuring your dApp remains fast and resilient wherever your users are.</p>
<p class="p1">Like all dRPC products, NodeCraft’s routing stack is <span class="s1"><b>battle‑tested under real‑world traffic</b></span> from high‑TPS dApps and rollups. You get the reliability of global RPC infrastructure, tuned for your specific geography and usage patterns.</p>
<h3 class="p4"><b>Can we manage the infrastructure ourselves?</b><b></b></h3>
<p class="p1">Absolutely. NodeCraft offers <span class="s1"><b>three operational models</b></span> to fit your internal capabilities:</p>
<ul>
<li>
<p class="p1"><span class="s1"><b>Fully managed:</b></span> dRPC handles everything — infra, scaling, monitoring, and updates — so your team focuses purely on development.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Co‑managed:</b></span> We build and deploy, then collaborate on tuning and scaling over time.</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Self‑hosted handoff:</b></span> We implement and document the setup, then hand it off for your internal team to operate independently.</p>
</li>
</ul>
<p class="p1">All deployment models inherit dRPC’s <span class="s1"><b>battle‑tested performance layer</b></span>, ensuring that even self‑managed environments start from a proven, production‑ready baseline.</p>
<h3 class="p4"><b>What kinds of teams use NodeCraft?</b><b></b></h3>
<p class="p1">NodeCraft is used by <span class="s1"><b>teams that outgrow generic RPC solutions</b></span> and need custom RPC infrastructure — typically those running <span class="s1"><b>mission‑critical or high‑throughput workloads</b></span> where control, reliability, and security are non‑negotiable.</p>
<ul>
<li>
<p class="p1"><span class="s1"><b>High‑traffic dApps</b></span> needing predictable performance under extreme load</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Rollups and chains</b></span> requiring fine‑tuned observability or regional scaling</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Gaming and DePIN protocols</b></span> needing low‑latency, geo‑optimized routing</p>
</li>
<li>
<p class="p1"><span class="s1"><b>Enterprise or compliance‑heavy projects</b></span> that must host internally with strict access and audit layers</p>
</li>
</ul>
<p class="p1">These teams choose NodeCraft because it combines <span class="s1"><b>custom flexibility</b></span> with a <span class="s1"><b>battle‑tested core</b></span> — the same stack that keeps dRPC’s global RPC network running smoothly across dozens of chains and billions of monthly requests.</p>
<h2><b>Let’s Build Something Better</b></h2>
<blockquote><p><i>“We had strict security requirements, so NodeCore was the only real option. NodeCraft’s custom implementations helped us avoid spinning up an expensive internal infra team.”</i><i></i></p></blockquote>
<p class="p1">Custom RPC infrastructure doesn’t have to be painful.</p>
<p class="p1">Let’s scope your custom infra → <a href="https://calendly.com/craci-drpc/with-craci-on-the-record" target="_blank" rel="noopener">Book a call</a></p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/custom-rpc-infrastructure/">Custom RPC Infrastructure Without the Overhead</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>dRPC Launches as Official Plasma RPC Provider</title>
		<link>https://drpc.org/blog/drpc-plasma-rpc-launch/</link>
		
		<dc:creator><![CDATA[Fito Benitez]]></dc:creator>
		<pubDate>Mon, 29 Sep 2025 12:47:29 +0000</pubDate>
				<category><![CDATA[Partnerships]]></category>
		<category><![CDATA[Product]]></category>
		<category><![CDATA[plasma]]></category>
		<category><![CDATA[RPC]]></category>
		<guid isPermaLink="false">https://drpc.org/blog/?p=3252</guid>

					<description><![CDATA[<p>dRPC Powers Plasma Builders with High-Performance RPC Endpoints We’re thrilled to announce that dRPC has become an official Plasma RPC partner, a high-performance Layer 1 blockchain purpose-built for stablecoins. This partnership ensures that developers building on Plasma can access reliable, performant, and scalable RPC endpoints, accelerating their ability to deploy applications securely and efficiently. About [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/drpc-plasma-rpc-launch/">dRPC Launches as Official Plasma RPC Provider</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1 class="p1">dRPC Powers Plasma Builders with High-Performance RPC Endpoints</h1>
<p>We’re thrilled to announce that dRPC has become an official <a href="https://www.plasma.to/" target="_blank" rel="noopener">Plasma</a> RPC partner, a high-performance Layer 1 blockchain purpose-built for stablecoins. This partnership ensures that developers building on Plasma can access reliable, performant, and scalable RPC endpoints, accelerating their ability to deploy applications securely and efficiently.</p>
<h2 class="p1">About Plasma: EVM-Compatible Blockchain for Stablecoins</h2>
<p>Plasma is designed from the ground up for stablecoins, powering near-instant, fee-free payments with institutional-grade security. With block times under one second and the ability to handle thousands of transactions per second, Plasma is revolutionising the way money moves in the digital economy. The network already supports over 15 stablecoins globally and is backed by notable institutions, including Bitfinex, Founders Fund, and Flow Traders.</p>
<h2 class="p1">dRPC as Official RPC Provider: Reliable Infrastructure for Builders</h2>
<p>As an RPC partner, dRPC ensures Plasma’s blockchain is accessible with <strong>high-performance RPC endpoints</strong>. This allows builders to:</p>
<ul>
<li>Connect securely to the network</li>
<li>Test and deploy smart contracts efficiently</li>
<li>Scale applications without bottlenecks</li>
</ul>
<h2>Key Features of Plasma RPC Endpoints from dRPC</h2>
<p>With dRPC powering the RPC layer, developers gain <strong>granular control, reliability, and speed</strong>, enabling a better overall experience when building on Plasma. This collaboration reinforces Plasma’s commitment to providing robust infrastructure for stablecoin projects and positions developers to innovate confidently in the growing digital financial ecosystem.</p>
<h2 class="p1">Getting Started with Your Plasma RPC Endpoint</h2>
<p>Visit our Plasma page to learn more: <a href="https://drpc.org/chainlist/plasma-mainnet-rpc">https://drpc.org/chainlist/plasma-mainnet-rpc</a></p>
<p>Access the endpoints directly: <a href="https://plasma.drpc.org">https://plasma.drpc.org</a></p>
<p>Through this partnership, dRPC continues its mission to provide <strong>battle-tested, scalable, and developer-friendly RPC infrastructure</strong> for leading Layer 1 networks. We look forward to supporting the Plasma ecosystem as it expands globally and powers the next generation of stablecoin applications.</p>
<p><!-- notionvc: 03673163-ac6e-4bb3-a1c4-adbf2780b5dd --></p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/drpc-plasma-rpc-launch/">dRPC Launches as Official Plasma RPC Provider</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Choosing the Right RPC Infrastructure: A Guide to dRPC’s Product Stack</title>
		<link>https://drpc.org/blog/rpc-infrastructure-comparison/</link>
		
		<dc:creator><![CDATA[Fito Benitez]]></dc:creator>
		<pubDate>Fri, 12 Sep 2025 11:59:19 +0000</pubDate>
				<category><![CDATA[Product]]></category>
		<category><![CDATA[NodeCloud]]></category>
		<category><![CDATA[NodeCore]]></category>
		<category><![CDATA[NodeCraft]]></category>
		<category><![CDATA[NodeHaus]]></category>
		<category><![CDATA[product suite]]></category>
		<category><![CDATA[RPC infrastructure]]></category>
		<guid isPermaLink="false">https://drpc.org/blog/?p=3248</guid>

					<description><![CDATA[<p>As the demand for scalable, reliable, and customizable RPC infrastructure grows across Web3, choosing the right stack can make or break your application’s performance. At dRPC, we’ve designed a modular suite of RPC products tailored to developers, chains, and enterprises at different stages of their infrastructure journey. This guide breaks down the key differences across [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/rpc-infrastructure-comparison/">Choosing the Right RPC Infrastructure: A Guide to dRPC’s Product Stack</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p class="p1">As the demand for scalable, reliable, and customizable <span class="s1"><b>RPC infrastructure</b></span> grows across Web3, choosing the right stack can make or break your application’s performance. At dRPC, we’ve designed a modular suite of RPC products tailored to developers, chains, and enterprises at different stages of their infrastructure journey.</p>
<p class="p1">This guide breaks down the key differences across <span class="s1"><b>NodeCloud</b></span>, <span class="s1"><b>NodeCore</b></span>, <span class="s1"><b>NodeCraft</b></span>, and <span class="s1"><b>NodeHaus</b></span>—so you can select the RPC solution that fits your performance, hosting, and customization needs.</p>
<hr />
<h2><b>NodeCloud: Plug-and-Play RPC for Startups and Growing dApps</b></h2>
<p class="p3"><span class="s2"><b>NodeCloud</b></span> is our fully managed RPC solution for dApps that want fast, reliable infrastructure without managing any nodes.</p>
<table style="height: 503px;" width="540">
<thead>
<tr>
<th>
<p class="p1"><b>Feature</b></p>
</th>
<th>
<p class="p1"><b>Details</b></p>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<p class="p1"><b>Organization</b></p>
</td>
<td>
<p class="p1">dApps</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Hosting</b></p>
</td>
<td>
<p class="p1">Fully hosted by dRPC</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Customization</b></p>
</td>
<td>
<p class="p1">None</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Best For</b></p>
</td>
<td>
<p class="p1">Startups and small/medium apps</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Chain Support</b></p>
</td>
<td>
<p class="p1">100+ supported chains out of the box</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>AI Load Balancing</b></p>
</td>
<td>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /> Enabled</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Pricing</b></p>
</td>
<td>
<p class="p1">Flat-rate, pay-as-you-go</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Other</b></p>
</td>
<td>
<p class="p1">Unlimited keys, no infra required</p>
</td>
</tr>
</tbody>
</table>
<p><strong>TAKE-AWAY</strong>: If you’re launching or scaling a dApp and need fast RPC access to multiple chains without operational complexity, <span class="s1">NodeCloud</span> gives you a ready-to-use endpoint with high reliability and built-in AI-based load balancing.</p>
<hr />
<h2><b>NodeCore: Self-Hosted RPC Infrastructure, Fully in Your Control</b></h2>
<p class="p3"><span class="s2"><b>NodeCore</b></span> is our open-source RPC layer designed for dev teams and foundations that prefer to self-host and maintain full control of their stack.</p>
<table style="height: 508px;" width="537">
<thead>
<tr>
<th>
<p class="p1"><b>Feature</b></p>
</th>
<th>
<p class="p1"><b>Details</b></p>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<p class="p1"><b>Organization</b></p>
</td>
<td>
<p class="p1">dApps &amp; Chains</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Hosting</b></p>
</td>
<td>
<p class="p1">Self-hosted (open source)</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Customization</b></p>
</td>
<td>
<p class="p1">High (built in-house)</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Best For</b></p>
</td>
<td>
<p class="p1">Teams with existing infrastructure</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Chain Support</b></p>
</td>
<td>
<p class="p1">Modular for all EVM-compatible chains</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>AI Load Balancing</b></p>
</td>
<td>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /> (via plugin or custom router)</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Pricing</b></p>
</td>
<td>
<p class="p1">Free (OSS license)</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Other</b></p>
</td>
<td>
<p class="p1">Plug-and-play, chain-agnostic RPC layer</p>
</td>
</tr>
</tbody>
</table>
<p><strong>TAKE-AWAY</strong>: NodeCore offers <span class="s1">maximum flexibility</span> with a modular architecture and optional plugins for load balancing and performance optimization. Ideal for advanced teams looking to own and operate their own RPC infrastructure.</p>
<hr />
<h2><b>NodeCraft: Bespoke RPC Infrastructure for Advanced Use Cases</b></h2>
<p class="p3">Need tailored infrastructure for enterprise-level or compliance-heavy use cases? <span class="s2"><b>NodeCraft</b></span> delivers custom self-hosted RPC solutions, designed and deployed by dRPC’s expert team.</p>
<table style="height: 512px;" width="544">
<thead>
<tr>
<th>
<p class="p1"><b>Feature</b></p>
</th>
<th>
<p class="p1"><b>Details</b></p>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<p class="p1"><b>Organization</b></p>
</td>
<td>
<p class="p1">dApps &amp; Chains</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Hosting</b></p>
</td>
<td>
<p class="p1">Self-hosted by client</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Customization</b></p>
</td>
<td>
<p class="p1">High (via dRPC experts)</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Best For</b></p>
</td>
<td>
<p class="p1">Regulated orgs or unique compliance needs</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Chain Support</b></p>
</td>
<td>
<p class="p1">Fully configurable per project</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>AI Load Balancing</b></p>
</td>
<td>
<p class="p1">Optional (custom implementation)</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Pricing</b></p>
</td>
<td>
<p class="p1">Priced per project scope</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Other</b></p>
</td>
<td>
<p class="p1">Built on NodeCore; supports multi-region setup</p>
</td>
</tr>
</tbody>
</table>
<p><strong>TAKE-AWAY</strong>: If you’re running in multiple regions, need chain-specific compliance, or have enterprise-grade requirements, <span class="s1">NodeCraft</span> gives you all the benefits of NodeCore—customized and managed to your spec.</p>
<hr />
<h2><b>NodeHaus: Turnkey RPC Infrastructure for Foundations and Chains</b></h2>
<p class="p3"><span class="s2"><b>NodeHaus</b></span> is a hosted infrastructure solution purpose-built for blockchain foundations and protocol teams that need a turnkey RPC layer.</p>
<table style="height: 513px;" width="704">
<thead>
<tr>
<th>
<p class="p1"><b>Feature</b></p>
</th>
<th>
<p class="p1"><b>Details</b></p>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<p class="p1"><b>Organization</b></p>
</td>
<td>
<p class="p1">Chains / Foundations</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Hosting</b></p>
</td>
<td>
<p class="p1">Fully hosted by dRPC</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Customization</b></p>
</td>
<td>
<p class="p1">Medium (via modular components)</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Best For</b></p>
</td>
<td>
<p class="p1">Foundations launching RPC infrastructure</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Chain Support</b></p>
</td>
<td>
<p class="p1">Chain-specific RPC + third-party integrations</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>AI Load Balancing</b></p>
</td>
<td>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /> Enabled</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Pricing</b></p>
</td>
<td>
<p class="p1">Flat-rate enterprise plans</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>Other</b></p>
</td>
<td>
<p class="p1">Includes dashboard, branded faucet, observability, and 24/7 support</p>
</td>
</tr>
</tbody>
</table>
<p><strong>TAKE-AWAY</strong>: NodeHaus is ideal for chains looking to scale their ecosystem with branded, reliable infrastructure that serves their community with minimal internal ops overhead. The NodeHaus infra health dashboard is our start module, saving you $$$Ks in inhouse development and wasted resources. Check the demo tour <a href="https://youtu.be/tBAFNWMzW0E?si=A-gOic5b3-Bwmubr" target="_blank" rel="noopener">here</a>.</p>
<hr />
<h2><b>Comparing dRPC’s RPC Infrastructure Products</b></h2>
<table style="height: 285px;" width="1021">
<thead>
<tr>
<th>
<p class="p1"><b>Product</b></p>
</th>
<th>
<p class="p1"><b>Hosting Model</b></p>
</th>
<th>
<p class="p1"><b>Customization Level</b></p>
</th>
<th>
<p class="p1"><b>Best For</b></p>
</th>
<th>
<p class="p1"><b>AI Load Balancing</b></p>
</th>
<th>
<p class="p1"><b>Price</b></p>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<p class="p1"><b>NodeCloud</b></p>
</td>
<td>
<p class="p1">Hosted (by dRPC)</p>
</td>
<td>
<p class="p1">None</p>
</td>
<td>
<p class="p1">Startups and dApps</p>
</td>
<td>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
</td>
<td>
<p class="p1">Pay-as-you-go</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>NodeCore</b></p>
</td>
<td>
<p class="p1">Self-hosted (OSS)</p>
</td>
<td>
<p class="p1">High (in-house)</p>
</td>
<td>
<p class="p1">Infra-savvy teams</p>
</td>
<td>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /> (optional)</p>
</td>
<td>
<p class="p1">Free (OSS)</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>NodeCraft</b></p>
</td>
<td>
<p class="p1">Self-hosted</p>
</td>
<td>
<p class="p1">High (with dRPC)</p>
</td>
<td>
<p class="p1">Regulated or custom enterprise needs</p>
</td>
<td>
<p class="p1">Optional</p>
</td>
<td>
<p class="p1">Scoped pricing</p>
</td>
</tr>
<tr>
<td>
<p class="p1"><b>NodeHaus</b></p>
</td>
<td>
<p class="p1">Hosted (by dRPC)</p>
</td>
<td>
<p class="p1">Medium (modular)</p>
</td>
<td>
<p class="p1">Chain teams and blockchain foundations</p>
</td>
<td>
<p class="p1"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
</td>
<td>
<p class="p1">Bundle or modular</p>
</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<hr />
<h2><b>Final Thoughts: Which RPC Infrastructure Is Right for You?</b></h2>
<p class="p3">Whether you’re launching your first dApp or scaling a global blockchain network, <span class="s2"><b>dRPC’s RPC infrastructure offerings</b></span> give you the flexibility to choose between hosted ease and self-hosted control.</p>
<ul>
<li>
<p class="p1">Want instant scalability with no overhead? Go with <span class="s1"><b>NodeCloud</b></span>.</p>
</li>
<li>
<p class="p1">Building in-house and want total control? <span class="s1"><b>NodeCore</b></span> is for you.</p>
</li>
<li>
<p class="p1">Need enterprise customization and compliance? Choose <span class="s1"><b>NodeCraft</b></span>.</p>
</li>
<li>
<p class="p1">Running a chain and need full-service RPC infra? Use <span class="s1"><b>NodeHaus</b></span>.</p>
</li>
</ul>
<p class="p3">→ <a href="https://drpc.org">Learn more and get started</a></p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/rpc-infrastructure-comparison/">Choosing the Right RPC Infrastructure: A Guide to dRPC’s Product Stack</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>MEV Protection: Secure Your Transactions Now with dRPC</title>
		<link>https://drpc.org/blog/mev-protection-nodes/</link>
		
		<dc:creator><![CDATA[Fito Benitez]]></dc:creator>
		<pubDate>Fri, 22 Aug 2025 12:19:57 +0000</pubDate>
				<category><![CDATA[Product]]></category>
		<category><![CDATA[Security]]></category>
		<guid isPermaLink="false">https://drpc.org/blog/?p=3169</guid>

					<description><![CDATA[<p>MEV protection nodes are essential for safeguarding blockchain transactions against front-running, sandwich attacks, and other exploitable behaviors by validators or bots. Essentially, MEV protection ensures fair ordering, privacy, and reduced latency at the RPC layer — making your transactions more secure and predictable. Note: MEV protection is a premium feature, available only to paid users, [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/mev-protection-nodes/">MEV Protection: Secure Your Transactions Now with dRPC</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p data-start="122" data-end="450"><strong data-start="122" data-end="146">MEV protection nodes</strong> are essential for safeguarding blockchain transactions against front-running, sandwich attacks, and other exploitable behaviors by validators or bots. Essentially, MEV protection ensures fair ordering, privacy, and reduced latency at the RPC layer — making your transactions more secure and predictable.</p>
<blockquote data-start="452" data-end="492">
<p data-start="455" data-end="492"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out"><strong data-start="0" data-end="8" data-is-only-node="">Note</strong>: MEV protection is a <strong data-start="30" data-end="49">premium feature</strong>, available only to <strong data-start="69" data-end="83">paid users</strong>, starting at just <strong data-start="102" data-end="108">$1</strong> per unit.</span></p>
</blockquote>
<h2 data-start="499" data-end="542">Supported Chains &amp; Endpoint Highlights</h2>
<p data-start="544" data-end="581"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">Here’s a quick guide to all blockchains where dRPC provides MEV protection:</span></p>
<h3 data-start="588" data-end="607"><strong data-start="593" data-end="605">Ethereum</strong></h3>
<p data-start="608" data-end="754"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">The foundational smart contract blockchain with the largest DeFi ecosystem and significant MEV risk.</span><br data-start="645" data-end="648" /><strong data-start="648" data-end="672">dRPC public endpoint</strong>: <a class="decorated-link" href="https://drpc.org/chainlist/ethereum#ethereum" target="_new" rel="noopener" data-start="674" data-end="754">Ethereum RPC with MEV protection</a></p>
<h3 data-start="761" data-end="776"><strong data-start="766" data-end="774">Base</strong></h3>
<p data-start="777" data-end="911"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">Coinbase’s EVM-compatible Layer‑2 chain optimized for low-cost, high-throughput transactions.</span><br data-start="814" data-end="817" /><strong data-start="817" data-end="841">dRPC public endpoint</strong>: <a class="decorated-link" href="https://drpc.org/chainlist/base#base" target="_new" rel="noopener" data-start="843" data-end="911">Base RPC with MEV protection</a></p>
<h3 data-start="918" data-end="950"><strong data-start="923" data-end="948">BNB Smart Chain (BSC)</strong></h3>
<p data-start="951" data-end="1094"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">Binance’s fast and cost-efficient EVM-compatible chain. Widely used for DeFi, raising MEV concerns.</span><br data-start="988" data-end="991" /><strong data-start="991" data-end="1015">dRPC public endpoint</strong>: <a class="decorated-link" href="https://drpc.org/chainlist/bsc#bsc" target="_new" rel="noopener" data-start="1017" data-end="1094">BNB Smart Chain RPC with MEV protection</a></p>
<h3 data-start="918" data-end="950"><strong data-start="923" data-end="948">Arbitrum (ARB)</strong></h3>
<p data-start="951" data-end="1094"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">A significant layer 2 scaling solution for Ethereum. Widely used for DeFi.</span><br data-start="988" data-end="991" /><strong data-start="991" data-end="1015">dRPC public endpoint</strong>: <a class="decorated-link" href="https://drpc.org/chainlist/arbitrum-mainnet-rpc" target="_new" rel="noopener" data-start="1017" data-end="1094">Arbitrum RPC with MEV protection</a></p>
<h3 data-start="1443" data-end="1460"><strong data-start="1448" data-end="1458">Solana</strong></h3>
<p data-start="1461" data-end="1601"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">Designed for high throughput and minimal latency, popular for DeFi, NFTs, and on‑chain apps.</span><br data-start="1498" data-end="1501" /><strong data-start="1501" data-end="1525">dRPC public endpoint</strong>: <a class="decorated-link" href="https://drpc.org/chainlist/solana#solana" target="_new" rel="noopener" data-start="1527" data-end="1601">Solana RPC with MEV protection</a></p>
<h3 data-start="1608" data-end="1639">Why MEV Protection Matters</h3>
<p data-start="1641" data-end="1678"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">MEV — or <em data-start="9" data-end="36">Maximal Extractable Value</em> — refers to opportunities for validators, miners, or bots to reorder transactions for profit. Common forms include front-running, sandwiching, and liquidation attacks.</span></p>
<p data-start="1641" data-end="1678"><img data-dominant-color="f1f0ec" data-has-transparency="false" style="--dominant-color: #f1f0ec;" loading="lazy" decoding="async" class="alignnone size-medium wp-image-3171 not-transparent" src="https://drpc.org/blog/wp-content/uploads/2025/08/drpc-mev-protection-diagram-300x200.webp" alt="drpc-mev-protection-diagram" width="300" height="200" srcset="https://drpc.org/blog/wp-content/uploads/2025/08/drpc-mev-protection-diagram-300x200.webp 300w, https://drpc.org/blog/wp-content/uploads/2025/08/drpc-mev-protection-diagram.webp 500w" sizes="(max-width: 300px) 100vw, 300px" /></p>
<p data-start="1680" data-end="1719"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">dRPC’s <strong data-start="7" data-end="31">MEV protection nodes</strong> use techniques like:</span></p>
<ul data-start="1721" data-end="1890">
<li data-start="1721" data-end="1762">
<p data-start="1723" data-end="1762"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">Mempool obfuscation and privacy to prevent bots from seeing and exploiting transactions.</span></p>
</li>
<li data-start="1763" data-end="1804">
<p data-start="1765" data-end="1804"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">Low-latency routing to minimise the window for malicious interference.</span></p>
</li>
<li data-start="1805" data-end="1890">
<p data-start="1807" data-end="1890"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">Transparent, permissionless execution to maintain fairness and decentralisation.</span></p>
</li>
</ul>
<p data-start="1892" data-end="1973"><span class="relative -mx-px my-[-0.2rem] rounded px-px py-[0.2rem] transition-colors duration-100 ease-in-out">As explained in the <a href="https://drpc.org/docs/howitworks/mev-protection">dRPC documentation</a> (and exemplified in this <a href="https://drpc.org/blog/drpc-now-supports-stake-weighted-qos-and-mev-protection-on-solana/?utm_source=chatgpt.com">Solana-related article</a>), this layer of protection is critical for safeguarding transactions that touch DeFi, token minting, NFT drops, and more.</span><span class="" data-state="closed"><span class="ms-1 inline-flex max-w-full items-center relative top-[-0.094rem] animate-[show_150ms_ease-in]" data-testid="webpage-citation-pill"><br />
</span></span></p>
<h3 data-start="1980" data-end="1999">Final Thoughts</h3>
<ul data-start="2001" data-end="2441">
<li data-start="2001" data-end="2128">
<p data-start="2003" data-end="2128"><strong data-start="2003" data-end="2037">What are MEV protection nodes?</strong> Secure RPC endpoints that shield your transactions from front-running and extractive bots.</p>
</li>
<li data-start="2129" data-end="2204">
<p data-start="2131" data-end="2204"><strong data-start="2131" data-end="2147">Availability</strong>: Premium feature only — starts at <strong data-start="2182" data-end="2203">$1 for paid users</strong>.</p>
</li>
<li data-start="2205" data-end="2292">
<p data-start="2207" data-end="2292"><strong data-start="2207" data-end="2227">Supported chains</strong>: Ethereum, Base, BNB Smart Chain, Arbitrum, and Solana.</p>
</li>
<li data-start="2293" data-end="2441">
<p data-start="2295" data-end="2441"><strong data-start="2295" data-end="2314">Actionable step</strong>: Choose your chain above and start sending your transactions through dRPC’s MEV-protected endpoint — no code changes required.</p>
</li>
</ul>
<p>The post <a rel="nofollow" href="https://drpc.org/blog/mev-protection-nodes/">MEV Protection: Secure Your Transactions Now with dRPC</a> appeared first on <a rel="nofollow" href="https://drpc.org/blog">dRPC Blog</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
