system_addReservedPeer - Bittensor RPC Method
Add a reserved peer to a Bittensor node. Administrative method, not available on public RPC.
Adds a reserved peer to the running Bittensor node. Reserved peers are always maintained as connections -- the node will actively try to connect and reconnect to them, and they are not subject to normal peer eviction. This is an administrative method that requires --rpc-methods unsafe.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
peer | string | Yes | Multiaddr of the peer to add (e.g. "/ip4/198.51.100.1/tcp/30333/p2p/12D3KooW..."). |
Response
| Field | Type | Description |
|---|---|---|
result | null | Confirms the peer has been added to the reserved list. |
Code Examples
Use Cases
- Guaranteed connectivity -- Ensure your Bittensor node always maintains a connection to critical peers (e.g. your own boot nodes or trusted validators).
- Private network setup -- Build a private or semi-private node cluster by reserving connections between known nodes.
- Connectivity recovery -- Add a known-good peer when a node is struggling to find peers.
Notes
- This is an unsafe/administrative method. Disabled on public RPC endpoints including Dwellir's shared Bittensor nodes.
- Reserved peers are persistent -- the node will continue trying to connect to them even after disconnections.
- The peer multiaddr must include the peer ID (the
/p2p/12D3KooW...component). - Use
system_removeReservedPeerto remove a peer from the reserved list.
Related Methods
system_removeReservedPeer-- Remove a reserved peersystem_reservedPeers-- List current reserved peerssystem_peers-- List all currently connected peerssystem_localListenAddresses-- Get the node's own listen addresses