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
112commits · 60 days
314commits · 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 1 minute 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.

AI review queuedLocalize Blazor strings that the text-translate TagHelper can't reach (#7423)by Wiredancer · 364e6be9 · Jul 7, 2026 · 4 filesMessage 81 · StrongInformational 15Details
Commit message · Wiredancer

Localize Blazor strings that the text-translate TagHelper can't reach (#7423)

`text-translate`/`html-translate` are handled by TranslateTagHelper, an
MVC TagHelper that only runs while rendering Razor (.cshtml) views.
Blazor components do not execute TagHelpers, so these attributes are
inert inside .razor files: the literal English text is always rendered,
regardless of the active language.

Switch the affected strings to @StringLocalizer[...] / @ui.StringLocalizer[...],
which resolves correctly in Blazor (as already used e.g. for the
notifications button tooltip on the very same component):

- NotificationsDropDown.razor: "Notifications", "Mark all as seen",
"No new notifications", "View all"
- PosLoginCode.razor: "Signed in user", "None, just open the URL"
(adds the IStringLocalizer injection)
- XPubSelect.razor: "Account"

Also register the newly-translatable strings in Translations.Default.cs.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit fixes a localization bug in BTCPay Server's Blazor user interface components. Some text strings were not being translated into the user's chosen language because they relied on a translation mechanism that only works in older Razor view files, not in newer Blazor components. The change switches those strings to use Blazor-compatible localization and registers the new translatable phrases in the default translation file. There is no security impact.

Lower-priorityReturn NotFound when opening payouts for a missing pull payment (#7429)by Atharva Borade · 39119692 · Jul 7, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · Atharva Borade

Return NotFound when opening payouts for a missing pull payment (#7429)

FindAsync returns null when the pull payment id no longer exists (e.g. a
deleted/archived pull payment or a stale bookmarked URL). Calling GetBlob()
on it threw a NullReferenceException and rendered a 500. Look up the pull
payment up front and return NotFound() if it's missing, matching the
pattern used elsewhere.

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityfix: standardize topbar dropdown menus (#7425)by thgO.O · 36eaf4ae · Jul 7, 2026 · 7 filesMessage 65 · AdequateTriage 0Details
Commit message · thgO.O

fix: standardize topbar dropdown menus (#7425)

65/100 · AdequateMessage clarity
✓ 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 queuedFix "File traversal detected" crash processing plugin commands on Windows (#7422)by Andrew Camilleri · a8c01be5 · Jul 7, 2026 · 1 fileMessage 58 · ThinLow 33Details
Commit message · Andrew Camilleri

Fix "File traversal detected" crash processing plugin commands on Windows (#7422)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Low 33/100

This commit fixes a bug in BTCPay Server's plugin system where a safety check that prevents directory traversal attacks was accidentally rejecting valid plugin names on Windows. The original code always appended a '/' slash, but Windows uses '\' as its path separator, so the safety check compared paths with mismatched slashes and falsely flagged them as attacks, causing a crash. The fix makes the trailing slash match the operating system's separator. There is no direct evidence in the commit that an actual security vulnerability was exploited; it appears to be a bug fix for a false-positive crash.

Lower-priorityGreenfield: support includePaymentMethods on get invoice (#7426)by Atharva Borade · 76e089ae · Jul 6, 2026 · 4 filesMessage 58 · ThinTriage 0Details
Commit message · Atharva Borade

Greenfield: support includePaymentMethods on get invoice (#7426)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityFix broken default rate calculation for DASHby Nicolas Dorier · 5e7fbbf7 · Jul 4, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Fix broken default rate calculation for DASH

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priority Greenfield: support payoutMethods array on invoice refund (#7413)by Atharva Borade · d4da8916 · Jul 3, 2026 · 5 filesMessage 58 · ThinTriage 0Details
Commit message · Atharva Borade

Greenfield: support payoutMethods array on invoice refund (#7413)

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 queuedMake test less flakyby Nicolas Dorier · 7cb03bb3 · Jun 30, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Make test less flaky

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit removes Bootstrap tooltip attributes from a few disabled buttons and archive links in the invoice view. It is a test-flakiness fix with no apparent security relevance.

Lower-priorityFix NBXplorer error rendering (#7421)by Michael Rihani · abd94b97 · Jun 30, 2026 · 1 fileMessage 53 · ThinTriage 0Details
Commit message · Michael Rihani

Fix NBXplorer error rendering (#7421)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityFix: Server admin unable to see the store of usersby Nicolas Dorier · 2a131156 · Jun 29, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: Server admin unable to see the store of users

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritybind to all interface even outside of the test container (#7410)by napoly · 250fd224 · Jun 29, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · napoly

bind to all interface even outside of the test container (#7410)

68/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityFix: LNDHub should be supported by default (Fix #7418)by Nicolas Dorier · 51a5d1d3 · Jun 27, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · Nicolas Dorier

Fix: LNDHub should be supported by default (Fix #7418)

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 queuedAdd blog post announcementby Nicolas Dorier · e5c2a4cc · Jun 25, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Add blog post announcement

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only adds a link to a blog post announcement in the changelog. It contains no code changes, no security fixes, and no functional modifications.

Lower-priorityAdd tether plugin to plugin compat checkby Nicolas Dorier · 50ae4bfc · Jun 25, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add tether plugin to plugin compat check

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedRestore lndhub supportby Nicolas Dorier · cea07e5e · Jun 24, 2026 · 2 filesMessage 28 · OpaqueInformational 16Details
Commit message · Nicolas Dorier

Restore lndhub support

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

This commit reverts a planned removal of LNDHub support by updating a single Lightning library version and editing the changelog. It is a feature restoration, not a security fix. There is no evidence in the commit of any vulnerability, exploit, or security-relevant change.

AI review queuedFix flaky testby Nicolas Dorier · 23219bc9 · Jun 24, 2026 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix flaky test

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit fixes a flaky automated test for the global search feature. The JavaScript change makes the search run automatically if a query is already present when the search UI opens, and the test code is simplified to remove a special screenshot-on-failure workaround. There is no security issue here.

Lower-priorityRemove useless SubTitle property to global search vmby Nicolas Dorier · 54521cf4 · Jun 23, 2026 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Remove useless SubTitle property to global search vm

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAdd entry for dyndns setupby Nicolas Dorier · 2699770c · Jun 23, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add entry for dyndns setup

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityTry to catch flaky GlobalSearch testby Nicolas Dorier · 67cda519 · Jun 23, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Nicolas Dorier

Try to catch flaky GlobalSearch test

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityAdd breaking change notice to changelogby Nicolas Dorier · 6828fc83 · Jun 22, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add breaking change notice to changelog

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityBumping LND to 0.21.0-betaby rockstardev · 307acf4d · Jun 22, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · rockstardev

Bumping LND to 0.21.0-beta

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAdd support for core lightning 26.06 (#7412)by Nicolas Dorier · 77839370 · Jun 22, 2026 · 6 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add support for core lightning 26.06 (#7412)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedImprove phoenixd, remove support for deprecated lightning backendby Nicolas Dorier · 009f458e · Jun 19, 2026 · 22 filesMessage 50 · ThinInformational 22Details
Commit message · Nicolas Dorier

Improve phoenixd, remove support for deprecated lightning backend

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 22/100

This commit is a routine maintenance update for BTCPay Server. It removes support for three older/deprecated Lightning payment backends (Lightning Charge, LNDHub, and LNBank), updates the phoenixd integration, bumps a couple of library versions, and adjusts tests accordingly. There is no indication in the commit that this fixes an active security vulnerability or introduces new attack paths.

Lower-priorityfix: bulk archive pull payments scoped to current store (#7407)by Atharva Borade · ee2a64c2 · Jun 18, 2026 · 2 filesMessage 93 · StrongTriage 0Details
Commit message · Atharva Borade

fix: bulk archive pull payments scoped to current store (#7407)

MassAction was passing selectedItems to Cancel() without a store filter,
allowing a user with CanArchivePullPayments on store A to archive pull
payments from other stores. Filter PullPaymentIds by StoreIds in
HandleCancel before attaching the archived flag.

Signed-off-by: atharrva01 <adityashinde1525@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
AI review queuedFix: When a server has too many apps, the Policies page timeout or crash (#7406)by Nicolas Dorier · e6085835 · Jun 17, 2026 · 4 filesMessage 70 · AdequateLow 37Details
Commit message · Nicolas Dorier

Fix: When a server has too many apps, the Policies page timeout or crash (#7406)

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: broader security terminology
AI analysis · Low 37/100

This commit fixes a performance problem on the BTCPay Server 'Policies' settings page. Previously, the page tried to load a dropdown list of every app on the server, which could time out or crash when there were many apps. The fix replaces the dropdown with a simple text box where the administrator types an app ID directly. It also adds validation to reject invalid app IDs instead of crashing. The change is primarily a reliability/performance fix, but it slightly changes how app IDs are entered and validated.