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 37 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.

AI review queuedpage-primary should not be automatically translatedby Nicolas Dorier · ed082c55 · Dec 3, 2025 · 35 filesMessage 50 · ThinInformational 15Details
Commit message · Nicolas Dorier

page-primary should not be automatically translated

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a user-interface localization cleanup, not a security fix. It stops the system from automatically translating any button or link with the ID 'page-primary'. Instead, developers must now explicitly mark each primary button/link with a 'text-translate' attribute if they want it translated. The commit adds that attribute to many existing buttons and links so translations continue to work as intended. There is no security vulnerability here.

AI review queuedRename Entitlement -> Feature (#7016)by Nicolas Dorier · fa314d2f · Dec 2, 2025 · 29 filesMessage 43 · ThinInformational 15Details
Commit message · Nicolas Dorier

Rename Entitlement -> Feature (#7016)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ 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 straightforward internal rename from the word 'Entitlement' to the word 'Feature' across the new subscriptions/monetization plugin code. It changes class names, database table names, property names, method names, UI labels, and test helpers, but does not alter any security logic, access checks, or data handling behavior. There is no indication this fixes or introduces a security issue.

Security candidate[Feature] Monetization (#6986)by Nicolas Dorier · bcb5c56b · Dec 2, 2025 · 97 filesMessage 43 · ThinLow 40Details
Commit message · Nicolas Dorier

[Feature] Monetization (#6986)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 40/100

This is a large feature commit titled 'Monetization' that adds subscription and paid-access functionality to BTCPay Server. It introduces new plugins for monetization and subscriptions, changes how user login restrictions are enforced, adds a 'limited login' authentication scheme, and refactors user registration/invitation email flows. The changes touch authentication, authorization, billing, and user lifecycle logic. While the commit is framed as a feature, several areas have security implications: a new limited-login path that signs users in under a separate scheme when normal login is blocked, changes to password-reset and invitation-token handling, and new database entities for plans/subscribers/portal sessions. No explicit security bug is visible in the diff, but the breadth and sensitivity of the modified code means defects could have significant consequences.

Lower-priority(Refactor) : Converted Selenium test for `CanUseRoleManager` and Others to playwright (#6996)by Abhijay Jain · 65dc0a76 · Nov 27, 2025 · 4 filesMessage 96 · StrongTriage 0Details
Commit message · Abhijay Jain

(Refactor) : Converted Selenium test for `CanUseRoleManager` and Others to playwright (#6996)

* refactor: resovled merge conflict

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

* (Refactor): Removed Selenium Test for CanUseRoleManager

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

* Refactor : removed spacing and extra alert message

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

* (Test):Converted/Added Playwright Test for CanSigninWithLoginCode

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

* (Refactor): Removed Selenium Test for CanSigninWithLoginCode

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

* fix: updated UIServerController.Roles.cs to handle storeID

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

* refactor : updated some minor nits

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

* Fix: Preserve store context when deleting server-wide roles from store page

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

* refactor: fix auth mismatch in role Edit/Remove links for store context

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

---------

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

96/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✓ Names security-relevant behavior explicitly
Lower-priorityFix clipboard copy for fiat amounts and other numeric values (#7011)by psam21 · ab6aa1e9 · Nov 27, 2025 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · psam21

Fix clipboard copy for fiat amounts and other numeric values (#7011)

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

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Lower-priorityfeat : add functionality to download language pack (#6943)by Abhijay Jain · 03349b6f · Nov 26, 2025 · 3 filesMessage 81 · StrongTriage 0Details
Commit message · Abhijay Jain

feat : add functionality to download language pack (#6943)

* refactor : added link to translations files

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

* feat : added ability to download langauge pack

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

* refactor: removed link for the edit page

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

* refactor: server-side downloading instead of JavaScript

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

* refactor : addressed request changes

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

* refactor: updated GetDictionary method and other changes

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

---------

Signed-off-by: Abhijay007 <Abhijay007j@gmail.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
AI review queuedFix property name: use CanUseHotWallet and CanCreateNewColdWalletby psam21 · cf692c6e · Nov 24, 2025 · 1 fileMessage 50 · ThinLow 29Details
Commit message · psam21

Fix property name: use CanUseHotWallet and CanCreateNewColdWallet

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100

This is a tiny one-line fix in a BTCPay Server web page that checks whether a user is allowed to set up certain types of cryptocurrency wallets. The old code referenced two properties that appear to have been renamed or replaced. The change simply swaps in the current property names so the page renders the wallet-setup section correctly. It is most likely a routine bug fix, but because it touches permission checks for wallet creation, it could have security-adjacent effects if the wrong users were shown (or hidden from) wallet options.

Security candidateHide wallet creation option when permissions disabledby psam21 · 09e2b3e7 · Nov 24, 2025 · 2 filesMessage 81 · StrongLow 40Details
Commit message · psam21

Hide wallet creation option when permissions disabled

- Pass wallet creation permissions to SetupWallet view
- Conditionally render 'Create a new wallet' based on CanCreateHotWallet || CanCreateWalletWatchOnly
- Remove 'I have a wallet' and 'I don't have a wallet' section headings
- Always show 'Connect an existing wallet' option (import is always allowed)

Fixes #6991

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
credential or privilege statesigning or wallet path
AI analysis · Low 40/100

This commit fixes a UI bug where BTCPay Server was showing a 'Create a new wallet' button to users who did not have permission to create wallets. The button itself was just a link; the actual wallet creation endpoint still enforced permissions separately. So the fix is about hiding an option that shouldn't appear, not about blocking an unauthorized action. It is a defense-in-depth or user-experience security improvement rather than a critical vulnerability.

Lower-priorityIssue 6918 re enable plugin (#6930)by monicamuyama · 5a487985 · Nov 21, 2025 · 5 filesMessage 76 · AdequateTriage 0Details
Commit message · monicamuyama

Issue 6918 re enable plugin (#6930)

* Added the enable button on disabled plugins

* Added the disable function and button for installed plugins

* Changes based on the coderabbitai comments

* Removed markers and added the disable in the same if block as the unistall

* Hide the uninstall button when plugin is queued for enabling

* Removed the duplicate enale function

* Removed the disable button for installed plugins

* Removed the disableplugin functions as they are no longer needed

* Trigger CI pipeline after dotnet restore

* reverted the git ignore

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queuedFix missing assignationby Nicolas Dorier · 0a518320 · Nov 21, 2025 · 1 fileMessage 28 · OpaqueLow 34Details
Commit message · Nicolas Dorier

Fix missing assignation

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

This commit fixes a simple but potentially important coding mistake: a constructor parameter named `loadAssembliesInDefaultLoadContext` was not being saved into its matching field. As a result, the plugin loader's intended setting about where to load assemblies was effectively ignored, and the code would fall back to the default value (false). This could change how plugins are isolated from the main application, potentially weakening the sandbox between plugins and the host.

Lower-priorityTests: All plugin integration tests to resolve plugin's typesby Nicolas Dorier · e002f59f · Nov 21, 2025 · 6 filesMessage 91 · StrongTriage 0Details
Commit message · Nicolas Dorier

Tests: All plugin integration tests to resolve plugin's types

Reported by @napoly

In an integration test for a plugin, attempt to resolve a type provided by that plugin using `BTCPayServerTester`.

For example:
```
tester.GetService<MoneroRPCProvider>();
```

The type should be resolved successfully.

The type fails to resolve.

During the test run, the dotnet runtime attempts to load `MoneroRPCProvider` in the default load context (`AssemblyLoadContext.Default`). It locates the plugin assembly in the test directory and loads it there.

In contrast, when BTCPay Server loads a plugin, it creates a dedicated plugin load context, and the plugin’s `MoneroRPCProvider` is loaded inside that context. This results in two distinct `MoneroRPCProvider` types: one in the default context and one in the plugin context.

This PR forces the plugin context, during integration tests, to load the types it resolves into the default assembly context rather than its own. This prevents duplicate type definitions.

As a side effect, behavior may differ slightly between running BTCPay Server normally and running tests, but this should be acceptable in most cases.

Relevant discussion: #6851

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
AI review queuedFix flacky CanUseFormsby Nicolas Dorier · 4e34a185 · Nov 21, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix flacky CanUseForms

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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, not a security issue. The test previously checked the entire web page content for an email address, which could fail if the email appeared anywhere else on the page or if timing caused the page content to be incomplete. The change narrows the check to look specifically at the value of the email input field. There is no indication this affects real users or production code.

Lower-priorityAdd a 'Pending invoice' pill in portal subscription when invoice processingby Nicolas Dorier · 2f8be8c9 · Nov 19, 2025 · 5 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add a 'Pending invoice' pill in portal subscription when invoice processing

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAdd buyerEmail to invoice metadata created by suscribersby Nicolas Dorier · 0e649a68 · Nov 19, 2025 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Add buyerEmail to invoice metadata created by suscribers

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedImprove testby Nicolas Dorier · 6b76af43 · Nov 18, 2025 · 6 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Improve test

28/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! 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 is a routine test and code-quality improvement. It tightens a test helper that was incorrectly always setting IsAdmin to true, modernizes some C# syntax, removes unused imports, and adds test-id attributes to a web page so automated tests can locate elements more reliably. There is no security-relevant change to production behavior.

Lower-priorityFix: SVG icons stop displaying when served from cache (#7003)by Nicolas Dorier · c97ddd16 · Nov 18, 2025 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · Nicolas Dorier

Fix: SVG icons stop displaying when served from cache (#7003)

See #7003

The fix seems to be to just reinsert the svg into the page once it is
loaded. This is probably a browser bug...

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 queuedRemove LocalBTCPayClientby Nicolas Dorier · ccbc0614 · Nov 18, 2025 · 4 filesMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Remove LocalBTCPayClient

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 removes an internal-only API client called LocalBTCPayClient. It was a convenience wrapper that let server code call BTCPay Server's own Greenfield API without making real HTTP requests. There is no indication this change fixes a security vulnerability; it appears to be a code cleanup or architectural simplification.

Lower-priorityValidate scopes of service injections in testsby Nicolas Dorier · 749c7722 · Nov 15, 2025 · 11 filesMessage 55 · ThinTriage 8Details
Commit message · Nicolas Dorier

Validate scopes of service injections in tests

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
defensive validation
Lower-priorityFix: Spurious EF error on CallbackGeneratorby Nicolas Dorier · c9dcd4f0 · Nov 14, 2025 · 10 filesMessage 57 · ThinTriage 0Details
Commit message · Nicolas Dorier

Fix: Spurious EF error on CallbackGenerator

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidateFeature: Plugin can extend whether an account can login or notby Nicolas Dorier · 41f55882 · Nov 14, 2025 · 13 filesMessage 50 · ThinLow 37Details
Commit message · Nicolas Dorier

Feature: Plugin can extend whether an account can login or not

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 37/100

This commit refactors how BTCPay Server decides whether a user is allowed to log in. It replaces a simple built-in check with a new extensible system where plugins can add their own login-blocking rules. The change touches password logins, two-factor/FIDO2/LNURL logins, API key authentication, and basic HTTP authentication. It also fixes a small bug in basic authentication where the password was checked before the user was validated. There is no claim in the commit that this fixes a known security vulnerability, and no CVE or advisory is referenced.

Lower-priorityFix CI: Unsupported repository version 1. Only versions up to 0 are supported.by Nicolas Dorier · a914d798 · Nov 14, 2025 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier

Fix CI: Unsupported repository version 1. Only versions up to 0 are supported.

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedFix node menu link styleby Nicolas Dorier · 2926dc40 · Nov 14, 2025 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix node menu link style

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

This is a one-line user-interface styling fix in the main navigation menu. It adds a missing layout attribute so a menu link is styled consistently with other navigation items. There is no security relevance.

Lower-priorityrefactor : addressed requested changesby Abhijay007 · cc0570f0 · Nov 13, 2025 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Abhijay007

refactor : addressed requested changes

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

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Lower-priorityrefactor : addressed requested changesby Abhijay007 · 1bbb9508 · Nov 13, 2025 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Abhijay007

refactor : addressed requested changes

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

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Lower-priorityrefactor: updated testby Abhijay007 · f26f42ba · Nov 13, 2025 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Abhijay007

refactor: updated test

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

65/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification