# \#rpc

**URL:** https://forum.polkadot.network/tag/rpc/46.md

[Latest](https://forum.polkadot.network/latest.md) · [Categories](https://forum.polkadot.network/categories.md) · [Tags](https://forum.polkadot.network/tags.md)

---

## [🌐 Launched a Global RPC Network, Starting with Polkadot Asset Hub. First Step of a DePIN. 14 Locations, Lowest Latency & Cost. Benchmarks & Free Endpoints](https://forum.polkadot.network/t/launched-a-global-rpc-network-starting-with-polkadot-asset-hub-first-step-of-a-depin-14-locations-lowest-latency-cost-benchmarks-free-endpoints/17422)

<div class="topic-metadata">

**Author:** [@kukabi](https://forum.polkadot.network/u/kukabi)\
**Replies:** 9\
**Last updated:** [June 26, 2026, 10:19am UTC](https://forum.polkadot.network/t/launched-a-global-rpc-network-starting-with-polkadot-asset-hub-first-step-of-a-depin-14-locations-lowest-latency-cost-benchmarks-free-endpoints/17422 "2026-06-26T10:19:18Z")

</div>

Summary This post announces the first step of DeServe, a progressively decentralized infrastructure services network coming to Polkadot, with the launch of a global RPC network for Polkadot Asset Hub. It covers the motiv…

---

## [Reliable ETH RPC for Kusama Assethub](https://forum.polkadot.network/t/reliable-eth-rpc-for-kusama-assethub/17854)

<div class="topic-metadata">

**Author:** [@contribnet](https://forum.polkadot.network/u/contribnet)\
**Replies:** 2\
**Last updated:** [June 11, 2026, 4:13pm UTC](https://forum.polkadot.network/t/reliable-eth-rpc-for-kusama-assethub/17854 "2026-06-11T16:13:50Z")

</div>

Looking for a stable eth rpc for Kusama Assethub. The eth rpc advertised on the kusama website is: https://eth-rpc-kusama.polkadot.io/ (source: Kusama Network). That RPC went down about a week ago and I was advised via…

---

## [New JSON-RPC API mega Q&A](https://forum.polkadot.network/t/new-json-rpc-api-mega-q-a/3048)

<div class="topic-metadata">

**Author:** [@tomaka](https://forum.polkadot.network/u/tomaka)\
**Replies:** 20\
**Last updated:** [May 6, 2026, 12:54pm UTC](https://forum.polkadot.network/t/new-json-rpc-api-mega-q-a/3048 "2026-05-06T12:54:18Z")

</div>

Polkadot consists in a peer-to-peer network of so-called clients that talk to each other. In order for the owner of a node to know what happens on Polkadot, they must then communicate with their node. This is done with w…

---

## [Substrate RPC server \`CLI changes/updates\`](https://forum.polkadot.network/t/substrate-rpc-server-cli-changes-updates/11122)

<div class="topic-metadata">

**Author:** [@niklasad1](https://forum.polkadot.network/u/niklasad1)\
**Replies:** 0\
**Last updated:** [December 12, 2024, 3:50pm UTC](https://forum.polkadot.network/t/substrate-rpc-server-cli-changes-updates/11122 "2024-12-12T15:50:10Z")

</div>

Hey A while ago, #4792 was merged, and substrate now comes with a new CLI option that is called --experimental-rpc-endpoint. This is a single CLI option that can be specified several times and gives more fine-grained op…

---

## [RPC Nodes Management Tools](https://forum.polkadot.network/t/rpc-nodes-management-tools/10151)

<div class="topic-metadata">

**Author:** [@0xpcGB](https://forum.polkadot.network/u/0xpcGB)\
**Replies:** 0\
**Last updated:** [September 26, 2024, 9:10am UTC](https://forum.polkadot.network/t/rpc-nodes-management-tools/10151 "2024-09-26T09:10:23Z")

</div>

Hey, Polkadot Community! Today I’d like to tell you how to manage your RPC nodes to get the best performance and the lowest downtimes possible. We will take the GetBlock RPC node provider as an example as they support Po…

---

## [Do you need more block history in the ink env?](https://forum.polkadot.network/t/do-you-need-more-block-history-in-the-ink-env/8771)

<div class="topic-metadata">

**Author:** [@christ](https://forum.polkadot.network/u/christ)\
**Replies:** 13\
**Last updated:** [July 8, 2024, 11:22am UTC](https://forum.polkadot.network/t/do-you-need-more-block-history-in-the-ink-env/8771 "2024-07-08T11:22:56Z")

</div>

On the frontend in polkadot js, we can use api.at(block\_num) to rewind the blockchain back by up to 256 blocks (as these are stored on the RPC nodes) and essentially run functions on recent history, as if we were at that…
