NodeGuide / Optional reference / RPC & REST
RPC & REST Reference Guide
Scroll down to see entire page
Quick definitions appear when you tap technical terms during setup. This optional guide gives you more help with setup, settings, and troubleshooting.
Safety wording reviewed September 23, 2026. Reference instructions may differ by device, app and installed software version; NodeGuide does not detect your version. Check the current official instructions before making a change.
Before changing network or policy settings, record the current values and check your installed version’s official guide. A wrong change can block access or transaction relay. Never put RPC or an admin dashboard on the public internet.
RPC vs P2P
P2P is how Bitcoin nodes communicate with each other. RPC is how trusted wallets or apps communicate with your node.
Why RPC should stay private
RPC can reveal information about your node and may allow trusted apps to send commands. Keep RPC private and do not expose it directly to the public internet.
RPC credentials and authentication
RPC may use a username, password, cookie, or other login information. Treat this information like a password and never share it publicly.
RPC work queue basics
The RPC work queue controls how many requests your node can handle from trusted apps at one time. Most beginners do not need to change this setting.
Before making REST public
REST can make some node information available to apps. Only turn on public access if you understand what information will be exposed and how you will protect it.
Trusted wallets and apps
Only allow wallets and apps you trust to connect to RPC. Keep software updated and remove access for apps you no longer use.
Local network vs remote access
Connecting from your home network is usually simpler and safer. For remote access, use a secure private-network method instead of exposing RPC directly to the internet.
Common RPC & REST troubleshooting
If an app cannot connect, first make sure your node is running. Then check the address, port, and login information. Do not make RPC public while troubleshooting.