system_reservedPeers - Bittensor RPC Method

Returns the list of reserved peers for the Bittensor node. Reserved peers are connections that the node actively maintains -- it will always try to stay connected to them and will not evict them during peer management. These are typically set via the --reserved-nodes CLI flag or the system_addReservedPeer RPC method.

Parameters

None.

Response

Code Examples

Use Cases

• Configuration verification -- Confirm that the expected reserved peers are configured after node startup or after adding/removing reserved peers via RPC.
• Infrastructure monitoring -- Track the reserved peer configuration across your Bittensor node fleet.
• Networking diagnostics -- Check which peers are reserved when debugging connectivity issues.

Notes

• On public shared RPC endpoints, the reserved peer list may be empty or masked for security.
• This method may require --rpc-methods unsafe on some node configurations.
• Reserved peers are distinct from boot nodes; boot nodes are used for initial peer discovery, while reserved peers are permanently maintained connections.

Related Methods

• system_addReservedPeer -- Add a reserved peer
• system_removeReservedPeer -- Remove a reserved peer
• system_peers -- List all connected peers (not just reserved)
• system_localListenAddresses -- Get the node's own listen addresses