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.
Security candidatecrypto: get generators return refby jeffro256 · 44ec22be · Aug 18, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · jeffro256
crypto: get generators return ref
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 15/100
This commit is a small performance and code-quality change. It changes several functions that return copies of fixed cryptographic 'generator' values so that they return constant references instead. This avoids making unnecessary copies of values that never change. There is no security issue visible in the diff itself.
Security candidatefix T,U,V generator raw valuesby jeffro256 · 25a7c97b · Aug 18, 2026 · 1 fileMessage 45 · ThinHigh 78Details
Commit message · jeffro256
fix T,U,V generator raw values
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 · High 78/100
This commit changes three special cryptographic constants—named T, U, and V—used in Monero's upcoming FCMP++ privacy protocol. These constants are like fixed 'reference points' on a mathematical curve that the protocol relies on to prove transactions are valid without revealing who sent what. The old values were apparently copied from an outdated source and were wrong; the new values match the updated reference implementation. If the wrong constants had gone live, Monero's privacy proofs could have been broken or forged, potentially allowing someone to create fake coins or trace transactions. The commit itself only updates the byte strings and their sanity-check first bytes; it does not explain how the error was discovered or whether any real funds were at risk.
✓ 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 25/100
This Monero wallet RPC patch changes how transaction hashes are reported for incoming transfers that the wallet does not know the source transaction for. Previously, the RPC would return a string of all-zero characters ('0000...0000') as the transaction hash. After the patch, it returns an empty string instead. This is a correctness and API-clarity fix rather than a direct exploit, but returning a fake all-zero hash could have misled downstream software into treating an unknown transfer as a known one.
AI review queuedtake m_daemon_rpc_mutex in wallet2::get_daemon_addressby Alhuda Khan · 472a275d · Aug 18, 2026 · 2 filesMessage 50 · ThinLow 35Details
Commit message · Alhuda Khan
take m_daemon_rpc_mutex in wallet2::get_daemon_address
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 35/100
This commit fixes a thread-safety bug in the Monero wallet. A function that reads the daemon's network address (get_daemon_address) was accessing shared data without holding a lock, while other parts of the code can change that same data under a mutex. The fix adds the missing lock and makes the mutex 'mutable' so it can be locked even in functions that promise not to modify anything. In practice this could lead to race conditions such as reading a partially updated or inconsistent daemon address, which might cause the wallet to connect to the wrong node or behave unpredictably. There is no direct evidence in the commit of an exploitable security outcome such as remote code execution or theft of funds.
AI review queuedFix two separate data races in async levin commandsby Lee Clagett · 6f82bacb · Aug 18, 2026 · 1 fileMessage 50 · ThinModerate 63Details
Commit message · Lee Clagett
Fix two separate data races in async levin commands
50/100 · ThinMessage clarity
✓ Specific, 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 · Moderate 63/100
This patch fixes two data races in Monero's asynchronous Levin network protocol handler. A data race happens when multiple threads access the same memory at the same time without proper locking, which can cause crashes, hangs, or corrupted state. The fix adds a mutex around shared callback/timer state and removes a separate 'cancel_timer' virtual method that was being called from multiple threads without synchronization. The commit title explicitly calls these 'data races'.
AI review queuedsimplewallet: allow closing wallet when locked due to inactivityby jpk68 · e03c6a20 · Aug 18, 2026 · 2 filesMessage 62 · AdequateInformational 23Details
Commit message · jpk68
simplewallet: allow closing wallet when locked due to inactivity
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 23/100
This change fixes a small user-experience bug in Monero's command-line wallet. Previously, if the wallet locked itself after a period of inactivity and the user tried to close it (for example by pressing Ctrl-C while being asked for the password), the program would keep looping and asking for the password, making it hard to exit. Now, when the password prompt is interrupted, the wallet closes cleanly instead.
Lower-prioritycmake: make Cargo command aware of jobserverby selsta · 00466ca8 · Aug 17, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · selsta
cmake: make Cargo command aware of jobserver
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedwallet2: return concrete low priority when adjust_priority failsby woodser · 9f5653cb · Aug 17, 2026 · 1 fileMessage 50 · ThinLow 35Details
Commit message · woodser
wallet2: return concrete low priority when adjust_priority fails
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 35/100
This change alters how the Monero wallet picks transaction fees when its automatic fee-estimation helper runs into problems. Previously, if the helper failed or got bad data, it returned whatever priority the caller had requested—potentially a high or urgent priority. Now it falls back to the lowest priority ('Unimportant'). This could mean users' transactions get delayed rather than overpaying, and it reduces the chance that an attacker who can feed bad blockchain data to the wallet can trick it into paying inflated fees. It is a defensive hardening fix, not a clear-cut remote exploit.
AI review queuedsimplewallet: don't exit when unable to get restore dateby jpk68 · d66d420d · Aug 16, 2026 · 1 fileMessage 50 · ThinInformational 17Details
Commit message · jpk68
simplewallet: don't exit when unable to get restore date
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 17/100
This change makes the Monero command-line wallet more forgiving when a user provides a restore date but the wallet cannot reach the network daemon to convert that date into a blockchain height. Previously the wallet would quit with an error; now it prints a warning and continues using a default restore height. This is primarily a usability improvement, but it slightly increases the risk that a restored wallet might scan from the wrong (too recent or too old) block height, potentially missing transactions or scanning more than intended until the user manually corrects it.
✓ 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 39/100
This commit tightens how the Monero software reads incoming HTTP requests by only accepting method names like GET and POST when written in uppercase. Previously, lowercase or mixed-case versions such as 'get' or 'Post' were also accepted. The change makes the parser follow the HTTP standard more strictly, which can help block unusual requests that might be used to bypass security checks or confuse proxies and firewalls.
Lower-prioritydevice_trezor: show error when device is disconnectedby jpk68 · 29922e19 · Aug 15, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · jpk68
device_trezor: show error when device is disconnected
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritydevice_trezor: show error when operations are cancelledby jpk68 · 617cb6ad · Aug 15, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · jpk68
device_trezor: show error when operations are cancelled
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedsimplewallet: fix crash in sweep commands when address is omittedby jpk68 · ddf0786e · Aug 15, 2026 · 1 fileMessage 50 · ThinLow 30Details
Commit message · jpk68
simplewallet: fix crash in sweep commands when address is omitted
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: broader security terminologysecond-pass: security-sensitive path
AI analysis · Low 30/100
This patch fixes a crash in Monero's command-line wallet (simplewallet) when a user runs a 'sweep' command without providing a destination address. Before the fix, the wallet would try to read from an empty list of arguments, likely causing it to crash. The fix adds a simple check: if no address is given, it prints an error and shows usage instructions instead of crashing. This is a reliability bug, not a security vulnerability that allows theft or remote compromise.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityreadme: line break between copyright headersby tobtoht · b6a29b0a · Aug 14, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · tobtoht
readme: line break between copyright headers
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedfunctional_tests_rpc: fix string.join()by a9oss · e000d42a · Aug 14, 2026 · 1 fileMessage 35 · OpaqueInformational 16Details
Commit message · a9oss
functional_tests_rpc: fix string.join()
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 16/100
This is a tiny Python 2-to-3 compatibility fix in a test helper script. It changes an outdated way of joining a list of strings into a modern one. The script only prints a help message listing available tests, so the change has no security relevance and does not affect the Monero wallet, daemon, or any user funds.
Security candidatecryptonote_basic: parse_and_validate_tx param to check max sizeby j-berman · 236ca60b · Aug 13, 2026 · 7 filesMessage 85 · StrongModerate 63Details
Commit message · j-berman
cryptonote_basic: parse_and_validate_tx param to check max size
Simple API to check max blob size before parsing. This is useful when reading blobs from untrusted sources.
@selsta pointed out that coinbase txs can technically be larger than get_max_tx_size(), otherwise we could enforce it on all txs.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
defensive validationcryptography-sensitive pathsigning or wallet pathparser or protocol path
AI analysis · Moderate 63/100
This Monero commit adds an optional size check to transaction parsing functions so that oversized transaction blobs from untrusted network sources are rejected before being decoded. It is a defensive hardening change that consolidates existing size checks and extends them to more code paths, reducing the chance that a maliciously large blob could waste resources or trigger memory-related issues during parsing.
Lower-priorityfunctional_tests: remove unreachable code, kill process after timeoutby SNeedlewoods · a16b3c80 · Aug 13, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · SNeedlewoods
functional_tests: remove unreachable code, kill process after timeout
Co-authored-by: selsta <selsta@sent.at>
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritycmake: enable compiler caching support for rust librariesby jpk68 · 67d99a98 · Aug 12, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · jpk68
cmake: enable compiler caching support for rust libraries
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedsimplewallet: don't ignore misplaced index= in sweep commandsby jpk68 · 6bc69dd5 · Aug 12, 2026 · 1 fileMessage 50 · ThinLow 35Details
Commit message · jpk68
simplewallet: don't ignore misplaced index= in sweep commands
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 35/100
This change fixes a bug in Monero's command-line wallet (simplewallet) where a user typing 'index=' in the wrong position of a 'sweep' command could be silently ignored. Previously, the wallet only checked the very first word for 'index='; if it appeared later, the wallet would act as if no subaddress index was specified, potentially sweeping funds from unintended addresses. The fix scans all words for 'index=' and removes it when found. This is primarily a usability/transaction-safety bug rather than a remote-exploitable vulnerability.
AI review queuedfcmp_pp_rust: fix docker buildby tobtoht · 6f9c5828 · Aug 12, 2026 · 1 fileMessage 35 · OpaqueInformational 16Details
Commit message · tobtoht
fcmp_pp_rust: fix docker build
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
This is a build-system patch that lets the Rust part of Monero compile correctly when targeting Linux systems that use the lightweight 'musl' C library (common in Docker containers). It adds a check so the build picks the right Rust toolchain variant. There is no indication this changes any runtime behavior, cryptographic logic, or network code.
Lower-prioritydepends: set CMAKE_{LANG}_COMPILER_TARGETby tobtoht · 1d909d09 · Aug 12, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · tobtoht
depends: set CMAKE_{LANG}_COMPILER_TARGET
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityrpc, p2p: remove pay-to-use RPC leftoversby Thomas · 67764f67 · Aug 12, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · Thomas
rpc, p2p: remove pay-to-use RPC leftovers
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body