Skip to content

RPC overview

CategoryDocumentationStatusDraftLast reviewed2026-07-13

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.

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.

The generated example configuration file includes RPC settings for:

  • rpcallowip
  • rpcauth
  • rpcbind
  • rpccookiefile
  • rpcpassword
  • rpcport
  • rpcthreads
  • rpcuser
  • rpcwhitelist
  • server

MoreBC2 has two relevant RPC-port evidence types:

  • BitcoinII Core v29.1.0 mainnet local testing used localhost-only RPC on 127.0.0.1:8337.
  • Older inherited/generated Bitcoin Core-style material may mention mainnet 8332, testnet 18332, signet 38332, and regtest 18443.

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.

MoreBC2 has reviewed first-pass source maps for these 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.

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:

  • getblockcount
  • getbestblockhash
  • getblockchaininfo
  • getnetworkinfo
  • getconnectioncount
  • getpeerinfo
  • getmempoolinfo
  • getdifficulty
  • uptime

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.

Reviewed mining RPC commands include:

  • getnetworkhashps
  • getmininginfo
  • getblocktemplate
  • submitblock
  • submitheader
  • prioritisetransaction
  • getprioritisedtransactions

Important note: the reviewed mining RPC file says mining RPCs follow GBT/BIP22 in using satoshi amounts, unlike wallet RPCs that use BC2 values.

Reviewed blockchain RPC commands include:

  • getblockchaininfo
  • getbestblockhash
  • getblockcount
  • getblock
  • getblockhash
  • getblockheader
  • getchaintips
  • getdifficulty
  • getdeploymentinfo
  • gettxout
  • gettxoutsetinfo
  • pruneblockchain
  • verifychain
  • scantxoutset
  • scanblocks
  • getdescriptoractivity
  • getblockfilter
  • dumptxoutset
  • loadtxoutset
  • getchainstates

Some commands are powerful, slow, experimental, or intended for advanced workflows. They should be documented carefully and tested before being recommended.

Reviewed network RPC commands include:

  • getconnectioncount
  • ping
  • getpeerinfo
  • addnode
  • disconnectnode
  • getaddednodeinfo
  • getnettotals
  • getnetworkinfo
  • setban
  • listbanned
  • clearbanned
  • setnetworkactive
  • getnodeaddresses
  • getaddrmaninfo

Reviewed hidden/testing commands include:

  • addconnection
  • addpeeraddress
  • sendmsgtopeer
  • getrawaddrman

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.

Reviewed raw transaction RPC commands include:

  • getrawtransaction
  • createrawtransaction
  • decoderawtransaction
  • decodescript
  • combinerawtransaction
  • signrawtransactionwithkey
  • decodepsbt
  • combinepsbt
  • finalizepsbt
  • createpsbt
  • converttopsbt
  • utxoupdatepsbt
  • descriptorprocesspsbt
  • joinpsbts
  • analyzepsbt

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.

Reviewed mempool/broadcast RPC commands include:

  • sendrawtransaction
  • testmempoolaccept
  • submitpackage
  • getrawmempool
  • getmempoolentry
  • getmempoolancestors
  • getmempooldescendants
  • gettxspendingprevout
  • getmempoolinfo
  • savemempool
  • importmempool
  • getorphantxs hidden/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.

Reviewed wallet RPC commands include:

  • getwalletinfo
  • listwalletdir
  • listwallets
  • loadwallet
  • unloadwallet
  • createwallet
  • setwalletflag
  • sethdseed
  • upgradewallet
  • migratewallet
  • simulaterawtransaction
  • getnewaddress
  • getrawchangeaddress
  • setlabel
  • listaddressgroupings
  • addmultisigaddress
  • backupwallet
  • restorewallet
  • sendtoaddress
  • sendmany
  • send
  • sendall
  • walletpassphrase
  • walletlock
  • getbalance
  • getbalances
  • listunspent
  • listtransactions
  • listsinceblock
  • gettransaction
  • rescanblockchain

The reviewed wallet registration and file-specific passes now cover major wallet command groups. Examples still need local testing before being recommended.

The command forms below are not verified instructions. They are placeholders for future local testing and are tracked in Command testing status.

Some of these commands now have a matching local Windows/mainnet test record. Commands without a matching dated record remain placeholders, not working instructions.

Terminal window
bitcoinII-cli getblockchaininfo
bitcoinII-cli getnetworkinfo
bitcoinII-cli getblockcount
bitcoinII-cli getbestblockhash
bitcoinII-cli getmininginfo
bitcoinII-cli getdifficulty
bitcoinII-cli getconnectioncount
bitcoinII-cli getpeerinfo
bitcoinII-cli getnettotals
bitcoinII-cli getrawmempool true
bitcoinII-cli getmempoolinfo
bitcoinII-cli listwallets
bitcoinII-cli listwalletdir

These need fixture values, node state, wallet context, or transaction examples before they can be used as instructions.

Terminal window
bitcoinII-cli gettransaction <txid>
bitcoinII-cli getrawtransaction <txid> 1
bitcoinII-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.

Terminal window
bitcoinII-cli getwalletinfo
bitcoinII-cli getnewaddress
bitcoinII-cli listtransactions
bitcoinII-cli sendtoaddress <address> <amount>

Notes:

  • getwalletinfo and listtransactions depend on wallet context.
  • getnewaddress can change wallet state by creating or reserving a new address.
  • sendtoaddress can move funds and should stay out of normal guides unless a disposable-wallet test record and strong warnings exist.
Terminal window
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.

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.
  • 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.

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.