Skip to content
MoreBC2

Command example scan

CategoryVerificationStatusArchived project-management historyLast reviewed2026-07-04

Archived: this scan records an earlier review checkpoint. Its dated findings remain useful, but its readiness language is not current.

Summary

Section titled “Summary”

This page tracks command-example scans before invite-only review.

The purpose is to make sure command examples are not accidentally presented as tested instructions.

This page is a scan checklist and record. It does not verify that any command works.

Scan goals

Section titled “Scan goals”

Before private review, find command examples that may need clearer labeling, especially examples involving:

  • bitcoinII-cli
  • bitcoinIId
  • bitcoinII-qt
  • bitcoinII.conf
  • getblockchaininfo
  • getnetworkinfo
  • getpeerinfo
  • getwalletinfo
  • getnewaddress
  • sendtoaddress
  • getblocktemplate
  • submitblock
  • submitheader
  • getrawtransaction
  • testmempoolaccept
  • sendrawtransaction
  • walletpassphrase
  • backupwallet
  • restorewallet
  • rescanblockchain
  • addnode
  • disconnectnode
  • setban
  • clearbanned
  • setnetworkactive

Required handling

Section titled “Required handling”

Every command example should be one of the following:

Status Required handling
Source-observed Link to source review or RPC overview, and say it is not locally tested.
Placeholder Label clearly as a future test shape, not instructions.
Locally tested Link to a command test record with environment details.
Do not publish Keep out of beginner/user docs and explain why if mentioned.

High-risk command categories

Section titled “High-risk command categories”

These should not appear as beginner copy/paste guidance:

  • Wallet movement commands.
  • Wallet backup/restore commands without a tested disposable-wallet record.
  • Wallet access-state commands.
  • Private-key or explicit-key signing commands.
  • Raw transaction live submission commands.
  • Block/header submission commands.
  • Manual peer or peer-list commands without operator context.
  • Network-active state changes without operator context.
  • Pruning/reindex/import commands without context.
  • RPC exposure/authentication examples without a security caveat.

Pages to scan first

Section titled “Pages to scan first”

Priority pages:

  • README.md
  • docs/README.md
  • docs/developers/rpc-overview.md
  • docs/verification/command-testing.md
  • docs/verification/command-smoke-test-plan.md
  • docs/nodes/node-guide.md
  • docs/wallets/wallet-guide.md
  • docs/mining/mining-overview.md
  • docs/configuration/configuration-overview.md
  • docs/configuration/rpc-configuration.md
  • docs/exchange/deposit-monitoring.md
  • docs/exchange/service-integration-checklist.md

Scan record

Section titled “Scan record”
Date Search term / concern Files checked Issues found Fix commit Notes
2026-06-30 bitcoinII-cli deposit examples docs/exchange/deposit-monitoring.md Command block needed clearer placeholder/test-tracker wording 8e7c539 Deposit command examples explicitly say they are placeholder examples and link to command-testing status.
2026-06-30 wallet command examples docs/wallets/wallet-guide.md No blocking issue found No change Wallet guide lists commands under command-testing status and warns sensitive/state-changing commands stay out of beginner docs until tested.
2026-06-30 mining command examples docs/mining/mining-overview.md No blocking issue found No change Mining overview links command-testing status and marks block/header submission commands as not for normal user examples.
2026-06-30 service checklist command wording docs/exchange/service-integration-checklist.md No blocking issue found No change Checklist says required commands must be tested and does not provide copy/paste examples.
2026-06-30 RPC overview inventory docs/developers/rpc-overview.md No blocking issue found No change RPC overview labels command forms as unverified placeholders and warns not to copy them into user guides as working examples.
2026-06-30 node command inventory docs/nodes/node-guide.md No command-labeling issue found; stale source links updated separately 8e4a749 Node guide links to command-testing status and warns not to treat listed commands as working instructions.
2026-06-30 configuration command/setup wording docs/configuration/configuration-overview.md, docs/configuration/rpc-configuration.md No command-labeling issue found; stale source links updated separately 062686f, b1272f8 Configuration pages say setup/auth examples are untested and link command-testing status.
2026-06-30 command tracker itself docs/verification/command-testing.md No blocking issue found No change Command tracker correctly labels entries as Placeholder, Source-observed, Locally tested, Verified, Needs recheck, or Do not publish.
2026-06-30 developer build/test command blocks docs/developers/local-development.md, docs/developers/build-system.md, docs/developers/testing.md No blocking issue found No change Build and test commands are explicitly described as untested or future record shapes.
2026-06-30 release checking command wording docs/developers/release-verification.md, docs/developers/release-process.md Release-process page had stale current-release wording and old release path a5aaf58 Release-process page now points to current observed release path and keeps download checking unverified.
2026-07-01 Source Atlas RPC command inventory RPC Source Atlas pages No blocking issue found after cleanup Recent Source Atlas cleanup commits RPC Source Atlas pages are source-review inventories, keep Draft status, and state that commands have not been run. Live submission and block/header submission remain separated from dry-run or read-only workflows.
2026-07-01 Source Atlas wallet command inventory Wallet Source Atlas pages No blocking issue found after cleanup Recent wallet Source Atlas cleanup commits Wallet Source Atlas pages keep commands as source-observed inventories. Spend, key, passphrase, restore, rescan, and encryption examples remain untested and should not become beginner copy/paste guidance.
2026-07-02 Network RPC command inventory docs/developers/source-atlas/rpc-network.md, docs/verification/command-testing.md, docs/verification/command-smoke-test-plan.md Network commands needed explicit tracking after network RPC source review a5960c4, 21ef11d Added read-only network status candidates and kept manual peer, peer-list, and network-active commands out of early testing. No network command has a local test record yet.
2026-07-02 Old-path/stale-value repository search spot check repository search for BitcoinII-Dev/BitcoinII, MinBIP9WarningHeight 292, and 292 Search returned no matches, but search reliability is not treated as complete proof No change Direct page cleanup already fixed known stale references. A more reliable local grep or full checkout should still be used before public release.
2026-07-04 Codex command-shaped audit Command scan pages, smoke-test plan, command tracker, RPC overview, node/wallet/mining/config/exchange pages, Source Atlas RPC/wallet/network pages No blocker for first narrow private review. Suggested two narrow improvements: add deposit-monitoring inline command caveats and split RPC placeholder examples by risk. 2b7005a, 4622800 Codex could not run a true local repo-wide rg because no checkout was available, so this is sufficient for the narrow command-safety packet but not public-launch readiness.

Codex audit summary, 2026-07-04

Section titled “Codex audit summary, 2026-07-04”

Codex reported:

  • No blocker for first narrow private review.
  • Reviewed pages consistently say examples are untested, placeholders, source-observed, or not suitable for publication.
  • docs/exchange/deposit-monitoring.md benefited from inline caveats around wallet context and getnewaddress state changes.
  • docs/developers/rpc-overview.md benefited from splitting placeholder examples into risk groups so funds-moving examples do not sit beside harmless status calls.
  • A true local repository-wide grep is still needed before public launch.

Still to scan

Section titled “Still to scan”
  • Any remaining command blocks found by repository search or full local grep.
  • Any new user-facing command examples added after this scan.
  • Release verification command examples when artifact data becomes available.
  • Ecosystem/service command examples after live service checks.

Known acceptable cases

Section titled “Known acceptable cases”

It is acceptable to list command names when:

  • The page clearly says commands are untested.
  • The command is part of an inventory or source-review list.
  • The command links to Command testing status.
  • The command is marked Do not publish for normal docs.

Next actions

Section titled “Next actions”
  1. Use a full local checkout or stronger grep to scan remaining command terms before broad review.
  2. Continue first narrow private review with the command-safety packet.
  3. Keep risky command examples split by risk group.
  4. Update documentation coverage after larger command-tracker changes.
Section titled “Related pages”

Verification

Section titled “Verification”

Status: Draft Primary sources checked: Current MoreBC2 command tracker, RPC overview, node, wallet, mining, exchange, configuration, developer workflow pages, Source Atlas RPC/wallet/network pages, command smoke-test plan, and Codex command-shaped audit report Notes: This page records command-example scans across the main user/service-facing, developer workflow, Source Atlas RPC/wallet/network command inventory pages, updated command tracker/smoke-test plan, and first Codex command-shaped audit. A full local grep is still needed before public release.