🟣 Release/5.6.2 (update mainnet RPC endpoint) #6509

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

Merged

Lezek123 merged 2 commits into Joystream:master from Lezek123:mainnet-rpc-hotfix

May 21, 2025

CHANGELOG.md

-Original file line number
+Diff line change
@@ Expand Up @@
     The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
     and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+    ## [5.6.2] - 2026-05-21
+    ### Fixed
+    - Updated mainnet RPC endpoint from `wss://rpc.joystream.org:9944` to `wss://rpc.joystream.org`
     ## [5.6.1] - 2026-05-09
     ### Fixed
@@ Expand Down @@

docs/operator-guide.md

-Original file line number
+Diff line change
@@ Expand Up @@
     ### RPC Node
-    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`.
+    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`.
     ### Member faucet
@@ Expand Down @@

package.json

-Original file line number
+Diff line change
@@ -1,6 +1,6 @@
     {
       "description": "UI for consuming Joystream - a user governed video platform",
-      "version": "5.6.1",
+      "version": "5.6.2",
       "license": "GPL-3.0",
       "workspaces": [
         "packages/*"
@@ Expand Down @@

packages/atlas/package.json

-Original file line number
+Diff line change
@@ -1,7 +1,7 @@
     {
       "name": "@joystream/atlas",
       "description": "UI for consuming Joystream - a user governed video platform",
-      "version": "5.6.1",
+      "version": "5.6.2",
       "license": "GPL-3.0",
       "scripts": {
         "start": "vite",
@@ Expand Down @@

packages/atlas/src/.env

-Original file line number
+Diff line change
@@ Expand Up / @@ -36,7 +36,7 @@ VITE_VWO_ACCOUNT_ID= @@
     VITE_PRODUCTION_ORION_AUTH_URL=https://auth.gleev.xyz/api/v1
     VITE_PRODUCTION_ORION_URL=https://orion.gleev.xyz/graphql
     VITE_PRODUCTION_QUERY_NODE_SUBSCRIPTION_URL=wss://orion.joystream.org/graphql
-    VITE_PRODUCTION_NODE_URL=wss://rpc.joystream.org:9944
+    VITE_PRODUCTION_NODE_URL=wss://rpc.joystream.org
     VITE_PRODUCTION_FAUCET_URL=https://faucet.joystream.org/member-faucet/register
     VITE_PRODUCTION_YPP_FAUCET_URL=https://18.184.136.237.nip.io/membership
@@ Expand Down @@

Provide feedback