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

Feature: Cold wallet transaction support via Greenfield API (#7068)

Public commit record

What the developer wrote

Authored by Nicholas Halka

91/100 · Strong
Feature: Cold wallet transaction support via Greenfield API (#7068)

* Enables unsigned PSBT transaction creation

Adds support for creating unsigned PSBT transactions, facilitating multisig withdrawal workflows.
Introduces a new API endpoint for broadcasting on-chain transactions.
Enhances transaction creation to allow opting out of server-side signing.

* Update Docs And Tests

* Removes Unused Transaction field from PSBT creation response
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit adds new API features to BTCPay Server so users can create unsigned Bitcoin transactions (PSBTs) and broadcast already-signed transactions through the Greenfield API. It is a feature addition, not a bug fix. The code does not appear to introduce an obvious vulnerability, but it changes how wallet transactions are authorized and signed, which is security-sensitive. There is no vendor statement or external report saying this commit fixes a security issue.

Recommended action

Treat this as a normal feature commit. Review the new broadcast endpoint for PSBT parsing robustness, ensure authorization checks are appropriate for unsigned PSBT creation, and verify that the relaxed hot-wallet policy cannot be abused to sign or broadcast transactions without proper permissions. No immediate security patch action is indicated by the supplied materials.

Security signals we found

01

New API surface for transaction creation and broadcasting

02

Authorization gate relaxed for unsigned PSBT creation (hot-wallet policy only applies when signing on server)

03

New broadcast endpoint parses and finalizes PSBTs from user input before broadcasting

04

No explicit security advisory, CVE, or bug-fix language in commit message or diff

Risk score

Why this scored 32/100

Our methodology →
Potential impact 5/30
Exploitability 5/25
Stealth signal 5/15
Affected reach 8/15
Confidence 6/10
Evidence quality 3/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.