From 91dbe8dc8a314699d8fdf226a177afedc17c1dc7 Mon Sep 17 00:00:00 2001 From: Tim Garcia Date: Mon, 21 Oct 2024 06:48:06 -0700 Subject: [PATCH] Fixed SW QoS doc to use getClusterNodes (#578) The QUIC tpu port number was incorrectly listed in the docs. This change tells the user to get the QUIC tpu port from the getClusterNodes RPC call. --- content/guides/advanced/stake-weighted-qos.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/content/guides/advanced/stake-weighted-qos.md b/content/guides/advanced/stake-weighted-qos.md index 3a59738a8..149b5cca1 100644 --- a/content/guides/advanced/stake-weighted-qos.md +++ b/content/guides/advanced/stake-weighted-qos.md @@ -140,9 +140,8 @@ On the RPC you will have to use `--rpc-send-transaction-tpu-peer` to forward transactions to a specific leader. The exact usage would be `--rpc-send-transaction-tpu-peer HOST:PORT`. The Host is the ip address of the leader you have the `staked-nodes-overrides` enabled on and the Port is the QUIC -TPU port of that host. The QUIC TPU port number is the lowest value of your -`--dynamic-port-range` plus 9. For example, if the flag is -`--dynamic-port-range 8000-8100`, the QUIC TPU port is `8009`. +TPU port of that host. The QUIC TPU port for a leader can be identified by +making an RPC call to [getClusterNodes](/docs/rpc/http/getClusterNodes.mdx). The peering would looking like the following: