Skip to content

Commit f587e73

Browse files
authored
🔧 Update mainnet RPC endpoint (#73)
* Update mainnet RPC endpoint * Bump version and update CHANGELOG
1 parent 7f89e79 commit f587e73

File tree

5 files changed

+10
-4
lines changed

5 files changed

+10
-4
lines changed

CHANGELOG.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,12 @@ All notable changes to this project will be documented in this file.
55
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
66
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
77

8+
## [5.6.2] - 2026-05-21
9+
10+
### Fixed
11+
12+
- Updated mainnet RPC endpoint from `wss://rpc.joystream.org:9944` to `wss://rpc.joystream.org`
13+
814
## [5.6.1] - 2026-05-09
915

1016
### Fixed

docs/operator-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -252,7 +252,7 @@ Query Node (QN) is a service that processes blockchain events and stores them in
252252

253253
### RPC Node
254254

255-
RPC nodes are Joystream blockchain nodes that are responsible for running the network. Whether you need your own instance of RPC node depends on your setup. If you are running your own QN, you probably also want to run RPC node alongside for speed of synching and indexing. If you make that RPC endpoint public, you can pass it as `VITE_PRODUCTION_NODE_URL` environment variable, meaning that all user-initiated transactions would be sent to your RPC node. However, you can also use a publicly available node, like `wss://rpc.joystream.org:9944`.
255+
RPC nodes are Joystream blockchain nodes that are responsible for running the network. Whether you need your own instance of RPC node depends on your setup. If you are running your own QN, you probably also want to run RPC node alongside for speed of synching and indexing. If you make that RPC endpoint public, you can pass it as `VITE_PRODUCTION_NODE_URL` environment variable, meaning that all user-initiated transactions would be sent to your RPC node. However, you can also use a publicly available node, like `wss://rpc.joystream.org`.
256256

257257
### Member faucet
258258

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"description": "UI for consuming Joystream - a user governed video platform",
3-
"version": "5.6.1",
3+
"version": "5.6.2",
44
"license": "GPL-3.0",
55
"workspaces": [
66
"packages/*"

packages/atlas/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"name": "@joystream/atlas",
33
"description": "UI for consuming Joystream - a user governed video platform",
4-
"version": "5.6.1",
4+
"version": "5.6.2",
55
"license": "GPL-3.0",
66
"scripts": {
77
"start": "vite",

packages/atlas/src/.env

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ VITE_VWO_ACCOUNT_ID=
3636
VITE_PRODUCTION_ORION_AUTH_URL=https://auth.gleev.xyz/api/v1
3737
VITE_PRODUCTION_ORION_URL=https://orion.gleev.xyz/graphql
3838
VITE_PRODUCTION_QUERY_NODE_SUBSCRIPTION_URL=wss://orion.joystream.org/graphql
39-
VITE_PRODUCTION_NODE_URL=wss://rpc.joystream.org:9944
39+
VITE_PRODUCTION_NODE_URL=wss://rpc.joystream.org
4040
VITE_PRODUCTION_FAUCET_URL=https://faucet.joystream.org/member-faucet/register
4141
VITE_PRODUCTION_YPP_FAUCET_URL=https://18.184.136.237.nip.io/membership
4242

0 commit comments

Comments
 (0)