CommitWatch RSS
BT
← All projectsBTCPay Server

BTCPay Server

Free, open-source, self-hosted Bitcoin payment processor supporting on-chain and Lightning payments.

BitcoinLightning NetworkPayment infrastructureNormal
Source repository ↗Security policy ↗
Repository coverage

563 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

77security candidates198second-pass queue275AI analyses
65commits · 30 days
111commits · 60 days
313commits · 180 days
563commits · 365 days
Backfill bands
Aug 8 → Feb 9247 seen22 candidatesComplete
Feb 9 → Jun 9197 seen39 candidatesComplete
Jun 9 → Jul 954 seen0 candidatesComplete
Jul 9 → Aug 865 seen16 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

53/100 average clarity
76Strong · 80–100
134Adequate · 60–79
215Thin · 40–59
138Opaque · 0–39
6security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Nicolas Dorier36544203346
Cerberus622290
rockstardev31612049
Abhijay Jain26610087
Chukwuleta Tobechi1857070
thgO.O29411065
Tim522074
Atharva Borade711067
dstrukt413065
Pavlenex412065
psam21312068
Nicholas Halka111091
Analysis record

Published AI watches

Last scanned 48 minutes ago

Informational 15 AI analysisMessage 18 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update Changelog

This commit only edits the wording of a changelog entry for BTCPay Server 2.4.2. It does not change any code, configuration, or executable files. The edit makes the release sound more urgent, but the commit itself is purely documentation a…

Changelog language changed to describe a critical, actively exploited vulnerability in release 2.4.2No code, configuration, or dependency changes present in the commitSecurity issue is referenced but not fixed or explained in this diff
fbf761f3by Nicolas Dorier+1−11 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 49 AI analysisMessage 28 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Disabled unwanted routes

This commit marks several public methods on ASP.NET Core controllers with [NonAction], which prevents them from being exposed as web-accessible HTTP routes. Without this attribute, these helper methods could be reached directly via URL, po…

Public controller methods exposed as unintended HTTP routesRouting-level access-control hardeningPotential bypass of intended controller action flow
6689cad4by Nicolas Dorier+9−05 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 64 AI analysisMessage 38 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Changelog for 2.4.2

This commit is a version bump and changelog for BTCPay Server 2.4.2. The changelog describes two security-related changes: disabling Basic authentication by default shortly after account creation, and fixing a TOTP two-factor authenticatio…

Vendor describes security fixes in changelogTOTP two-factor authentication bypass via Greenfield Basic authenticationBasic authentication disabled by default after account creation
3e2928cfby Nicolas Dorier+29−12 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 18 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update translations

This commit only adds, removes, and reorders English text strings used for translations and user-interface labels in BTCPay Server. There are no code logic changes, no security settings being enabled or disabled, and no behavior changes. I…

8d5f52daby Nicolas Dorier+17−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 25 AI analysisMessage 0 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

bump deps

This commit updates several third-party software libraries and a test Docker image to newer versions. It also removes one library (AngleSharp) that was no longer needed. Dependency updates can fix security bugs in those external packages, …

Dependency version bumps for packages that handle HTML sanitization (HtmlSanitizer) and Bitcoin protocol parsing (NBitcoin/NBXplorer)Removal of unused AngleSharp package referenceNo commit-level description of security fixes or CVEs
1c16e265by Nicolas Dorier+10−1110 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 62 AI analysisMessage 63 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Disable Greenfield Basic Auth by default after 5 min of user creation (#7492)

This change makes BTCPay Server's Greenfield API stop accepting username-and-password 'Basic' authentication by default for existing users. New accounts can still use it for only the first five minutes after creation to set up an API key. …

Disables Basic authentication by default after a 5-minute onboarding windowAdds per-user opt-in flag for Basic auth in data model, API, and UITightens rate-limit bypass to require a recently created account
61cb0702by Nicolas Dorier+74−612 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Containerize store settings views into sections & clean up views (#7448)

This commit is a user-interface redesign, not a security fix. It wraps store settings pages in new visual 'section' containers, updates headings and spacing, and adjusts CSS styling. No code behavior, permissions, or data handling changed.

b8774051by dstrukt+715−54920 files
No security note in commit
Open full analysis →Source commit ↗
Critical 86 AI analysisMessage 75 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix: TOTP 2FA bypass via Greenfield Basic auth (#7491)

BTCPay Server fixed a bug where accounts protected only by TOTP-based two-factor authentication (2FA) could access the Greenfield API using just an email and password, skipping the second factor. The change now blocks Basic authentication …

2FA bypassauthentication logic flawTOTP bypass
c173a919by Nicolas Dorier+1−11 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 23 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Adds table (wallet transactions) column controls (hide/show/re-order) (#7474)

This commit adds a user-facing preference feature to BTCPay Server's wallet transactions table: a dropdown that lets users show, hide, and reorder columns. Preferences are saved in the browser's localStorage. The change is a routine UI enh…

No security-relevant keywords in commit title or messagePure client-side UI feature using localStorageNo changes to authentication, authorization, or input processing
033460e7by dstrukt+422−157 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Cover all generated witness PSBTs

This commit changes how BTCPay Server decides whether a Bitcoin transaction input is a SegWit (witness) type when building PSBTs (Partially Signed Bitcoin Transactions). Previously the code only recognized three specific SegWit formats: na…

Broadens SegWit detection from a fixed allow-list to any ScriptType.Witness, mitigating future-version compatibility issuesAdds missing WitnessUtxo population in two wallet PSBT creation pathsWitness UTXO data reduces reliance on NonWitnessUtxo (full previous transaction) for SegWit inputs, which is a known PSBT hardening recommendation
ede7cc70by rockstardev+10−133 files
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 28 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Preserve imported PSBTs

This commit removes a single line that automatically added witness UTXO data to SegWit inputs when decoding a PSBT. The change is titled 'Preserve imported PSBTs,' suggesting the previous behavior was modifying user-supplied transaction da…

PSBT mutation behavior changedWitness UTXO data no longer auto-injected for SegWit inputsPotential data-integrity / non-repudiation consideration for imported PSBTs
31ad661aby rockstardev+0−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 40 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Finalize stale pending multisig transactions on read

This commit fixes a bookkeeping bug in BTCPay Server's multisig (multi-signature) transaction tracker. Previously, a pending transaction could silently collect enough signatures to be finalized, but the system would still label it as 'Pend…

State-machine inconsistency: persisted transaction state could diverge from actual signature countMultisig workflow: incorrect 'Pending' label for a transaction that is actually ready to broadcastNo input validation or authorization changes in the diff
1bcfc148by rockstardev+60−62 files
No security note in commit
Open full analysis →Source commit ↗
Low 45 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Include witness UTXOs in SegWit PSBTs

This commit changes BTCPay Server so that when it builds or decodes Partially Signed Bitcoin Transactions (PSBTs), it explicitly adds a compact 'witness UTXO' record for any SegWit inputs. Previously, some SegWit PSBTs may only have carrie…

PSBT data completeness change for SegWit inputsPotential prior state: SegWit PSBTs may have been distributed without witness UTXOsHardware-wallet compatibility / BIP-174 compliance improvement
63236df4by rockstardev+83−04 files
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Address pending signature retry review feedback

This commit is a follow-up code review patch for BTCPay Server's pending Bitcoin transaction (multisig) signing feature. It tightens when the service logs a warning versus a debug message after a failed finalization attempt, and it removes…

Logging level change reduces false-warning noise but could mask real finalization failures if SignaturesNeeded is incorrectly zeroRemoval of additionalPsbt parameter prevents accidental combination of an unvalidated extra PSBT into the effective PSBTPer-input signature progress tracking refined to avoid prematurely counting aggregate signatures
89b8f49cby rockstardev+109−102 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Simplify pending finalization failure logs

This commit is a minor code cleanup that simplifies how BTCPay Server writes log messages when a pending multi-signature transaction fails to finalize. It removes the list of failed input indexes from the log and merges two nearly identica…

7e71c45eby rockstardev+11−271 file
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Bound pending multisig signature history

This change tightens how BTCPay Server stores signature attempts for multi-signature Bitcoin transactions. Previously, every submitted PSBT (a partially signed transaction file) was kept in history, even if it added no real progress. Now o…

Unbounded history/list growth bounded by logical retention gateResource consumption / storage abuse vector mitigatedLogic change in multi-signature signature collection path
eb0f15caby rockstardev+32−242 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Log pending transaction finalization errors

This commit only adds more detailed logging when a pending multi-signature Bitcoin transaction fails to finalize. It does not change how transactions are validated, authorized, or executed. There is no security vulnerability being fixed he…

c3fe1d7bby rockstardev+29−41 file
No security note in commit
Open full analysis →Source commit ↗
Low 42 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix pending multisig signature retries

This commit fixes a bug in BTCPay Server's multisig transaction handling. Previously, the service could get stuck in a 'Pending' state even when enough valid signatures had been collected, because it discarded new signature submissions tha…

Logic flaw in multisig signature collection could leave transactions permanently pending despite sufficient valid signaturesPreviously ignored distinct PSBTs that did not immediately increase signature progressMissing retry of transaction finalization after collecting additional signatures
ebeafc5aby rockstardev+153−182 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 0 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix typo

This commit changes one word in the project's changelog, adding the word 'the' to a bullet point. It is a grammatical typo fix with no effect on software behavior, security, or user data.

2ed0fa17by Nicolas Dorier+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 40 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Add race condition safe InvoiceRepository.UpdateMetadata (#7475)

This commit changes how BTCPay Server stores invoice comments and metadata. Previously, comments were saved in a separate field and could be updated with a method that was not safe when multiple requests happened at the same time. The patc…

Commit title explicitly describes a race condition fixReplaced read-modify-write metadata update with atomic PostgreSQL jsonb_set operationRemoved dedicated API 'comment' field, narrowing update surface
5664bd41by Nicolas Dorier+51−9010 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-priorityAdd: Implement UpdateCrowdfundApp endpoint and client method (#7202)by SiriusBig · 8e748f9d · Mar 25, 2026 · 4 filesMessage 91 · StrongTriage 8Details
Commit message · SiriusBig

Add: Implement UpdateCrowdfundApp endpoint and client method (#7202)

* Add: Implement UpdateCrowdfundApp endpoint and client method

- Added a new API endpoint to update properties of a Crowdfund app in GreenfieldAppsController.
- Introduced request validation for the update operation, ensuring required fields are checked.
- Updated Swagger documentation to include the new PUT operation for Crowdfund apps.
- Added corresponding client method in BTCPayServerClient for making requests to the new endpoint.

* Enhance: Update ToCrowdfundSettings method to merge request with existing settings

- Modified the ToCrowdfundSettings method to accept existing settings, allowing for selective updates based on non-null properties in the request.
- Updated the call to ToCrowdfundSettings in the app update logic to include the existing settings.

* Refactor: Adjust description handling in Crowdfund app updates

- Updated the logic to preserve the description during partial updates, ensuring it defaults to existing settings only when omitted by the client.
- Modified validation to only reject empty descriptions when explicitly provided, improving compatibility with legacy apps.

* Enhance: Add extra validation for reset-related fields in Crowdfund app updates

- Implemented additional checks when patching reset-related fields without specifying ResetEvery, ensuring a start date is provided and the reset amount is valid.
- Improved error handling to guide users on required fields for effective goal resetting.

* Add Update tests to CanCreateReadUpdateAndDeleteCrowdfundApp

Add Crowdfund PUT tests: full update, partial update, validation

* Fix UpdateCrowdfundApp to behave as a true PUT, not a PATCH

The previous implementation silently ignored missing fields and merged them from the existing app, which is inconsistent with the rest of the API. Users who want to update should GET, modify, then PUT the full
payload.

- Remove merge overload ToCrowdfundSettings(request, existing)
- Always call ValidateAppRequest so AppName is required
- Always overwrite app.Name and app.Archived unconditionally
- Update tests: replace patch-specific cases with proper PUT validation
- Fix swagger description and add missing displayPerksRanking field

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validation
Lower-prioritySubscriptions: Can delete subscribers via UI and API (#7254)by Nicolas Dorier · fa6baded · Mar 24, 2026 · 8 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier

Subscriptions: Can delete subscribers via UI and API (#7254)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedRemove useless codeby Nicolas Dorier · ab438f42 · Mar 24, 2026 · 4 filesMessage 28 · OpaqueInformational 12Details
Commit message · Nicolas Dorier

Remove useless code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 12/100

This commit is a small cleanup in the BTCPay Server subscriptions plugin. It removes redundant assignments to the PreviousPlan property (which is now set only through the constructor), makes a property read-only, fixes a test to wait for an event, and corrects a namespace reference. There is no indication this fixes a security vulnerability.

Lower-priorityRevert to Include plan started eventby Chukwuleta Tobechi · 939480db · Mar 24, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Chukwuleta Tobechi

Revert to Include plan started event

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityfeat: add RTL Language Support (#7259)by Abhijay Jain · 20d5a0dd · Mar 24, 2026 · 3 filesMessage 88 · StrongTriage 0Details
Commit message · Abhijay Jain

feat: add RTL Language Support (#7259)

* feat: add RTL Language Support

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: addressed code suggestions

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: added script

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: updating check lang on switch

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: sync <html lang> with active locale in updateLanguageDir

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

---------

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queuedresolve code rabbitby Chukwuleta Tobechi · 5f4f4495 · Mar 23, 2026 · 2 filesMessage 28 · OpaqueLow 28Details
Commit message · Chukwuleta Tobechi

resolve code rabbit

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 28/100

This commit makes two small fixes in the BTCPay Server Subscriptions plugin. It changes a test helper so two UI form-filling branches are mutually exclusive, and it tightens when a subscription plan change can be scheduled and updates statistics when a plan actually changes. There is no clear security vulnerability in the diff itself; it looks like a routine bug-fix or code-review follow-up.

Lower-priorityfeedback fixes, include tests and update swaggerby Chukwuleta Tobechi · d88d20f5 · Mar 23, 2026 · 5 filesMessage 55 · ThinTriage 0Details
Commit message · Chukwuleta Tobechi

feedback fixes, include tests and update swagger

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI review queuedRefactor: Move Forms in its own plugin folder (#7261)by Nicolas Dorier · 6b3c39bd · Mar 23, 2026 · 27 filesMessage 70 · AdequateInformational 15Details
Commit message · Nicolas Dorier

Refactor: Move Forms in its own plugin folder (#7261)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 15/100

This commit is a code reorganization: the existing Forms feature is moved from the core BTCPayServer project into its own plugin folder. Files are renamed and namespaces adjusted, but the actual form logic, validation, and behavior remain essentially unchanged. There is no indication this change fixes or introduces a security vulnerability.

Lower-priorityRemove useless code (#7262)by Nicolas Dorier · 984076c5 · Mar 23, 2026 · 1 fileMessage 43 · ThinTriage 0Details
Commit message · Nicolas Dorier

Remove useless code (#7262)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityfix Missing <tr> wrapper in table headerby Chukwuleta Tobechi · 4c154845 · Mar 22, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Chukwuleta Tobechi

fix Missing <tr> wrapper in table header

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateAllow upgrade/downgrade of a subscription at period endby Chukwuleta Tobechi · ea7bb40b · Mar 22, 2026 · 12 filesMessage 50 · ThinInformational 20Details
Commit message · Chukwuleta Tobechi

Allow upgrade/downgrade of a subscription at period end

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
update trust
AI analysis · Informational 20/100

This commit adds a new feature to BTCPay Server's subscription plugin that lets users schedule a plan upgrade or downgrade to take effect at the end of their current billing period, instead of happening immediately. It also lets users cancel a scheduled change. The change is a normal feature addition and does not appear to fix or introduce a security vulnerability based on the code shown.

Lower-priorityRefactor: Move BitpayIPNSender in plugin dirby Nicolas Dorier · aa14c9ac · Mar 20, 2026 · 5 filesMessage 57 · ThinTriage 0Details
Commit message · Nicolas Dorier

Refactor: Move BitpayIPNSender in plugin dir

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityshow payment method on receipt (#7226)by Chukwuleta Tobechi · 961b097c · Mar 20, 2026 · 1 fileMessage 76 · AdequateTriage 0Details
Commit message · Chukwuleta Tobechi

show payment method on receipt (#7226)

* show payment method on receipt

* fix coderabbit suggestion

* flip payment view

* include payment link to destination

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityGive some time for plugins nav extensions to use GetStoreDataOrNull() or model.Storeby Nicolas Dorier · 68f088dd · Mar 20, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Give some time for plugins nav extensions to use GetStoreDataOrNull() or model.Store

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedfix: store dashboard wallet balance chart and numbers widget (#7247)by Abhijay Jain · 36234754 · Mar 20, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · Abhijay Jain

fix: store dashboard wallet balance chart and numbers widget (#7247)

* fix: store dashboard wallet balance chart and numbers widget

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* fix: transfor the API Unix timestamp labels to ISO

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: reverted numbersUrl period sync feature

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

* refactor: removed rest of files

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

---------

Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit fixes a store dashboard widget that displays wallet balance charts and numbers. The changes ensure chart labels are rendered correctly (especially the last data point) and convert API timestamps from Unix seconds into ISO date strings that the chart library expects. There is no security-relevant change.

AI review queuedbump dotnet imageby Nicolas Dorier · f127ca71 · Mar 20, 2026 · 2 filesMessage 28 · OpaqueLow 31Details
Commit message · Nicolas Dorier

bump dotnet image

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 31/100

This commit updates the .NET runtime and SDK Docker images used to build and run BTCPay Server from version 10.0.200/10.0.4 to 10.0.201/10.0.5. These are patch-level updates to the underlying Microsoft .NET platform. Such updates typically include bug fixes and security fixes, but the commit message does not say this is a security update and no specific vulnerability is referenced. The change is routine maintenance rather than a fix for a known, actively exploited flaw in BTCPay Server itself.

AI review queuedbump versionby Nicolas Dorier · 4d3cd760 · Mar 20, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

bump version

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only changes a single version number in a build file from 2.3.6 to 2.3.7. There is no code change, no bug fix, and no security-related content in the diff.

Lower-priorityfix: Price and currency tampering via mirror fields in public forms/POS/crowdfund (#7245)by Cerberus · 8d0439f4 · Mar 15, 2026 · 2 filesMessage 90 · StrongTriage 0Details
Commit message · Cerberus

fix: Price and currency tampering via mirror fields in public forms/POS/crowdfund (#7245)

Co-authored-by: Cerberus Merlin <merlin@cerberus.security>

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Security candidatefix: Cross-store privilege escalation to approved pull payments/payouts in GreenfieldPullPaymentController (#7244)by Cerberus · 3c839152 · Mar 15, 2026 · 1 fileMessage 90 · StrongHigh 81Details
Commit message · Cerberus

fix: Cross-store privilege escalation to approved pull payments/payouts in GreenfieldPullPaymentController (#7244)

Co-authored-by: Cerberus Merlin <merlin@cerberus.security>

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
credential or privilege state
AI analysis · High 81/100

This commit fixes a privilege escalation bug in BTCPay Server's Greenfield API. Two authorization checks were passing 'null' instead of the actual store ID when verifying whether a user could auto-approve pull payments or payouts. In BTCPay Server's authorization system, a null resource likely causes the check to fall back to a global permission evaluation, meaning a user who only had permission on one store could potentially approve or auto-approve pull payments/payouts for other stores where they should have been denied. The patch simply passes the correct storeId so the permission is scoped properly.

Lower-priorityReintroduce PolicyRequirement(string policy) to avoid breaking pluginsby Nicolas Dorier · 99ddc693 · Mar 14, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Reintroduce PolicyRequirement(string policy) to avoid breaking plugins

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Lower-priorityAdd back SecurityExtensions.cs to avoid plugin breakingby Nicolas Dorier · cd067ca3 · Mar 14, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Add back SecurityExtensions.cs to avoid plugin breaking

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
AI review queuedUpdate Changelogby Nicolas Dorier · 0bb223b0 · Mar 14, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Update Changelog

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates the project's changelog file, adding one line describing a previously completed feature (wallet label filtering). It makes no code changes and has no security relevance.

Lower-priorityChangelog for 2.3.6 (#7227)by Nicolas Dorier · 2ac99d8d · Mar 14, 2026 · 1 fileMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier

Changelog for 2.3.6 (#7227)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityFix: Show a popup before re-generate reset recovery code (#7241)by Nicolas Dorier · fdf59b45 · Mar 14, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Show a popup before re-generate reset recovery code (#7241)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedFeat: Improved Label System - Add search filtering to label dropdown menu (#7210)by rollforsats · c5f48e7b · Mar 14, 2026 · 6 filesMessage 100 · StrongInformational 15Details
Commit message · rollforsats

Feat: Improved Label System - Add search filtering to label dropdown menu (#7210)

* improved label system - add filtering using search bar on the filter dropdown when labels exceed more than 20

* Update BTCPayServer/Views/UIWallets/WalletTransactions.cshtml

* magic number 20

* magic number js reference error

* string localization

* use ellipses instead of separate periods in the Search Labels string. Use tag helper asp-route-labelFilter to filter labels instead of Url.Action.

* use template to clone filtered label items

* Ensuring top 20 most used labels are displayed first

* Adding test to validate that labels filter is displayed correctly

Co-authored-by: rockstardev <5191402+rockstardev@users.noreply.github.com>

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit adds a search box to the wallet transaction label filter dropdown. When a wallet has more than 20 labels, users can now type to search instead of scrolling through a long list. It also shows how often each label is used and lists the 20 most popular labels first. There is no security-relevant change here.