Skip to content
MoreBC2

Local-only RPC enablement plan

CategoryVerification planStatusPlanned / Not yet executedLast reviewed2026-08-27

Public-release privacy note: Personal local-user path component minimally redacted for public release; technical content otherwise unchanged. The current-tree record is not byte-identical to the original committed version, which remains in Git history.

Summary

Section titled “Summary”

This page records a proposed safe configuration for enabling local-only JSON-RPC access to a BitcoinII Core v29.1.0 GUI node on Windows.

The plan was derived from then-reviewed BitcoinII material and a read-only inspection of the locally running node. This page preserves the plan as it stood before execution; the linked local-node inspection and smoke-test records document the later v29.1.0 Windows/mainnet result. The plan does not establish 8337 as a universal source default.

Environment

Section titled “Environment”

Observed local paths:

  • GUI executable: C:\Users\<user>\Desktop\BitcoinII-29.1.0-x86_64-win64-GUI\BitcoinII-29.1.0-x86_64-win64-GUI\bitcoinII-qt.exe
  • CLI executable: C:\bcli\bin\Release\bitcoinII-cli.exe
  • Data directory: C:\Users\<user>\AppData\Local\BitcoinII
  • Proposed configuration file: C:\Users\<user>\AppData\Local\BitcoinII\bitcoinII.conf

Source-observed ports

Section titled “Source-observed ports”

BitcoinII Core v29.1.0 source in src/chainparamsbase.cpp indicates:

  • Mainnet JSON-RPC port: 8337
  • Mainnet P2P port: 8338

The running node was already observed listening for P2P on 8338.

A separate listener on 127.0.0.1:8339 did not respond as a usable BitcoinII JSON-RPC HTTP endpoint when tested with bitcoinII-cli.

Proposed configuration

Section titled “Proposed configuration”
server=1
rpcbind=127.0.0.1
rpcallowip=127.0.0.1
rpcport=8337

Cookie authentication is preferred. No rpcuser, rpcpassword, or rpcauth setting is proposed.

Interpretation:

  • server=1 enables RPC server mode for the GUI node.
  • rpcbind=127.0.0.1 binds RPC only to localhost.
  • rpcallowip=127.0.0.1 limits accepted RPC clients to localhost.
  • rpcport=8337 is the value selected for this dated local test and later observed in that v29.1.0 Windows/mainnet environment. It is not established here as a universal BitcoinII mainnet RPC default; inherited/generated material elsewhere shows 8332.

Planned restart procedure

Section titled “Planned restart procedure”
  1. Close BitcoinII GUI normally.
  2. Wait until bitcoinII-qt.exe is no longer running.
  3. Create bitcoinII.conf in the observed data directory with the reviewed content above.
  4. Start the same GUI executable again.
  5. Confirm the GUI uses the same data directory.
  6. Confirm a localhost listener exists on port 8337.
  7. Run only the reviewed read-only RPC commands below.

Do not kill the process, edit wallet files, delete cookie files, or expose authentication material.

Planned read-only checks

Section titled “Planned read-only checks”
Terminal window
& 'C:\bcli\bin\Release\bitcoinII-cli.exe' -datadir='C:\Users\<user>\AppData\Local\BitcoinII' -rpcconnect=127.0.0.1 -rpcport=8337 getblockcount


& 'C:\bcli\bin\Release\bitcoinII-cli.exe' -datadir='C:\Users\<user>\AppData\Local\BitcoinII' -rpcconnect=127.0.0.1 -rpcport=8337 getbestblockhash


& 'C:\bcli\bin\Release\bitcoinII-cli.exe' -datadir='C:\Users\<user>\AppData\Local\BitcoinII' -rpcconnect=127.0.0.1 -rpcport=8337 getblockchaininfo


& 'C:\bcli\bin\Release\bitcoinII-cli.exe' -datadir='C:\Users\<user>\AppData\Local\BitcoinII' -rpcconnect=127.0.0.1 -rpcport=8337 getnetworkinfo


& 'C:\bcli\bin\Release\bitcoinII-cli.exe' -datadir='C:\Users\<user>\AppData\Local\BitcoinII' -rpcconnect=127.0.0.1 -rpcport=8337 getconnectioncount

Optional harmless listener check:

Terminal window
netstat -ano | Select-String -Pattern ':8337\s'

Data to record after execution

Section titled “Data to record after execution”
  • Date and time checked.
  • BitcoinII Core version.
  • chain.
  • blocks.
  • headers.
  • bestblockhash.
  • verificationprogress.
  • initialblockdownload.
  • networkactive.
  • subversion.
  • connections.
  • Same-time explorer height and tip hash, if a comparison is performed.
  • Exact commands used and whether each command passed or failed.

Do not record cookie contents, RPC credentials, wallet data, addresses, balances, or transaction history.

Rollback

Section titled “Rollback”

If RPC should be disabled again:

  1. Close BitcoinII GUI normally.
  2. Remove or rename: C:\Users\<user>\AppData\Local\BitcoinII\bitcoinII.conf
  3. Restart the same GUI executable.

Rollback means returning to the previous no-config-file state. Do not delete .cookie, wallet files, chainstate, blocks, or settings files.

What this plan does not prove

Section titled “What this plan does not prove”

This page does not prove:

  • that RPC has been enabled,
  • that port 8337 is reachable,
  • that cookie authentication succeeds,
  • that the detected CLI is fully compatible with the running GUI,
  • that any RPC result is correct,
  • that the explorer or local node is synced.
Section titled “Related pages”

Verification

Section titled “Verification”

Status: Planned / Not yet executed
Primary sources checked: BitcoinII Core v29.1.0 material and the 2026-07-10 local-node inspection report Notes: This is a preserved reviewed plan, not the runtime evidence record. RPC-port wording was synchronized on 2026-08-27: 8337 is supported for the linked local test environment only, while inherited/generated material elsewhere shows 8332.