Bitcoin Core createwallet RPC: Loaded Wallet Provisioning Guide

This guide explains Bitcoin Core createwallet RPC in plain English. It shows what the command does, what its result means and what it cannot prove.

Name and path control

Validate wallet_name against an approved inventory and canonicalise any path. Reject traversal, ambiguous relative paths, symlink surprises and locations outside the wallet storage boundary. The returned name can be a full path when one was used, so clients must not assume a short basename.

Creates and loads

The operation immediately loads the wallet into the running node. Update monitoring, RPC wallet routing, backup discovery and access control as one transaction. A new loaded wallet should not automatically become eligible for deposits, withdrawals or signing.

Private-key mode

disable_private_keys false creates a key-capable wallet; true prevents private keys so only watch-only material is possible. This setting is a permanent design choice for the wallet. Require explicit custody approval for key-enabled creation and prove watch-only signing is denied.

Warning is evidence

The result includes name and warning. Treat any non-empty warning as a failed readiness gate even if the wallet object exists. Preserve the warning with configuration and logs, investigate loading state and do not retry creation under another name to hide the condition.

Initial hardening

For a key-capable wallet, establish encryption, backup and access controls before receiving value. For watch-only use, import only authenticated descriptors or scripts and record birthday information. Do not expose addresses until restoration and monitoring have been tested.

Multiwallet identity

Route subsequent RPC calls to the exact wallet endpoint and carry an immutable wallet identifier through jobs. Duplicate display names, renamed paths and unloaded wallets can cause operations to target the wrong custody domain unless identity is explicit.

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.

Conclusion

createwallet provisions a live custody or watch-only database, not just a file. Safe automation controls path and key mode, treats warnings as blockers and proves backup, routing and denial behaviour before use.