AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 13 Bitcoin

bkpr: restore run-recorder.

Public commit record

What the developer wrote

Authored by Rusty Russell

58/100 · Thin
bkpr: restore run-recorder.

This requires us to turn "sql" calls into calls to a local db, which
means pulling in a lot of infrastructure. But it's possible.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Descriptive subject✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit restores a bookkeeping plugin test that had been disabled. It adds a new test file that exercises account, chain-event, channel-event, and on-chain-fee recording logic against a temporary local SQLite database. The changes are confined to test code and build files; no production plugin or node logic is modified.

Recommended action

No security action required. Treat as normal test-infrastructure maintenance. If reviewing further, verify that the restored test passes in CI and that the local SQL stub does not accidentally get compiled into production builds.

Security signals we found

01

No changes to network-facing code, cryptographic operations, or consensus logic.

02

No modifications to production plugin behavior; changes are test-only.

03

No new dependencies on untrusted input parsing in production paths.

04

Test harness uses temporary SQLite databases and asserts on query results.

Risk score

Why this scored 13/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 9/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.