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.
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
22Strong · 80–100
158Adequate · 60–79
690Thin · 40–59
66Opaque · 0–39
14security candidates with opaque commit messaging
This commit only adds a new automated test tool (a fuzzer) for the Monero wallet. It does not change any production wallet, node, or consensus code. It cannot by itself introduce a vulnerability that affects real users, nor does it fix one…
This is a cleanup and refactoring patch for Monero's new FCMP++ (full-chain membership proof) database and transaction handling code. It renames a method, fixes typos and comments, tightens a constant name, adds a safety check that outputs…
Added runtime invariant check that locked outputs do not unlock below the default unlock blockRefactored transparent-amount commitment collection to reduce indirection and potential misuseClarified unlock-time semantics and coinbase detection in migration code
This commit is a cleanup and hardening patch following an earlier pull request. It adds a safety check to make sure outputs are not incorrectly treated as spendable before they should be, fixes several typos and variable-name issues, rewri…
Added invariant check that outputs unlock no earlier than the default unlock block before adding locked outputs to the databaseRefactored transparent-amount commitment collection to remove std::reference_wrapper indirection, reducing complexityCorrected constant-name typos in spendable-age calculations
This is a one-line fix in Monero's wallet software that adjusts how far ahead the wallet tries to 'skip' scanning after a blockchain reorganization (reorg). A reorg happens when the network briefly disagrees on the chain of blocks and then…
Incorrect scan resume height after blockchain reorgPotential missed transaction detectionBalance accuracy issue in wallet
This commit is a code cleanup that replaces the non-standard WIN32 preprocessor macro with the compiler-defined _WIN32 macro across 18 files. It does not change program logic or behavior; it only makes Windows-specific code detection more …
No functional code changes observedPreprocessor macro standardization onlyWindows-specific code paths remain identical in behavior
This commit only adds a new automated security test (a fuzzer) for Monero's wallet cache file parser. It does not change any production wallet code, fix a bug, or introduce a vulnerability. It is a testing-only addition intended to help fi…
Adds a fuzz target for wallet cache deserializationNo changes to production code pathsNo patch of a reported vulnerability
This Monero update adds a cache that remembers which transactions in the memory pool have already failed expensive input verification, so the node does not waste CPU re-checking the same bad transaction repeatedly. It is a performance and …
Adds caching of invalid input verification IDs to avoid repeated expensive ring signature verificationReduces CPU consumption for transactions that re-enter or remain in the mempool with unchanged invalid inputsCould mitigate a minor denial-of-service vector where a node repeatedly re-verifies a bad transaction
This patch changes how Monero's daemon calculates the total coinbase transaction sum (emission plus fees) for a range of blocks. Previously, the code called a general 'get_transactions' helper that could trigger a deadlock because it might…
Deadlock avoidance in consensus-related coinbase emission calculationChange from general transaction retrieval to direct, pruned database readAddition of functional test covering coinbase sum correctness
This change is a performance optimization for the Monero wallet's balance-reporting RPC. When a user asks for balances across many subaddresses, the code now pre-counts unspent outputs in one pass instead of re-scanning the entire transact…
This update adds a safety check in the Monero wallet's fast refresh process. Previously, if a malicious or buggy remote server told the wallet to start syncing from a block height beyond the wallet's known blockchain data, the wallet could…
Added bounds check on untrusted server-supplied start_height against local hash chain sizeDefensive hardening at wallet/daemon trust boundaryUnit test demonstrates rejection of out-of-bounds refresh request
This commit tightens filename validation in the Monero wallet's remote-control interface (RPC server). It now rejects wallet names that are just '.' or '..', contain a hidden null character, or contain path separators like '/' (and on Wind…
Path-traversal defense: blocks directory separators and parent-directory references in wallet filenamesNull-byte injection defense: rejects embedded NUL characters that could truncate or confuse downstream path handlingRPC input validation hardening in wallet_rpc_server
This Monero wallet update fixes a file-handling bug in the 'save wallet as' function. Previously, the code compared only the main wallet cache path and used a simple path check that could be fooled by symlinks or filenames ending in '.keys…
Path overlap / self-overwrite protection for wallet cache and keys filesSymlink and hardlink alias detection using boost::filesystem::equivalentRejection of ambiguous paths where .keys file and cache file could collide
This commit adds an optional, faster way to set up N-of-N Monero multisig wallets. Normally, all signers must complete a final verification round to prove they are active and have finished setup. The new 'fast non-interactive setup' skips …
New feature adds a non-default, opt-in fast setup path that intentionally weakens a liveness/verification guaranteeForce-update flag (force_update_use_with_caution) is used internally to bypass the normal post-KEX roundUser-facing and API documentation clearly warn that funds may become inaccessible if other signers do not complete setup
This change refactors how Monero's wallet fetches transaction data when creating or verifying 'spend proofs'—cryptographic receipts that prove you spent funds. Previously, spend-proof code fetched transactions directly from the network dae…
Refactoring of spend-proof transaction lookup to a single helperAddition of explicit RPC timeout parameter to transaction fetch helperImproved daemon RPC error/status reporting in get_tx_for_proof
This commit refactors how the Monero wallet fetches a transaction when verifying a payment proof (the check_tx_key feature). It replaces a direct daemon RPC call with a helper function called get_tx_for_proof, which is described in the com…
Replaces direct /gettransactions RPC with centralized helper for proof verificationCommit title explicitly frames change as 'verify v1 txid in check_tx_key'Removes local tx_hash == txid equality check in favor of helper-internal verification
This change stops a Monero wallet from creating 'InProofs' (receipt proofs) for transactions that the wallet itself sent. InProofs are meant to prove to someone else that you received money. If a wallet could generate an InProof for a tran…
Prevents generation of misleading InProofs for outgoing/self-sent transactionsAdds explicit runtime guard in wallet proof generation pathFunctional tests updated to assert refusal behavior
This patch fixes a bug in the Monero wallet where, if a pending transaction failed, the wallet could incorrectly mark coins as unspent even though they had already been spent by a separate confirmed transaction. This could let the wallet t…
Incorrect state reset on failure pathPotential double-spend attempt caused by stale UTXO selectionWallet balance/availability inconsistency after failed pending tx
This commit only adds a new automated fuzz-testing harness for Monero wallet features. It does not change any production wallet code, fix a bug, or alter network behavior. It is a test-only addition intended to help find bugs in the future…
Adds fuzz targets for payment URI parsing and transaction proof verificationNo changes to production wallet, consensus, or network codeNo bug fix or behavior change in existing source files
This Monero update fixes a bug in how nodes ask each other for blockchain history. Previously, a node could get stuck or drop a peer when it already knew about some blocks from another connection, because it would not ask for the next batc…
P2P protocol synchronization logic changePotential denial-of-service via peer dropping or sync stallNo authentication or cryptographic boundary crossed
This commit fixes a bug in how the Monero wallet saves itself to disk. Previously, the wallet could accidentally overwrite or corrupt its own files when the user chose a path that overlapped with existing wallet files, such as saving to a …
File overwrite / corruption prevention in wallet save path handlingSymlink and hardlink alias detection via filesystem equivalent() checksRejection of overlapping source/destination wallet files
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedepee: use correct minor http versionby jpk68 · 49108d7a · Jun 5, 2026 · 1 fileMessage 45 · ThinLow 29Details
Commit message · jpk68
epee: use correct minor http version
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 29/100
This is a one-line bug fix in Monero's embedded HTTP protocol handler. The code was accidentally passing the major HTTP version number twice to a parsing function, instead of passing both the major and minor version numbers. The fix makes the parser receive the correct minor version number. This is clearly a bug, but from the diff alone it is hard to tell whether it has any practical security consequence.
Defer loading of private view key from device until first time it is needed. Do not fail if this fails. This has two effects:
1. The prompt to export the view key is only needed once when creating a `cryptonote::account_base` 2. The call to `connect()` doesn't fail if the user decies to not export the viewkey, and thus usage of the device without exporting view keys is possible
This is a small convenience for Ledger users, but will be an even larger convenience for Ledger device testing
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
privacy or spend-authorization protocol
AI analysis · Informational 18/100
This change makes Monero's Ledger hardware wallet integration ask for the private view key only when it is first needed, rather than immediately when connecting. If the user refuses, the software no longer fails and can continue in a slower mode where the Ledger does more cryptographic work. The change also clears the cached view key from memory when disconnecting. It is a usability improvement, not a fix for an active security flaw.
Fix: check hwdev.generate_output_ephemeral_keys result
If it fails, out_eph_public_key and view_tag remain uninitialized.
77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 59/100
This commit fixes a bug where Monero's transaction creation code did not check whether a hardware wallet device successfully generated the one-time public key and view tag for a transaction output. If the hardware device call failed, the code would continue using uninitialized cryptographic values, which could lead to creating an invalid or insecure transaction. The fix adds an explicit error check that aborts transaction creation if the key generation fails.
Security candidateRefactored tx verification NIC logicby SChernykh · 196078ea · Jun 4, 2026 · 5 filesMessage 70 · AdequateLow 46Details
Commit message · SChernykh
Refactored tx verification NIC logic
Encapsulated `nic_verified_hf_version` and `txs_by_txid` to make it impossible for callers to skip updating it.
70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
defensive validationcryptography-sensitive pathparser or protocol path
AI analysis · Low 46/100
This commit is a defensive code cleanup in Monero's transaction verification system. It restructures how a temporary list of extra block transactions (the 'pool supplement') is handled so that callers cannot accidentally forget to mark the list as unverified when adding new transactions. Before, outside code directly inserted transactions and separately reset a verification flag, which created a risk that someone could add a transaction without resetting the flag and potentially use a stale 'already verified' status. Now, adding or clearing transactions automatically resets the flag, and only the dedicated verification function can set it to a valid version. There is no direct evidence in the commit of an actual exploit or bug being fixed, but the change removes a fragile pattern that could lead to consensus or security issues.
Blockchain: fix wrong block_weight in handle_get_objects
- When there are missing IDs, blocks.size() != arg.blocks.size(), so arg.blocks can't be indexed by `i` - the indices will be wrong, the wrong weight will be returned to some peer and this peer will ban our node.
Use `bl.second` instead of `arg.blocks[i]`. Also it saves one DB query per returned block.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 60/100
This commit fixes a bug in Monero's blockchain code where a node could accidentally report the wrong block size (weight) to a peer. The bug happened because the code used a mismatched index when some requested blocks were missing. A peer receiving the wrong weight might ban the node, hurting network connectivity. The fix also removes an unnecessary database lookup.
Security candidatewallet_rpc_server: preserve payment ID when editing address bookby selsta · f095abd9 · Jun 3, 2026 · 2 filesMessage 50 · ThinLow 37Details
Commit message · selsta
wallet_rpc_server: preserve payment ID when editing address book
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
privacy or spend-authorization protocolsigning or wallet path
AI analysis · Low 37/100
This commit fixes a bug in Monero's wallet RPC server where editing an address book entry could accidentally drop or mishandle the payment ID associated with an integrated address. The fix ensures the payment ID flag is preserved correctly, and new tests check that converting between integrated and standard addresses works as expected. In practical terms, this could have caused users to send funds without the intended payment identifier, making transactions harder to track or reconcile.
Security candidatetranslations: don't include locationsby tobtoht · b51a0cb8 · Jun 3, 2026 · 14 filesMessage 45 · ThinInformational 15Details
Commit message · tobtoht
translations: don't include locations
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update pathtranslation-only discount
AI analysis · Informational 15/100
This commit removes source-code file names and line numbers from Monero's translation files. It is a routine cleanup to make translation updates smaller and less noisy. There is no change to program logic, no bug fix, and no security improvement or regression.
Security candidatetx_pool: fix use-after-free in prune() - txid was a reference to an item which was later deleted in remove_tx_from_transient_lists(), and txid was used after thatby SChernykh · b5f7330e · Jun 3, 2026 · 1 fileMessage 73 · AdequateModerate 59Details
Commit message · SChernykh
tx_pool: fix use-after-free in prune() - txid was a reference to an item which was later deleted in remove_tx_from_transient_lists(), and txid was used after that
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 59/100
This commit fixes a use-after-free bug in Monero's transaction pool (tx_pool). The code was storing a reference to a transaction ID, then deleting the underlying data structure that held that ID, and later still using the now-stale reference. The fix simply copies the ID value instead of holding a reference, so it remains valid after deletion. This is a memory-safety bug that could cause crashes or, in the worst case, be exploited to manipulate transaction processing, though the commit itself does not describe any exploit.
AI review queuedsimplewallet: add wallet-dir flagby jpk68 · ed7d4637 · Jun 3, 2026 · 3 filesMessage 60 · AdequateInformational 20Details
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 20/100
This commit adds a new --wallet-dir command-line option to the Monero command-line wallet (monero-wallet-cli). It lets users specify a single directory where wallet files should be looked for and saved. The change is a convenience/usability feature and does not appear to fix a security bug or introduce a dangerous capability. The code only accepts absolute paths for the directory and ignores the option if an absolute wallet-file path is given, which reduces the chance of tricking the wallet into writing files somewhere unexpected.
AI review queuednet: canonicalize Tor/I2P hosts during deserializationby selsta · 0fc5bb7c · Jun 3, 2026 · 3 filesMessage 50 · ThinLow 48Details
Commit message · selsta
net: canonicalize Tor/I2P hosts during deserialization
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Low 48/100
This change makes Monero's network address handling for Tor and I2P more consistent by converting hostnames to lowercase when they are read from stored or received data. Before this fix, an address like 'EXAMPLE.onion' written in capital letters would be treated differently from 'example.onion', which could cause mismatches, failed connections, or possibly bypass security checks that rely on exact string comparison. The patch adds a normalization step during deserialization and includes tests to confirm it works.
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 35/100
This commit fixes a bug in Monero's wallet RPC server where the rescan_blockchain command was not passing through a new keep_key_images option. A hard rescan normally destroys key images (the proof that a coin has already been spent), so the patch also blocks the contradictory combination of a hard rescan while trying to preserve key images. The change is mostly a missing-parameter fix, but mishandling key images could in theory affect wallet balance accuracy or spendability.
Security candidateworkflows: speed up slow-hash in PR core_testsby selsta · 9f6ffb54 · May 31, 2026 · 2 filesMessage 45 · ThinInformational 18Details
Commit message · selsta
workflows: speed up slow-hash in PR core_tests
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 18/100
This commit changes Monero's CI testing workflow to optionally reduce the number of slow-hash iterations during automated pull-request tests, so the tests run faster. It does not change the real Monero mining or transaction verification code used by ordinary nodes or wallets. The production default of about 1 million iterations stays the same unless someone explicitly compiles with a special override flag. The main risk is accidental: if a binary were built with the reduced iteration count and used in production, the proof-of-work would be much weaker. But the commit only applies the override inside GitHub's test runners for pull requests.
AI review queuedutils/fish: use correct suffixes for ssl filesby jpk68 · dc73ab29 · May 31, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · jpk68
utils/fish: use correct suffixes for ssl files
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: broader security terminologysecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit updates the Fish shell auto-completion scripts for Monero command-line tools. It changes the suggested file extensions for SSL private keys and certificates from .pem to .key and .crt respectively. This is a cosmetic/usability improvement for tab-completion only and does not change how the actual software handles SSL files or introduce any security vulnerability.
simplewallet: deduplicate human-readable timespan function
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 · Informational 15/100
This commit is a routine code cleanup: it removes a duplicate copy of a helper function that converts a number of seconds into a human-readable phrase like '5 minutes' or '2 days', and makes the wallet use a shared version already present elsewhere. There is no change to security-sensitive logic, no bug fix, and no vulnerability.
AI review queuedsimplewallet: fix error messageby jpk68 · ef4f8b87 · May 30, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · jpk68
simplewallet: fix error message
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit changes a single English sentence in a user prompt. It rewords 'Are you sure to overwrite it?' to 'Are you sure you want to overwrite it?' There is no functional, security, or behavioral change to the wallet software.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 17/100
This commit replaces older, compiler-specific thread-local storage keywords (__thread) with standard C/C++ ones (thread_local and _Thread_local). It is a portability and standards-compliance cleanup. There is no direct evidence in the commit that this fixes an exploitable security vulnerability.
AI review queuedtranslations: remove translation files containing no translationsby tobtoht · dde7997a · May 28, 2026 · 33 filesMessage 50 · ThinInformational 15Details
Commit message · tobtoht
translations: remove translation files containing no translations
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
This commit simply deletes 33 translation files that contained no actual translations—only English placeholder text. It is a cleanup change with no security relevance.
AI review queuedadd safety for future fork heightsby SNeedlewoods · 10b0118c · May 27, 2026 · 1 fileMessage 45 · ThinLow 29Details
Commit message · SNeedlewoods
add safety for future fork heights
45/100 · ThinMessage clarity
✓ 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 small patch fixes a wallet function that estimates the current blockchain height by looking at known past 'fork' events. Before the fix, if a fork was scheduled in the future, the code only added blocks when time had already passed the fork, but did nothing sensible when the fork was still ahead. The new code subtracts the remaining time from the estimate, and returns 0 with an error log if the calculation would go negative. This prevents the wallet from producing a nonsensical or underflowing height estimate, which could affect transaction creation, fee calculations, or lock-time checks.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 12/100
This commit is a routine code cleanup: it moves some serialization declarations out of a core cryptographic header file into a new dedicated header. There is no indication this fixes a security bug or changes how data is actually processed; it only reorganizes where certain type definitions live to make the codebase easier to maintain.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathparser or protocol path
AI analysis · Low 37/100
This commit removes the entire 'pay-to-use RPC' feature from the Monero node software. Previously, node operators could optionally require remote users to do small proof-of-work payments (or mining shares) before serving RPC requests. The patch deletes the payment logic, command-line options, RPC commands, tests, and shell completions. It is a feature-removal cleanup, not a fix for an active vulnerability, and it makes RPC access free again on nodes that had not separately restricted it.
AI review queuedtests: remove psutilby tobtoht · af4e0cf4 · May 26, 2026 · 4 filesMessage 38 · OpaqueInformational 15Details
Commit message · tobtoht
tests: remove psutil
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 simply removes an unused dependency called 'psutil' from the Monero test suite. It updates documentation and build checks to no longer require psutil, and deletes a helper function that reported available RAM during a mining test. There is no indication this fixes or introduces a security issue.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100
This commit simply deletes an unused experimental utility for building cryptographic transcripts (data-to-be-hashed) in the Seraphis crypto work area. It removes the source files, the CMake build target, and test-suite links. There is no runtime code change, no bug fix, and no security patch.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100
This commit only fixes the formatting of copyright comments across many source files. It removes blank lines between the copyright line and the license text, adds missing copyright lines, fixes minor whitespace issues, and removes an unused debug macro. There are no changes to program logic, security behavior, or functionality.
AI review queuedwallet2: guard optimized coinbase refresh against empty voutby selsta · 57f4cda1 · May 22, 2026 · 1 fileMessage 50 · ThinLow 29Details
Commit message · selsta
wallet2: guard optimized coinbase refresh against empty vout
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 patch fixes a corner case in Monero's wallet refresh logic. When scanning a coinbase (miner) transaction with no outputs, the wallet could previously call an internal output-generation helper with zero outputs, which may cause an error or undefined behavior during refresh. The fix skips that work when there are no outputs. It is a defensive hardening change rather than a clear exploit path for stealing funds.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Moderate 61/100
This patch fixes the way Monero's network code reads incoming message headers. Previously, the code directly cast raw byte buffers to structured header types, which can crash or behave incorrectly on some processors when the memory address is not properly aligned. The fix copies the bytes into a properly aligned variable first using memcpy. This is a robustness/correctness fix that may prevent denial-of-service crashes from malformed or specially positioned network data, but the commit message does not frame it as a security vulnerability.