LWS
← All projectsMonero LWS

Monero LWS

Light-wallet server indexing Monero chain data for remote wallet clients.

Indexing infrastructureMoneroPrivacy protocolsNormal
Repository coverage

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

13security candidates29second-pass queue42AI analyses
13commits · 30 days
30commits · 60 days
64commits · 180 days
111commits · 365 days
Backfill bands
Sep 27 → Mar 3144 seen3 candidatesComplete
Mar 31 → Jul 2932 seen4 candidatesComplete
Jul 29 → Aug 2812 seen2 candidatesComplete
Aug 28 → Sep 276 seen0 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
8Strong · 80–100
12Adequate · 60–79
87Thin · 40–59
17Opaque · 0–39
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Lee *!* Clagett95934149
Evgeny624061
DHIVAKAR R812086
everoddandeven411060
Lee Clagett601045
jpk68300057
Paul V Puey100076
William Swanson100066
Analysis record

Published AI watches

Last scanned 48 minutes ago

Moderate 57 AI analysisMessage 70 · Adequate
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

fix: self-deadlock in subaddress lookahead on mmap resize (#316)

This patch fixes a self-deadlock bug in Monero LWS, a lightweight wallet server. When the server tried to expand the number of subaddresses it watches ahead of time, it could lock itself because one part of the code held a shared lock whil…

Self-deadlock in synchronization primitive (reader shared vs resize exclusive)Denial-of-service vector: wallet/server thread can hang on subaddress lookaheadFix pattern: release shared lock before operation that may acquire exclusive lock
4b98478dby everoddandeven+7−31 file
No security note in commit
Moderate 50 AI analysisMessage 68 · Adequate
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Find subaddress payments in mempool scan (#305)

This commit fixes a bug in the Monero Light Wallet Server (LWS) where payments sent to subaddresses were not being detected when scanning the mempool (the pool of pending transactions). Before the fix, users would not see incoming subaddre…

Functional bug in transaction scanning causing missed subaddress payments in mempoolIncorrect cache invalidation when subaddress set changesNull/empty storage reader hardening added
122ca986by Evgeny+242−258 files
No security note in commit
Moderate 64 AI analysisMessage 86 · Strong
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Decrypt encrypted payment ids per account (#309)

This fix corrects a bookkeeping bug in Monero's lightweight wallet server. When two accounts on the same server sent money to each other, the server could store the wrong payment ID for the receiver. It also accidentally put decrypted paym…

Incorrect cryptographic result reused across accountsPayment ID cross-contamination between sender and receiver outputsSensitive decrypted value stored in wrong database record type
de5bb10fby DHIVAKAR R+223−53 files
Vendor flagged security relevance
Informational 19 AI analysisMessage 70 · Adequate
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

feat: add received outputs to /get_address_txs (#304)

This commit adds an optional feature to the Monero Light Wallet Server's /get_address_txs endpoint. When a wallet explicitly asks for it by setting 'receives': true, the server will include details about incoming (received) transaction out…

New optional RPC field exposes additional wallet data (received outputs) only when explicitly requested and authenticatedRefactoring reuses existing RingCT decryption logic; no new cryptographic primitives introducedDefault behavior unchanged: 'receives' defaults to false, preserving prior response shape
bd3916cfby Evgeny+365−295 files
No security note in commit
Informational 15 AI analysisMessage 76 · Adequate
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Fix builds with assertions enabled (#307)

This commit fixes two assertion-related bugs that only appear when the software is compiled with assertions enabled. One fixes a stale variable name in a sanity check, and the other removes an incorrect size comparison that would falsely t…

2e374648by DHIVAKAR R+1−22 files
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Update expat to 1.9.0

This commit simply updates the version of the expat XML parsing library used when building a Docker image from version 2.8.4 to version 2.9.0. It changes only download URLs and checksums in the Dockerfile. There is no information in the co…

a2e2554cby Lee Clagett+5−51 file
No security note in commit
Low 36 AI analysisMessage 59 · Thin
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Submit raw tx (#300)

This commit changes the /submit_raw_tx endpoint so that callers now receive clearer HTTP status codes and error reasons when the Monero daemon rejects or fails to relay a transaction. It also fixes a bug where the local mempool was incorre…

Behavioral change in error handling for transaction submission endpointLocal mempool no longer updated when daemon reports relayed=falseHTTP status codes now distinguish client errors (400), daemon rejection (422), and accepted-but-not-relayed (200)
18770abeby Evgeny+119−276 files
No security note in commit
High 71 AI analysisMessage 81 · Strong
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Fixes for issues reported by llm (#297)

This commit fixes nine separate bugs in the Monero Light Wallet Server (LWS). The most serious ones are: an infinite loop when importing certain address data, a missing size limit that let unauthenticated remote clients request huge amount…

Infinite loop in database import path (DoS)Missing authentication-time message size limit on remote scanner protocol (memory exhaustion / DoS)Untrusted array reads from client in light wallet RPC
81451fb2by Lee *!* Clagett+62−129 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 28 · Opaque
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Fix docker build:

This commit fixes a broken GitHub Actions workflow file that builds and publishes Docker images. It corrects a variable name (from 'platform' to 'arch') and adds a missing period at the end of the docker build command. There is no security…

10118fbdby Lee *!* Clagett+3−31 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Fix docker action file

This commit fixes a YAML indentation error in a GitHub Actions workflow file. It changes one line of spacing so the Docker login step is correctly aligned under the job's steps list. There is no security-relevant change to the software its…

bff4b1b4by Lee *!* Clagett+1−11 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Fix docker build command

This commit fixes a typo in a GitHub Actions workflow file. The Docker build command had an extra word ('build build') that would cause the automated Docker image build to fail. It is a routine CI/CD fix with no security relevance.

e5d4b3a7by Lee *!* Clagett+1−11 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Fix docker build matrix

This commit fixes a GitHub Actions workflow syntax error. The 'matrix' keyword was missing its required parent 'strategy' wrapper, which would prevent Docker build jobs from running correctly. There is no security relevance in the code cha…

800e026fby Lee *!* Clagett+3−21 file
No security note in commit
Informational 12 AI analysisMessage 70 · Adequate
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Changes required due to upstream monero changes (#290)

This commit is a routine compatibility update to keep the Monero Light Wallet Server (LWS) project building against recent changes in the upstream Monero codebase. It replaces a custom macro-based type declaration (POD_CLASS) with plain C+…

No security-relevant behavioral changes in the diffChanges are limited to forward-declaration style and missing header includesNo memory safety, cryptographic, input validation, or authorization changes observed
fee43d23by Lee *!* Clagett+6−55 files
No security note in commit
Low 32 AI analysisMessage 58 · Thin
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Fix LMDB (wrong) context cast, and remove now unnecessary LMDB code (#287)

This commit fixes a type-casting mistake in the Monero Light Wallet Server's database code. The program was treating its own custom database context as a different, more generic context. That mismatch could corrupt internal accounting of a…

Wrong context cast in LMDB transaction cleanup (type confusion)Custom context reference counting could be corrupted by mismatched deleterLarge code removal reduces attack surface and eliminates duplicated LMDB wrappers
eef10334by Lee *!* Clagett+155−6839 files
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Fix docker conditional

This commit fixes a simple syntax typo in a GitHub Actions workflow file. The condition that decides whether to add release tags had an extra closing brace, which would cause the workflow to fail parsing rather than run incorrectly. There …

cbf6f328by Lee *!* Clagett+1−11 file
No security note in commit
Informational 15 AI analysisMessage 18 · Opaque
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Latest master

This commit only updates the 'external/monero' git submodule pointer from one commit hash to another. No actual source code changes are shown in this repository's diff. The title and message are generic ('Latest master') and give no indica…

248e9148by Lee *!* Clagett+1−11 file
No security note in commit
Low 35 AI analysisMessage 58 · Thin
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Fix mempool webhook read during subaddress scanning (#283)

This commit fixes a bug in the Monero Light Wallet Server (LWS) where webhook notifications for mempool transactions could fail or behave incorrectly when scanning subaddresses. The change passes an existing database reader into the output…

Fixes a read-transaction lifecycle issue in webhook lookup during mempool scanningAdds regression test covering mempool publication + webhook deliveryCallback signature change propagates an existing storage_reader to avoid nested/duplicate reads
89e90f58by Lee *!* Clagett+354−136 files
No security note in commit
Informational 15 AI analysisMessage 53 · Thin
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Add/update newest GPG signing key (#282)

This commit simply adds a new GPG public key file to the repository. A GPG public key is used to verify that future releases or commits were genuinely signed by the project maintainer. There is no code change, no vulnerability, and no secu…

5b64b31eby Lee *!* Clagett+22−01 file
No security note in commit
Informational 11 AI analysisMessage 45 · Thin
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Another attempt at fixing external/monero pin

This commit is a routine build/maintenance change that adjusts which version of the external Monero dependency is pinned. There is no indication of any security fix, vulnerability, or user-facing behavior change. It is essentially a housek…

1e48ef2bby Lee *!* Clagett+1−11 file
No security note in commit
Informational 4 AI analysisMessage 45 · Thin
LWS Monero LWSMonero LWS Indexing infrastructureMoneroPrivacy protocols

Fix external/master pin back to master

This commit appears to change which version of an external Monero component the project points to (a so-called 'git submodule pin' or dependency reference). The title says it fixes the pin for 'external/master' back to the 'master' branch.…

d7f8ef46by Lee *!* Clagett+1−11 file
No security note in commit
Repository ledger

Explore captured commits

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

Security candidatefix: self-deadlock in subaddress lookahead on mmap resize (#316)by everoddandeven · 4b98478d · Oct 31, 2026 · 1 fileMessage 70 · AdequateModerate 57Details
Commit message · everoddandeven

fix: self-deadlock in subaddress lookahead on mmap resize (#316)

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
privacy or spend-authorization protocol
AI analysis · Moderate 57/100

This patch fixes a self-deadlock bug in Monero LWS, a lightweight wallet server. When the server tried to expand the number of subaddresses it watches ahead of time, it could lock itself because one part of the code held a shared lock while another part needed an exclusive lock on the same resource. The fix releases the shared lock before calling the function that may need the exclusive lock, then reacquires it afterward. A deadlock would freeze server operations rather than let an attacker steal funds directly, but it could be triggered by normal wallet activity.

Security candidateFind subaddress payments in mempool scan (#305)by Evgeny · 122ca986 · Oct 30, 2026 · 8 filesMessage 68 · AdequateModerate 50Details
Commit message · Evgeny

Find subaddress payments in mempool scan (#305)

* fix: find subaddress payments in mempool scan
* fix: empty storage, null reader check

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
privacy or spend-authorization protocolsigning or wallet path
AI analysis · Moderate 50/100

This commit fixes a bug in the Monero Light Wallet Server (LWS) where payments sent to subaddresses were not being detected when scanning the mempool (the pool of pending transactions). Before the fix, users would not see incoming subaddress payments until they were confirmed in a block. The patch also adds safety checks for empty database storage and null readers to prevent crashes.

Security candidateDecrypt encrypted payment ids per account (#309)by DHIVAKAR R · de5bb10f · Oct 30, 2026 · 3 filesMessage 86 · StrongModerate 64Details
Commit message · DHIVAKAR R

Decrypt encrypted payment ids per account (#309)

* Decrypt encrypted payment ids per account

ownership_test decrypted a short payment id once per transaction, with
the derivation of the first matching account, and then stored that value
for every account in the transaction. When the sender and the receiver
are both registered, which account comes first decides the receiver's
payment id: if the sender's change output is scanned first, the receiver
gets the sender's (meaningless) decryption. construct_tx adds a dummy
encrypted payment id to most two-output transactions, so this affects
most transfers between accounts on the same server, and tx-confirmation
webhooks filtered on a payment id can miss the payment.

The decrypted value also leaked into spend records of later accounts,
which should only carry unencrypted payment ids.

Each account now starts from the unencrypted payment id and decrypts its
own copy.

Fixes #279

* Move ownership_test unit test to tests/unit/util

The util test library becomes an OBJECT library, like the db one, so
the test case in it is linked into monero-lws-unit.

86/100 · StrongMessage clarity
✓ 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
signing boundaryprivacy or spend-authorization protocol
AI analysis · Moderate 64/100

This fix corrects a bookkeeping bug in Monero's lightweight wallet server. When two accounts on the same server sent money to each other, the server could store the wrong payment ID for the receiver. It also accidentally put decrypted payment IDs into spend records where they did not belong. The patch makes each account decrypt its own payment ID independently, so the right value is recorded every time.

AI review queuedfeat: add received outputs to /get_address_txs (#304)by Evgeny · bd3916cf · Oct 29, 2026 · 5 filesMessage 70 · AdequateInformational 19Details
Commit message · Evgeny

feat: add received outputs to /get_address_txs (#304)

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit adds an optional feature to the Monero Light Wallet Server's /get_address_txs endpoint. When a wallet explicitly asks for it by setting 'receives': true, the server will include details about incoming (received) transaction outputs in the response. The feature is off by default and requires the same view-key authentication already used by the endpoint. The change refactors existing code to reuse the RingCT decoding logic rather than duplicating it.

AI review queuedFix builds with assertions enabled (#307)by DHIVAKAR R · 2e374648 · Oct 29, 2026 · 2 filesMessage 76 · AdequateInformational 15Details
Commit message · DHIVAKAR R

Fix builds with assertions enabled (#307)

* Fix compilation of builds with assertions enabled

check_loop() asserted on lws_server_addr, which no longer exists after
a7aea46. The remote scanner address is lws_server.address.

Fixes #302

* Remove element-count assert in vec_lmdb_::get_value()

end - pos counts remaining vector elements, but the assert compared it
with a byte size, so it fired whenever fewer than sizeof(G) + uoffset
elements were left (e.g. /feed updates with two outputs). The
static_assert above already keeps the field inside one element, and
assert(!is_end()) covers the iterator.

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ 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 two assertion-related bugs that only appear when the software is compiled with assertions enabled. One fixes a stale variable name in a sanity check, and the other removes an incorrect size comparison that would falsely trigger during normal operation. Neither change addresses a security vulnerability; they are build/compile fixes and removal of a buggy debug check.

AI review queuedUpdate expat to 1.9.0by Lee Clagett · a2e2554c · Oct 12, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Lee Clagett

Update expat to 1.9.0

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 commit simply updates the version of the expat XML parsing library used when building a Docker image from version 2.8.4 to version 2.9.0. It changes only download URLs and checksums in the Dockerfile. There is no information in the commit itself saying this fixes a security problem, and no independent references were provided.

AI review queuedSubmit raw tx (#300)by Evgeny · 18770abe · Oct 9, 2026 · 6 filesMessage 59 · ThinLow 36Details
Commit message · Evgeny

Submit raw tx (#300)

* feat: return daemon reject reason from /submit_raw_tx
* feat: use 4xx codes for /submit_raw_tx errors
* chore: rename copyable_slice to http_response

59/100 · ThinMessage clarity
✓ Subject identifies a change✓ 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 · Low 36/100

This commit changes the /submit_raw_tx endpoint so that callers now receive clearer HTTP status codes and error reasons when the Monero daemon rejects or fails to relay a transaction. It also fixes a bug where the local mempool was incorrectly updated even when the daemon did not actually relay the transaction. The change improves API correctness and reduces confusion, but it does not appear to fix a critical security vulnerability.

Security candidateFixes for issues reported by llm (#297)by Lee *!* Clagett · 81451fb2 · Sep 30, 2026 · 9 filesMessage 81 · StrongHigh 71Details
Commit message · Lee *!* Clagett

Fixes for issues reported by llm (#297)

* Fix infinite loop when importing lookahead address with {0,0} output
* Fix zero threads on client
* Restrict remote scanner client message sizes until authentication
* Fix untrusted array (users, blocks) reads from client
* Fix overflow check
* Harden gamma picker
* Add check for relayed flag before adding to mempool list
* Fix double response on tx parse error
* Fix erase call in remote scanning round-robin algo
* Fix mempool metadata in pessimistic state

81/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controlmemory safetydefensive validationsigning or wallet path
AI analysis · High 71/100

This commit fixes nine separate bugs in the Monero Light Wallet Server (LWS). The most serious ones are: an infinite loop when importing certain address data, a missing size limit that let unauthenticated remote clients request huge amounts of memory, reading untrusted array data from clients before proper validation, an incorrect overflow check when calculating subaddress counts, and a double HTTP response that could confuse clients. Several other fixes correct thread handling, mempool behavior, and a round-robin scheduling erase bug. The commit title says these issues were 'reported by llm'—likely an automated or large-language-model-assisted review—so the security relevance is acknowledged by the project author but not via a formal vendor security advisory.

AI review queuedFix docker build:by Lee *!* Clagett · 10118fbd · Sep 30, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Lee *!* Clagett

Fix docker build:

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

This commit fixes a broken GitHub Actions workflow file that builds and publishes Docker images. It corrects a variable name (from 'platform' to 'arch') and adds a missing period at the end of the docker build command. There is no security issue here—just a routine build script repair.

AI review queuedFix docker action fileby Lee *!* Clagett · bff4b1b4 · Sep 30, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Lee *!* Clagett

Fix docker action file

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

This commit fixes a YAML indentation error in a GitHub Actions workflow file. It changes one line of spacing so the Docker login step is correctly aligned under the job's steps list. There is no security-relevant change to the software itself.

AI review queuedFix docker build commandby Lee *!* Clagett · e5d4b3a7 · Sep 30, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Lee *!* Clagett

Fix docker build command

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

This commit fixes a typo in a GitHub Actions workflow file. The Docker build command had an extra word ('build build') that would cause the automated Docker image build to fail. It is a routine CI/CD fix with no security relevance.

AI review queuedFix docker build matrixby Lee *!* Clagett · 800e026f · Sep 30, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Lee *!* Clagett

Fix docker build matrix

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

This commit fixes a GitHub Actions workflow syntax error. The 'matrix' keyword was missing its required parent 'strategy' wrapper, which would prevent Docker build jobs from running correctly. There is no security relevance in the code change itself.

AI review queuedChanges required due to upstream monero changes (#290)by Lee *!* Clagett · fee43d23 · Sep 18, 2026 · 5 filesMessage 70 · AdequateInformational 12Details
Commit message · Lee *!* Clagett

Changes required due to upstream monero changes (#290)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit is a routine compatibility update to keep the Monero Light Wallet Server (LWS) project building against recent changes in the upstream Monero codebase. It replaces a custom macro-based type declaration (POD_CLASS) with plain C++ struct forward declarations and adds a few missing standard library header includes. There is no indication in the commit that any security vulnerability is being fixed.

AI review queuedFix LMDB (wrong) context cast, and remove now unnecessary LMDB code (#287)by Lee *!* Clagett · eef10334 · Aug 26, 2026 · 9 filesMessage 58 · ThinLow 32Details
Commit message · Lee *!* Clagett

Fix LMDB (wrong) context cast, and remove now unnecessary LMDB code (#287)

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 32/100

This commit fixes a type-casting mistake in the Monero Light Wallet Server's database code. The program was treating its own custom database context as a different, more generic context. That mismatch could corrupt internal accounting of active readers/writers or cause the wrong cleanup code to run when a database transaction ends. The patch also removes a lot of now-redundant LMDB wrapper code and switches the project to use its own dedicated transaction and cursor types so the mistake cannot recur in the same way.

AI review queuedFix docker conditionalby Lee *!* Clagett · cbf6f328 · Aug 8, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Lee *!* Clagett

Fix docker conditional

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

This commit fixes a simple syntax typo in a GitHub Actions workflow file. The condition that decides whether to add release tags had an extra closing brace, which would cause the workflow to fail parsing rather than run incorrectly. There is no security issue here.

AI review queuedLatest masterby Lee *!* Clagett · 248e9148 · Aug 8, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Lee *!* Clagett

Latest master

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 updates the 'external/monero' git submodule pointer from one commit hash to another. No actual source code changes are shown in this repository's diff. The title and message are generic ('Latest master') and give no indication of what changed in the submodule. Without inspecting the submodule's own commits, we cannot determine any security relevance from the materials provided.

Security candidateFix mempool webhook read during subaddress scanning (#283)by Lee *!* Clagett · 89e90f58 · Aug 8, 2026 · 6 filesMessage 58 · ThinLow 35Details
Commit message · Lee *!* Clagett

Fix mempool webhook read during subaddress scanning (#283)

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
privacy or spend-authorization protocol
AI analysis · Low 35/100

This commit fixes a bug in the Monero Light Wallet Server (LWS) where webhook notifications for mempool transactions could fail or behave incorrectly when scanning subaddresses. The change passes an existing database reader into the output-handling callback, so the code no longer tries to start a new read transaction inside an already-active one. This prevents potential failures or inconsistent reads during mempool webhook processing. The commit also adds tests that exercise the mempool publication path with a webhook server.

Security candidateAdd/update newest GPG signing key (#282)by Lee *!* Clagett · 5b64b31e · Aug 7, 2026 · 1 fileMessage 53 · ThinInformational 15Details
Commit message · Lee *!* Clagett

Add/update newest GPG signing key (#282)

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
signing boundary
AI analysis · Informational 15/100

This commit simply adds a new GPG public key file to the repository. A GPG public key is used to verify that future releases or commits were genuinely signed by the project maintainer. There is no code change, no vulnerability, and no security issue in the diff itself.

Security candidateAnother attempt at fixing external/monero pinby Lee *!* Clagett · 1e48ef2b · Jul 16, 2026 · 1 fileMessage 45 · ThinInformational 11Details
Commit message · Lee *!* Clagett

Another attempt at fixing external/monero pin

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 11/100

This commit is a routine build/maintenance change that adjusts which version of the external Monero dependency is pinned. There is no indication of any security fix, vulnerability, or user-facing behavior change. It is essentially a housekeeping update to a submodule reference.

Security candidateFix external/master pin back to masterby Lee *!* Clagett · d7f8ef46 · Jul 16, 2026 · 1 fileMessage 45 · ThinInformational 4Details
Commit message · Lee *!* Clagett

Fix external/master pin back to master

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 4/100

This commit appears to change which version of an external Monero component the project points to (a so-called 'git submodule pin' or dependency reference). The title says it fixes the pin for 'external/master' back to the 'master' branch. No actual code changes are visible, and no security-related information is provided in the commit message or materials.

Security candidateFix `MDB_BAD_RSLOT` in `subaddress_reader::update_reader()` causing permanently missed subaddress outputs (#278)by Evgeny · 38b336e2 · Jul 16, 2026 · 3 filesMessage 58 · ThinModerate 56Details
Commit message · Evgeny

Fix `MDB_BAD_RSLOT` in `subaddress_reader::update_reader()` causing permanently missed subaddress outputs (#278)

* fix: regtest
* fix: MDB_BAD_RSLOT

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
privacy or spend-authorization protocol
AI analysis · Moderate 56/100

This commit fixes a database-handling bug in Monero Light Wallet Server (LWS). The bug caused the server to permanently miss some subaddress outputs because a read transaction was not closed before a new one was opened, triggering an LMDB error (MDB_BAD_RSLOT). The fix explicitly releases the old read transaction before starting the next one. There is no direct evidence this is exploitable by an attacker; it appears to be a reliability/correctness bug.

Security candidateFix integer overflow check in subaddress handling (#264)by Lee *!* Clagett · 33c56770 · Jul 3, 2026 · 2 filesMessage 63 · AdequateModerate 59Details
Commit message · Lee *!* Clagett

Fix integer overflow check in subaddress handling (#264)

63/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
memory safetyprivacy or spend-authorization protocol
AI analysis · Moderate 59/100

This commit fixes a math mistake when checking whether a user requested too many Monero subaddresses. The original code divided two numbers and compared the result to a maximum, which is the wrong way to detect overflow and could allow the multiplication to overflow. The fix reverses the division so the check works correctly. A malicious or malformed request might have been able to bypass the subaddress limit, though the practical effect depends on what happens after the check.

AI review queuedBump branch to 1.1-alphaby Lee *!* Clagett · fb599e8a · May 23, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Lee *!* Clagett

Bump branch to 1.1-alpha

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 commit simply changes a version string from '1.0-alpha' to '1.1-alpha' in a single source file. There is no functional code change, no bug fix, and no security relevance visible in the diff or commit message.

AI review queuedBump mkdocs to regenerateby Lee *!* Clagett · 322f5827 · May 23, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Lee *!* Clagett

Bump mkdocs to regenerate

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

This commit changes one character in the documentation configuration file (mkdocs.yml), adding a trailing slash to the site description. It does not touch any program code, cryptographic logic, network handling, or user data. There is no security relevance.

AI review queuedAnother publish attemptby Lee *!* Clagett · d86d25a7 · May 23, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Lee *!* Clagett

Another publish attempt

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 is a routine documentation-site fix. It changes how the MkDocs documentation builder is invoked in a GitHub Actions workflow (from `python3 mkdocs build` to `python3 -m mkdocs build`) and fixes a typo in the site description. There is no security relevance.