Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update endpoints #6096

Merged
merged 6 commits into from
Jul 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 46 additions & 10 deletions docs/maintain/maintain-endpoints.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ keywords: [endpoints, network, connect]
slug: ../maintain-endpoints
---

import Tabs from "@theme/Tabs"; import TabItem from "@theme/TabItem";

Ideally, one may run their own node when interacting with the
[Polkadot network](https://polkadot.network/) via [Polkadot-JS Apps](https://polkadot.js.org/apps/)
or other UIs and programmatic methods. Another option would be to connect to one of the several
Expand All @@ -18,30 +20,64 @@ tables below list these endpoints.

### Network Endpoints

#### Main Networks
Endpoints for all production and test networks are listed on the
[Polkadot-JS UI](https://polkadot.js.org/apps/#/accounts) which are accessed from
[here](https://github.com/polkadot-js/apps/tree/master/packages/apps-config/src/endpoints).
Endpoints for Polkadot Relay Chain and Kusama Relay Chain, parachains, and Paseo test network are
maintained by the community. System Chains as well as Westend and Rococo test network endpoints maintained by Parity Technologies
are listed below:

<!-- prettier-ignore -->
<Tabs groupId="endpoints" values={[
{ label: 'Polkadot System Chains', value: 'psc' },
{ label: 'Kusama System Chains', value: 'ksc' },
{ label: 'Test Networks', value: 'tn' }
]}>

<TabItem value="psc">

| Network | WSS Endpoint |
| ------------ | ------------------------------------------ |
| Asset Hub | wss://polkadot-asset-hub-rpc.polkadot.io |
| Bridge Hub | wss://polkadot-bridge-hub-rpc.polkadot.io |
| Collectives | wss://polkadot-collectives-rpc.polkadot.io |
| People Chain | wss://polkadot-people-rpc.polkadot.io |

</TabItem>

| Network | URL |
| -------- | ---------------------------- |
| Polkadot | wss://rpc.polkadot.io |
| Kusama | wss://kusama-rpc.polkadot.io |
<TabItem value="ksc">

#### Test Networks
| Network | WSS Endpoint |
| ------------ | ---------------------------------------- |
| Asset Hub | wss://kusama-asset-hub-rpc.polkadot.io |
| Bridge Hub | wss://kusama-bridge-hub-rpc.polkadot.io |
| Collectives | wss://kusama-collectives-rpc.polkadot.io |
| People Chain | wss://kusama-people-rpc.polkadot.io |

| Network | URL |
</TabItem>

<TabItem value="tn">

| Network | WSS Endpoint |
| ------- | ----------------------------- |
| Westend | wss://westend-rpc.polkadot.io |
| Rococo | wss://rococo-rpc.polkadot.io |

</TabItem>

</Tabs>

#### Example usage with Polkadot-JS API

To connect to the Parity node, use the endpoint in your JavaScript apps like so:
To connect to the Parity node for the Polkadot Asset Hub, use the endpoint in your JavaScript apps
like so:

```javascript {5}
// Using the Polkadot Mainnet Endpoint
const { ApiPromise, WsProvider } = require('@polkadot/api');
async () => {
// Construct a provider with the endpoint URL
const provider = new WsProvider('wss://rpc.polkadot.io/');
const provider = new WsProvider('wss://polkadot-asset-hub-rpc.polkadot.io');
// Create an API instance for Polkadot
const api = await ApiPromise.create({ provider });
// ...
Expand All @@ -66,6 +102,6 @@ service, and additional metrics.
:::note

The list of third party RPC endpoints above for Polkadot and Kusama is directly fetched from
[Polkdot-JS UI](https://polkadot.js.org/apps/#/explorer)
[Polkadot-JS UI](https://polkadot.js.org/apps/#/explorer)

:::
Loading