Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
Bitcoin Core RPC Whitelists: Least-Privilege Access Guide
Bitcoin Core 0.20 rpcwhitelist guide covering per-user RPC allowlists, intersection rules, default-deny behaviour, authentication, testing and recovery.
This guide explains Bitcoin Core rpcwhitelist in plain English. It shows what the command does, what its result means and what it cannot prove.
TL;DR
- What it is: Bitcoin Core 0.20.0 introduced rpcwhitelist and rpcwhitelistdefault so authenticated RPC users could be restricted to named methods. A whitelist entry used a username followed by a comma-separated method set; multiple entries for the same user were intersected.
- Why it matters: Bitcoin Core RPC whitelists add useful method-level least privilege, but they do not replace network isolation or careful command design. Build explicit roles, test denial paths and preserve a protected recovery route.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Bitcoin Core rpcwhitelist in simple English
An RPC is a command sent to one Bitcoin Core node. It can ask that node for information or request a local action. A successful reply describes that node; it does not automatically prove what happened across the Bitcoin network.
Beginners can focus on the input, the result and the limit of that result. Operators should test the command on the exact Bitcoin Core version they run before relying on it.
Simple example
Think of the transaction as a form passed between several authorised signers. Each person or device checks the same payment details before adding approval. Passing the form around does not make the payment safe unless every signer checks what it contains.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Separate authentication and authority
Keep RPC transport on a protected interface with strong generated credentials. A correct username and password identifies a caller; the whitelist then limits which command names that identity may invoke.
Entry syntax
Each rpcwhitelist value binds one username to an explicit comma-separated method list. Generate configuration from reviewed structured policy rather than accepting free-form administrator text.
Intersection semantics
When several whitelist entries name the same user, Core intersects the method sets. Treat this as deliberate tightening and test the final effective set; duplicate fragments do not add permissions.
Default behaviour
Unless rpcwhitelistdefault is zero, setting any whitelist causes unspecified users to receive empty whitelists. Setting the default to one with no entries also denies every RPC method.
Method-level limits
Allowing a method does not constrain its arguments, wallet endpoint or filesystem path. Use separate users and nodes where parameter-level or tenant isolation is required.
Deployment safety
Keep one tested emergency administrative route on a protected host, validate syntax before restart and prevent credentials or method inventories entering public logs.
How specialists test it
Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.
Frequently asked questions
What is Bitcoin Core RPC Whitelists?
Bitcoin Core 0.20.0 introduced rpcwhitelist and rpcwhitelistdefault so authenticated RPC users could be restricted to named methods. A whitelist entry used a username followed by a comma-separated method set; multiple entries for the same user were intersected.
Is Bitcoin Core RPC Whitelists active or supported today?
Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Why does Bitcoin Core RPC Whitelists matter?
Bitcoin Core RPC whitelists add useful method-level least privilege, but they do not replace network isolation or careful command design. Build explicit roles, test denial paths and preserve a protected recovery route.
Do beginners need to use the technical details?
No. The command is mainly for people who operate Bitcoin Core or software connected to it. Other readers can use the article to understand what an operator or service is measuring.
Conclusion
Bitcoin Core RPC whitelists add useful method-level least privilege, but they do not replace network isolation or careful command design. Build explicit roles, test denial paths and preserve a protected recovery route.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 Explained made simple. See the main facts, costs, risks and practical checks before you make a decision.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.