BTCPay Server

This commit updates the .NET runtime and SDK versions used to build and run BTCPay Server. It is a routine dependency bump, likely to pick up bug fixes and security patches released by Microsoft. The commit itself does not describe any specific vulnerability or attack, but running older .NET versions can expose software to known security flaws.

This commit updates several third-party software libraries (dependencies) used by BTCPay Server to newer patch versions. It also adds a few new user-interface translation strings and records a bug fix in the changelog. The dependency bumps are routine maintenance that may include undisclosed security fixes from upstream vendors, but the commit itself does not describe any specific vulnerability or attack.

This commit only updates the project's changelog file, adding one line describing a UI fix for an invoice date filter widget. There is no code change and no security relevance in the diff itself.

This commit only updates the project's changelog file, adding a single line describing a user-interface improvement (inline QR code and copy button for a Store ID). There is no code change, no security fix, and no functional change to the software.

This commit only updates translation strings in a single C# resource file. It adds, removes, and rewords user-facing text labels (for example, changing '2FA' wording to 'Authenticator', adding labels for new passkey and multisig wallet features, and removing unused strings). There are no code logic changes, no security fixes, and no behavior changes.

This commit adds a single line to a test file to wait for the web page to finish loading before checking its content. It is a test reliability fix, not a security fix, and does not change any production code.

This is a one-line change in a test file that updates the name of a database migration being tested. It fixes a broken build caused by a renamed migration and has no security relevance.

This commit adds a new multisignature wallet setup feature to BTCPay Server. It introduces new database tables, UI flows, controllers, services, and tests for creating and managing multisig wallets. The changes are a feature implementation, not a security fix or vulnerability patch. There is no indication in the commit or supplied references that this addresses a security issue.

This commit swaps a regular dictionary for a thread-safe concurrent dictionary when caching store data attached to a web request. The stated goal is to prevent rare, random server crashes caused by multiple threads accessing the cache at the same time. It is a hardening fix rather than a clear-cut exploitable vulnerability, and the commit message does not frame it as a security issue.

This commit updates the project's test framework from xUnit version 2 to xUnit version 3. It only changes test code, package references, and compiler warning suppressions. There is no change to the production application that users interact with, and no security issue is introduced or fixed.

This commit adds new search and filter features to the wallet transaction list in BTCPay Server. Users can now filter transactions by text, direction (incoming/outgoing), labels, and date ranges, and export results matching those filters. The change is a feature addition with a large amount of new code, but the diff itself does not show an obvious security vulnerability. There are a few minor hardening touches, such as adding a missing null check for an unknown cryptocurrency code and removing a redundant anti-forgery attribute.

This commit only updates the API documentation file (a Swagger/OpenAPI template) to add a description for a newly documented setting called 'storeQuota'. It does not change any server code, permissions, or behavior. There is no security issue in this change.

This commit fixes a visual layout bug in an HTML table on the 'Enter your xpub' screen. The table had incorrect row span numbers, which made the table display incorrectly. There is no security issue here.

This commit adds a new global search bar and reorganizes the top navigation in BTCPay Server. Most of the change is user-interface code (menus, CSS, JavaScript, tests). There is one small security-relevant detail: the new search endpoint returns a list of internal URLs and checks whether the current user is authorized for each one, but it also accepts an arbitrary storeId parameter and queries the store with the current user's permissions. The commit does not describe itself as a security fix, and no vulnerability is clearly demonstrated in the diff.

This commit simply moves three helper methods that generate wallet-related URLs from a general file into a new file inside the Wallets plugin folder. There is no change to what the code does, no bug fix, and no security-related change.

This commit removes nullable markers ('?') from some string parameters and adds explicit controller names to two URL helper methods. It is titled 'fix warnings' and appears to be a routine compiler-warning cleanup. There is no direct evidence in the commit that these changes fix a security vulnerability.

This commit removes the old Shopify integration from BTCPay Server entirely. It deletes all Shopify-related code, settings pages, API clients, and rate-limiting rules. There is no security patch here—this is a feature removal because Shopify deprecated the underlying technology.

This commit changes how the wallet transactions page reads its paging settings (skip/count). Instead of taking them directly from the URL, it routes them through a shared helper called ParseListQuery that also reads and saves user preferences in a cookie. The change is a code-quality fix to make paging behave consistently with other pages. There is no direct evidence in the commit that this fixes an active security vulnerability, but it removes a place where paging parameters were handled differently from the rest of the application.

This commit simply moves three Greenfield API wallet controller files from one folder to another inside the BTCPay Server codebase and updates their class constructors to use C# primary constructors. The code logic, authorization checks, route URLs, and security behavior appear unchanged. It is a refactoring/organizational change, not a security fix or feature change.

This commit refactors authorization checks in two wallet-related controller actions. In one case, the 'clear' command previously required both server-admin role AND store-level wallet-settings permission; now it only requires a server-level policy. In another case, a new switch statement replaces nested if-checks but appears functionally equivalent. The change could be a security fix if the old combined check was overly restrictive, or a security weakening if the new single policy is less protective than the old two-factor check. Without vendor context, the security relevance is uncertain.

This commit is a routine code cleanup that converts three C# controller classes from traditional constructor syntax to a newer, shorter primary-constructor syntax. It does not change what the code does, what data it accepts, who can access it, or how it protects wallet operations. There is no visible security fix or behavior change.

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

This commit only updates the changelog file to add release notes for version 2.3.9. It does not change any source code, configuration, or executable files. There is no security-relevant change in the diff itself.

This commit fixes a bug where BTCPay Server would not properly recover after a plugin crashed. The server tries to identify which plugin caused an exception by looking at the stack trace. The old code only checked the main assembly name and did not look inside nested/inner exceptions, so it sometimes failed to find the culprit plugin. The fix makes the search walk through inner exceptions and also maps all assemblies loaded by each plugin, not just the plugin's primary assembly. A second small fix prevents malformed plugin commands from crashing the command parser.

This commit changes several BTCPay Server API endpoints so that callers no longer need to supply a store ID when working with existing invoices, payment requests, and pull payments. The server now looks up the store automatically from the invoice/payment-request/pull-payment record. The old store-scoped routes are kept alongside the new shorter routes. The change is described as a convenience/cleanup fix, not as a security patch, and the diff does not show any new authorization checks being added.