P1 after comparing with the other PRs here (assessed alone as P2): Raised to P1: release-binary verification tooling counting revoked/expired keys toward the quorum is a disclosed security defect in a tool downstream users rely on, the most consequential problem in this category.
P2 because verification tooling counted revoked and expired keys toward minimum required signatures
Fixes a responsibly disclosed flaw while retaining historical release verification via an explicit flag
Ready to review; all reviewer concerns have been addressed in pushed updates
P2 after comparing with the other PRs here (assessed alone as P3): Raised to P2 and moved up: the wrapper is simply unusable on distros with non-default libexec layout (issue #35785), the same class of supported-platform breakage as #36105, so the two must share a band.
P3 because it enables the bitcoin wrapper command to work on distributions with non-default layouts
P2 after comparing with the other PRs here (assessed alone as P3): Raised to P2: the problem is recurring privacy/deanonymization leaks in private broadcast, a security-class issue, not merely a new CLI utility.
P3 because it provides a standalone utility to privately broadcast transactions without running bitcoind
Offers isolated relay over Tor and BIP324 as a dedicated CLI tool
Author directed review to slimmed-down PR #36628 instead
No review verdicts recorded
No substantive discussion or review comments yet
Author noted that reviewers should look at PR #36628 instead
P2 after comparing with the other PRs here (assessed alone as P3): Raised to P2 and moved up: substantial snapshot-load performance gain plus an offline bitcoin-util inspection tool, and #35054 (P2P UTXO set sharing) builds on it.
P3 because it adds an offline tool to inspect snapshot statistics and commitments
Helps developers and node operators analyze assumeutxo snapshots without running bitcoind
Ready to review
No review verdicts recorded
Unaddressed objection: adds assumeutxo complexity to consensus paths (l0rinc)
Questioned whether speeding up snapshot loading justifies code complexity (l0rinc)
Author defended the approach for fast node startup with no further reply yet (l0rinc)
1,110 lines added or modified outside tests
213 lines added or modified in tests
472 lines removed in total
27 files, 12 commits
(+)#35608HowHsucontrib: Skip llvm-cov rendering for deterministic fuzz inputs
P3 · speedup
Waiting on author
0 (+1)
Strong
0 + 71 tests
Speed up deterministic fuzz coverage checking for developers
Avoid rendering expensive coverage reports when profile data between runs is identical
P3 after comparing with the other PRs here (assessed alone as P4): Raised from P4: silently swallowing options after a command (e.g. trailing -rpcwallet) is a real user-facing CLI correctness problem, not incidental cleanup.
P4 because updating bitcoin-tx to consume pre-filtered arguments is an incidental follow-up
P3 because it adds a developer productivity tool to test script fragments against consensus logic
Helps developers and researchers validate scripts without building custom test harnesses
Ranking pass: Moved down: a useful developer/researcher convenience tool with no existing breakage behind it, so it ranks below the tool bugs and the dev-time-saving automation in the same band.
P3 because it makes developer dependency checking tools easier to maintain
Keeps dependency rules automatically synchronized with design documentation
Ranking pass: Moved down: maintainability of a developer dependency check with unresolved design-doc objections and a stale branch ranks below concrete tool bugs and user-facing tooling in the same band.
Needs rebase and the author has been silent for over six months
Wait for the author to address blocking design objections
Command-line tools other than the node and its RPC client, and the scripts under contrib: bitcoin-tx, bitcoin-util, the offline bitcoin-wallet tool, the bitcoin wrapper, seed and asmap generation, signet tooling, tracing scripts, and developer helper scripts. Build and release scripts are build; test helpers are tests. The Scripts and tools label is a strong prior.
What matters here
Tools that operators and downstream projects depend on first: seed generation, asmap, signet, and the wallet tool affect real deployments. Then correctness of any tool that touches keys or transactions. Then developer productivity tools that many contributors use. Then niche or single-user scripts, which rank low regardless of size.
Every band, state, and summary on this page is model output against a written category definition, shown with its rationale. It is an unofficial tool and does not speak for the project. Click a row to expand it. The category definition lives in ryanofsky/prio-bitcoin/categories/tools.md; pull requests that improve it are welcome.