CommitWatch RSS
T
← Developer activityStrong match

thgO.O

Public commit activity attributed with strong match confidence. This page describes observable work, not personal trustworthiness.

@thgO-O on GitHub ↗
8 commits1 monitored projects4 candidates0 high-risk analyses
Project constellation

Where the commits appear

Amber nodes are monitored by CommitWatch. Gray nodes are sampled from authenticated GitHub public commit search and may not represent complete contribution history.

Monitored External sample
Projects connected to thgO.OA visual map of monitored and externally discovered repositories.Tdeveloper8BTCPay Server
Monitored evidence

CommitWatch projects

BTCPay ServerBTCPay Server8 commits4 candidates0 high risk
External discovery

Other public projects

No external sample loaded yet.

Authenticated GitHub discovery can enrich this profile.
Analyzed activity

Recent published watches

Message quality and risk characterize commits, never the person.

Low 38 AI analysisMessage 70 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

feat: embed plugin directory in plugin management (#7381)

This commit refactors BTCPay Server's plugin management into a dedicated plugin and adds an embedded plugin directory that loads content from an external plugin catalog via an iframe. The change moves plugin URLs from the server settings a…

New SafeExternalUrl helper filters plugin metadata URLs to http/https absolute URIs only, mitigating javascript: and relative-link injection in author/documentation fieldsDownloadRemotePlugin now validates that the downloaded manifest identifier matches the requested plugin identifierPlugin directory is rendered via iframe to an external, configurable plugin source, increasing attack surface if the source is compromised or MITM'd
5da26940by thgO.O+3018−169229 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 65 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

feat: Add multisig wallet setup (#7218)

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…

e48a8438by thgO.O+3659−17356 files
No security note in commit
Open full analysis →Source commit ↗
Low 40 AI analysisMessage 81 · Strong
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Add granular API permissions for on-chain wallets (#7357)

This commit introduces more fine-grained permission checks for BTCPay Server's on-chain wallet API. Previously, many wallet operations required broad 'modify store settings' or 'view store settings' permissions. Now, operations are gated b…

Authorization policy tightening from broad store policies to wallet-specific policiesNew explicit permission checks in transaction creation endpointPayjoin PSBT handling bugfix: clone before finalize to keep Payjoin PSBT unfinalized until after request
4a03202aby thgO.O+122−495 files
No security note in commit
Open full analysis →Source commit ↗
Low 45 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Add granular wallet permissions and move wallet to plugin (#7329)

This is a large refactoring commit that splits BTCPay Server's wallet functionality into a separate plugin and introduces finer-grained wallet permissions (view, create transactions, sign, broadcast, manage settings, etc.). It also adds ne…

Introduction of granular wallet permissions and role-based access controlRelocation of wallet controllers into a plugin area with updated authorization attributesNew tests assert that wallet-only users cannot access invoices, reports, payment requests, pull payments, payouts, or another store's wallet settings
1e1d2514by thgO.O+8429−729970 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 91 · Strong
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix reserved addresses after wallet replacement (#7304)

This commit fixes a bug where BTCPay Server's 'reserved addresses' list could show addresses from a previously replaced wallet. After a user swaps one wallet for another, the old reserved addresses are now filtered out by checking which ad…

Information disclosure: reserved addresses from a replaced wallet could remain visible to the store owner or users with wallet accessAddress/wallet confusion: UI displayed addresses not controlled by the currently configured walletMissing authorization boundary between wallet derivations sharing the same WalletId
dd5dcf19by thgO.O+142−02 files
No security note in commit
Open full analysis →Source commit ↗
Low 29 AI analysisMessage 91 · Strong
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

[Feature] Store-scoped labels + linkedType-scoped LabelManager suggestions (#7050)

This commit refactors how BTCPay Server stores labels for payment requests, moving them from a wallet-based graph system into new store-scoped database tables. It also adds a new API endpoint for updating store-scoped labels. The changes a…

New POST endpoint /stores/{storeId}/update-labels is protected with [Authorize(Policy = Policies.CanModifyStoreSettings)] and [ValidateAntiForgeryToken]Client-side JS extracts and sends the anti-forgery token in the RequestVerificationToken header for label updatesStore-scoped label endpoints verify CurrentStore exists and matches the route storeId before acting
689b9d17by thgO.O+1155−16625 files
No security note in commit
Open full analysis →Source commit ↗
Wrong identity?Names can collide and public author strings can be misleading.Contact commitwatch@karma-x.io →