RPC overview
Summary
Section titled “Summary”BitcoinII Core includes JSON-RPC functionality for command-line tools, wallets, exchanges, explorers, and other services.
This page is a safe starting point only. Nine read-only RPC commands have a dated local Windows/mainnet test record, but other RPC command examples should not be marked tested or Verified until they are tested against a running BitcoinII Core node in a documented environment.
For test tracking, see Command testing status, the Command smoke-test plan, Local BitcoinII node inspection - 2026-07-10, and Read-only RPC smoke test - 2026-07-10.
What RPC is used for
Section titled “What RPC is used for”RPC can be used to:
- Query node status.
- Query chain and block status.
- Query network and peer status.
- Query mining/template status.
- Query wallet status.
- Generate deposit addresses.
- Inspect transactions.
- Submit transactions.
- Monitor blocks and confirmations.
- Inspect UTXO state.
- Manage pruning and block-data workflows.
- Build, decode, and analyze raw transactions and PSBTs.
- Inspect mempool state and test transaction acceptance.
Source-observed configuration notes
Section titled “Source-observed configuration notes”The generated example configuration file includes RPC settings for:
rpcallowiprpcauthrpcbindrpccookiefilerpcpasswordrpcportrpcthreadsrpcuserrpcwhitelistserver
MoreBC2 has two relevant RPC-port evidence types:
- BitcoinII Core
v29.1.0mainnet local testing used localhost-only RPC on127.0.0.1:8337. - Older inherited/generated Bitcoin Core-style material may mention mainnet
8332, testnet18332, signet38332, and regtest18443.
Do not silently treat inherited/generated 8332 material as the BitcoinII v29.1.0 mainnet runtime value. Also do not assume every historical BitcoinII release used 8337 unless a version-specific source or test record supports it.
The same file warns not to expose the RPC server to untrusted networks such as the public internet.
Source-reviewed RPC groups
Section titled “Source-reviewed RPC groups”MoreBC2 has reviewed first-pass source maps for these RPC files:
- Mining RPC:
src/rpc/mining.cpp - Blockchain RPC:
src/rpc/blockchain.cpp - Network RPC:
src/rpc/net.cpp - Raw transaction RPC:
src/rpc/rawtransaction.cpp - Mempool and transaction broadcast RPC:
src/rpc/mempool.cpp - Wallet RPC: wallet startup/address/backup/spend/encryption/coin/history RPC files
These reviews document command groups and behavior from source, but do not mark command examples as tested unless a dated local record says so.
Locally tested read-only subset
Section titled “Locally tested read-only subset”The 2026-07-10 smoke test locally tested these read-only commands against BitcoinII Core v29.1.0 on Windows mainnet with localhost-only RPC at 127.0.0.1:8337:
getblockcountgetbestblockhashgetblockchaininfogetnetworkinfogetconnectioncountgetpeerinfogetmempoolinfogetdifficultyuptime
This is not cross-platform proof and does not cover wallet, transaction, mining, peer-control, shutdown, import/export, or state-changing workflows. For publication-ready examples, use API read-only examples and the dated smoke-test record.
Mining RPC group
Section titled “Mining RPC group”Reviewed mining RPC commands include:
getnetworkhashpsgetmininginfogetblocktemplatesubmitblocksubmitheaderprioritisetransactiongetprioritisedtransactions
Important note: the reviewed mining RPC file says mining RPCs follow GBT/BIP22 in using satoshi amounts, unlike wallet RPCs that use BC2 values.
Blockchain RPC group
Section titled “Blockchain RPC group”Reviewed blockchain RPC commands include:
getblockchaininfogetbestblockhashgetblockcountgetblockgetblockhashgetblockheadergetchaintipsgetdifficultygetdeploymentinfogettxoutgettxoutsetinfopruneblockchainverifychainscantxoutsetscanblocksgetdescriptoractivitygetblockfilterdumptxoutsetloadtxoutsetgetchainstates
Some commands are powerful, slow, experimental, or intended for advanced workflows. They should be documented carefully and tested before being recommended.
Network RPC group
Section titled “Network RPC group”Reviewed network RPC commands include:
getconnectioncountpinggetpeerinfoaddnodedisconnectnodegetaddednodeinfogetnettotalsgetnetworkinfosetbanlistbannedclearbannedsetnetworkactivegetnodeaddressesgetaddrmaninfo
Reviewed hidden/testing commands include:
addconnectionaddpeeraddresssendmsgtopeergetrawaddrman
Read-only network status commands are good smoke-test candidates. Peer-changing, ban-list, network-active, hidden, and testing-only commands should be documented carefully and should not be copied into beginner guides as normal examples.
Raw transaction RPC group
Section titled “Raw transaction RPC group”Reviewed raw transaction RPC commands include:
getrawtransactioncreaterawtransactiondecoderawtransactiondecodescriptcombinerawtransactionsignrawtransactionwithkeydecodepsbtcombinepsbtfinalizepsbtcreatepsbtconverttopsbtutxoupdatepsbtdescriptorprocesspsbtjoinpsbtsanalyzepsbt
Raw transaction commands are advanced tools for non-wallet transaction lookup, unsigned transaction construction, explicit-key signing, script decoding, and PSBT workflows. They need tested examples before appearing in service or user guides.
Mempool and broadcast RPC group
Section titled “Mempool and broadcast RPC group”Reviewed mempool/broadcast RPC commands include:
sendrawtransactiontestmempoolacceptsubmitpackagegetrawmempoolgetmempoolentrygetmempoolancestorsgetmempooldescendantsgettxspendingprevoutgetmempoolinfosavemempoolimportmempoolgetorphantxshidden/experimental
testmempoolaccept is a dry-run acceptance check. sendrawtransaction submits a signed raw transaction toward local acceptance and relay. submitpackage, getorphantxs, and mempool persistence commands should be treated as advanced until tested and documented more carefully.
Wallet RPC group
Section titled “Wallet RPC group”Reviewed wallet RPC commands include:
getwalletinfolistwalletdirlistwalletsloadwalletunloadwalletcreatewalletsetwalletflagsethdseedupgradewalletmigratewalletsimulaterawtransactiongetnewaddressgetrawchangeaddresssetlabellistaddressgroupingsaddmultisigaddressbackupwalletrestorewalletsendtoaddresssendmanysendsendallwalletpassphrasewalletlockgetbalancegetbalanceslistunspentlisttransactionslistsinceblockgettransactionrescanblockchain
The reviewed wallet registration and file-specific passes now cover major wallet command groups. Examples still need local testing before being recommended.
Untested command inventory
Section titled “Untested command inventory”The command forms below are not verified instructions. They are placeholders for future local testing and are tracked in Command testing status.
Read-only or status-style placeholders
Section titled “Read-only or status-style placeholders”Some of these commands now have a matching local Windows/mainnet test record. Commands without a matching dated record remain placeholders, not working instructions.
bitcoinII-cli getblockchaininfobitcoinII-cli getnetworkinfobitcoinII-cli getblockcountbitcoinII-cli getbestblockhashbitcoinII-cli getmininginfobitcoinII-cli getdifficultybitcoinII-cli getconnectioncountbitcoinII-cli getpeerinfobitcoinII-cli getnettotalsbitcoinII-cli getrawmempool truebitcoinII-cli getmempoolinfobitcoinII-cli listwalletsbitcoinII-cli listwalletdirLookup and dry-run placeholders
Section titled “Lookup and dry-run placeholders”These need fixture values, node state, wallet context, or transaction examples before they can be used as instructions.
bitcoinII-cli gettransaction <txid>bitcoinII-cli getrawtransaction <txid> 1bitcoinII-cli decoderawtransaction <hex>bitcoinII-cli testmempoolaccept '["signedhex"]'bitcoinII-cli analyzepsbt <psbt>Wallet-state-changing or funds-moving placeholders
Section titled “Wallet-state-changing or funds-moving placeholders”These should not sit beside harmless status calls in beginner guidance.
bitcoinII-cli getwalletinfobitcoinII-cli getnewaddressbitcoinII-cli listtransactionsbitcoinII-cli sendtoaddress <address> <amount>Notes:
getwalletinfoandlisttransactionsdepend on wallet context.getnewaddresscan change wallet state by creating or reserving a new address.sendtoaddresscan move funds and should stay out of normal guides unless a disposable-wallet test record and strong warnings exist.
Mining and block-template placeholders
Section titled “Mining and block-template placeholders”bitcoinII-cli getblocktemplate '{"rules":["segwit"]}'Block/header submission examples are intentionally not included here as copyable command lines.
Do not copy any of these into user guides as working examples until the command-testing page has matching test records. Even locally tested values should retain version, network, platform, datadir/RPC context, and redaction rules.
Exchange/service-provider caution
Section titled “Exchange/service-provider caution”Service providers should not expose RPC publicly. RPC access should be firewalled, authenticated, and restricted to trusted systems.
For service docs, MoreBC2 should distinguish:
- Read-only status commands.
- Network and peer status commands.
- Block and transaction lookup commands.
- Address/deposit commands.
- Wallet commands that can create addresses.
- Wallet commands that expose keys, sign transactions, or move funds.
- Raw transaction and PSBT commands for advanced construction workflows.
- Dry-run mempool acceptance commands.
- Live transaction submission commands.
- Maintenance commands that can affect node state.
- Peer-changing or network-state commands.
- Hidden/testing commands that should not appear in normal operator guides.
Open items
Section titled “Open items”- Test additional common RPC commands against a synced BitcoinII Core node or documented disposable local environment.
- Confirm binary names for each platform and release asset.
- Confirm configuration file paths by operating system.
- Confirm wallet loading behavior.
- Review lower-level P2P files beyond network RPC.
- Confirm whether any BitcoinII-specific RPC differences exist beyond naming and visible strings.
Sources
Section titled “Sources”share/examples/bitcoinII.confdoc/JSON-RPC-interface.mdsrc/rpc/mining.cppsrc/rpc/blockchain.cppsrc/rpc/net.cppsrc/rpc/rawtransaction.cppsrc/rpc/mempool.cppsrc/wallet/rpc/wallet.cppsrc/wallet/rpc/addresses.cppsrc/wallet/rpc/backup.cppsrc/wallet/rpc/spend.cppsrc/wallet/rpc/encrypt.cppsrc/wallet/rpc/coins.cppsrc/wallet/rpc/transactions.cpp- Command testing status
- Command smoke-test plan
- Local BitcoinII node inspection - 2026-07-10
- Read-only RPC smoke test - 2026-07-10
- API read-only examples
Verification
Section titled “Verification”Status: Draft
Primary sources checked: Partially
Notes: Config-option notes and inherited/generated port examples are source-observed from generated/example configuration material. BitcoinII Core v29.1.0 mainnet localhost-only RPC was locally tested on 127.0.0.1:8337. Mining, blockchain, network, raw transaction, mempool, and wallet RPC groups have first-pass source review. Command examples remain placeholders unless matching local test records exist.