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 queuedsimplewallet: prompt for restore height when using generate-from-deviceby jpk68 · 27367b8a · Jul 27, 2026 · 1 fileMessage 50 · ThinLow 25Details
Commit message · jpk68
simplewallet: prompt for restore height when using generate-from-device
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 25/100
This change adjusts the Monero command-line wallet's setup flow when creating a wallet from a hardware device. Previously, if the user answered anything other than 'yes' to a confirmation prompt, wallet creation was aborted. Now, if the user answers 'no', wallet creation continues but the wallet is told not to start scanning the blockchain from a specific estimated height. This could cause the wallet to scan from the beginning of the chain, which may be slower and could potentially reveal more information about the user's transaction history than intended. It is a usability and privacy-related change rather than a direct exploit.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 19/100
This commit fixes a simple arithmetic bug in how long a transaction has been waiting in the memory pool ("time in pool") was calculated. The old code subtracted the current time from the receive time in the wrong order, which could produce a very large, nonsensical age value instead of a small positive number. The fix ensures the age is always the current time minus the receive time, or zero if the clock somehow runs backward. This is a correctness fix for statistics/ranking of pending transactions, not a direct funds-theft or code-execution vulnerability.
Security candidatewallet2: check for overflow when calculating fee from weightby selsta · e2a4f68e · Jul 26, 2026 · 1 fileMessage 55 · ThinModerate 59Details
Commit message · selsta
wallet2: check for overflow when calculating fee from weight
55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
memory safetysigning or wallet path
AI analysis · Moderate 59/100
This commit adds an overflow check when the Monero wallet calculates transaction fees from a transaction's weight. Before the patch, multiplying a large 'weight' value by a non-zero 'base_fee' could silently wrap around to a tiny number, potentially causing the wallet to propose an incorrect (possibly far too low) fee. The fix now throws an internal wallet error instead of silently producing a wrong result.
device_trezor: improve error message for view key export
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 protocol
AI analysis · Informational 17/100
This commit changes how Monero's Trezor hardware wallet integration handles one specific error. Previously, if a user cancelled the view-key export on their Trezor device, the code fell through to a generic 'Get secret keys exception' message and returned false. Now it immediately throws a clearer error: 'Key export rejected on device.' This is a user-experience and diagnostic improvement, not a fix for an exploitable security flaw.
AI review queuedsimplewallet: use more straightforward device messageby jpk68 · 013741b0 · Jul 26, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · jpk68
simplewallet: use more straightforward device message
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 changes a single user-facing message in Monero's simplewallet from 'Device requires attention' to 'Device requests confirmation'. It is purely a wording clarification for hardware wallet prompts and has no security or functional effect on the code.
AI review queuedsimplewallet: fix restore-date parameter when using generate-from-deviceby jpk68 · 029fa3de · Jul 26, 2026 · 1 fileMessage 50 · ThinInformational 22Details
Commit message · jpk68
simplewallet: fix restore-date parameter when using generate-from-device
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 22/100
This commit fixes a bug in Monero's command-line wallet (simplewallet) when creating a wallet from a hardware device. Previously, if the user provided a restore date but no restore block height, the wallet ignored the date and started scanning from the current blockchain tip. This could cause the wallet to miss older transactions and make the user think funds were lost. The fix makes the wallet correctly convert the restore date into a block height and scan from there.
Use a proper hash function instead of f(x)=x to achieve better distribution of hash values
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy path
AI analysis · Low 45/100
This commit changes how Monero hashes certain internal data types. Previously, some types were hashed using a simple identity function that directly used raw bytes as the hash value, which can cause many items to land in the same hash-table bucket and potentially leak information through timing or collision patterns. The patch replaces that with SipHash-2-4, a keyed, cryptographically designed hash function, using a secret random key generated at startup. This is a defensive hardening change; the commit message frames it only as a performance/distribution optimization, not as a security fix.
✓ 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 adds a new internal cryptography helper for X25519 curve operations in Monero. It does not change existing wallet, network, or consensus logic. There is no indication in the commit or supplied references that this fixes or introduces a security vulnerability; it appears to be a routine feature addition with tests.
AI review queuedwallet_rpc_server: refresh immediately when auto_refresh is enabledby woodser · 04cb0666 · Jul 23, 2026 · 1 fileMessage 50 · ThinInformational 18Details
Commit message · woodser
wallet_rpc_server: refresh immediately when auto_refresh is enabled
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 18/100
This is a small user-experience fix for the Monero wallet's auto-refresh feature. When a user turns on auto-refresh, the wallet will now refresh on the next idle tick instead of waiting a full period first. There is no security bug being fixed here based on the commit content.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
privacy or spend-authorization protocolcryptography-sensitive path
AI analysis · Informational 15/100
This commit adds three new cryptographic generator points (named T, U, and V) to Monero's code. These are special numbers used in a new privacy feature called FCMP++. The commit also adds helper functions to recreate and access these generators. There is no indication of a security bug or vulnerability in this change; it is a straightforward addition of constants needed for future protocol work.
wallet2: bounds check additional derivations in is_out_to_acc
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 · Moderate 58/100
This commit adds a safety check in Monero's wallet code before accessing a list of 'additional derivations' by output index. Previously, if the list was shorter than expected, the code could read past its end (an out-of-bounds read). The patch throws a controlled wallet error instead of crashing or reading invalid memory. The most likely risk is a wallet crash or incorrect output detection when processing malformed or unusual transaction data, rather than direct theft of funds.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Moderate 59/100
This commit adds a safety check in Monero's command-line wallet. When the wallet asks the network node (daemon) for details about certain transaction outputs, it now verifies that the daemon actually returned the same number of results that were requested. Without this check, a malicious or buggy daemon could return fewer (or conceivably different) output records than expected, which might cause the wallet to misread ring member data when displaying or analyzing transactions. The patch is small and defensive; it does not by itself prove an exploitable vulnerability, but it closes a trust boundary gap between the wallet and the daemon.
wallet2: fix task lifetime during parsed block processing
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 · Moderate 51/100
This patch changes how a Monero wallet waits for background worker threads while scanning incoming blocks. Previously, one shared waiter object was used across three separate multi-threaded stages. Now each stage gets its own waiter, so the wallet correctly waits for each batch of tasks to finish before starting the next stage. The commit title says it fixes 'task lifetime' issues, which suggests the old code could have allowed threads to keep running while later code already read or overwrote their data. That kind of bug can lead to crashes or incorrect wallet balance/transaction detection, but the patch does not by itself prove remote theft of funds is possible.
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: opaque commit messagesecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 22/100
This commit removes the 'bootstrap mode' feature from the Monero daemon. Bootstrap mode let a not-yet-fully-synced local daemon forward wallet and mining RPC requests to a remote daemon. Removing it means wallets and miners now only get data from the local daemon. This is a hardening change: it shrinks the attack surface by eliminating a feature that could expose users to untrusted remote nodes, but it is not a fix for a specific known exploit.
Reviewed-by: koe <ukoe@protonmail.com> Reviewed-by: j-berman <justinberman@protonmail.com>
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 18/100
This commit adds two new math helper functions that convert points between two related elliptic-curve formats used in cryptography (Ed25519 and X25519). It is a pure addition of utility code; there is no bug fix, no change to existing behavior, and no indication it addresses a security flaw. The code includes a safety check that rejects the special 'identity' (zero) point, which is a sensible defensive measure.
This is a one-line build-system change that adds a missing library dependency ('wire') so another component can compile and link correctly. There is no indication it fixes a security vulnerability; it appears to be a routine build fix.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Moderate 59/100
This update adds safety checks to the Monero wallet software to detect and stop use of corrupted or tampered wallet cache data. Specifically, it verifies that internal indexes pointing to past transfers are not larger than the actual list of transfers. Without these checks, a damaged or maliciously crafted wallet cache could cause the wallet to read from invalid memory locations, potentially leading to crashes or unpredictable behavior. The change is defensive hardening rather than a fix for an active remote attack.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 47/100
This commit removes compiler directives that forced certain cryptographic data structures to be packed tightly without padding, and replaces some direct multi-byte memory reads with safer memcpy operations. On some processors, reading a multi-byte value from a memory address that is not aligned to that value's size can cause a crash or reduced performance. The change makes the code safer and more portable across different CPU architectures, but it does not appear to fix an exploitable remote vulnerability in the Monero network itself.
✓ 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 19/100
This commit fixes a bug in Monero's wallet API where the recipientAddress() function only returned the first recipient of an unsigned transaction, even when the transaction had multiple recipients. Now it returns all recipients. This is primarily a correctness/functional bug fix. A possible minor security angle is that downstream code relying on recipientAddress() to verify all payment destinations could have been misled into thinking only one recipient existed, but the commit itself does not describe any security impact and no exploit path is evident from the diff.
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 31/100
This commit fixes the way a Monero cryptographic function for ARMv8 processors describes its inline assembly code to the C compiler. Previously, the assembly block did not properly tell the compiler which memory and CPU registers it reads and writes. This can lead to subtle bugs where the compiler optimizes code incorrectly around the assembly, potentially causing wrong hash results or memory corruption on ARMv8 devices. The fix adds proper input/output constraints and a clobber list so the compiler knows exactly what the assembly touches.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationprivacy or spend-authorization protocol
AI analysis · Low 47/100
This commit adds a type check in Monero's JSON deserialization code. Before the fix, when reading a RingCT signature from JSON, the code assumed the 'prunable' field was a JSON object and accessed it directly. If someone supplied a non-object value (like a number or string), the code could read memory incorrectly or crash. The patch now throws a clear error if the type is wrong.
✓ Descriptive subject! 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 adds a new internal helper function in Monero's experimental FCMP++ (Forward-Commitment Membership Proof) code. It converts transaction output data into an intermediate mathematical representation called a 'pre-leaf tuple' by computing derivatives of elliptic-curve points. There is no user-facing change, no bug fix, and no security-relevant behavior described in the commit or diff.
- Function to convert an {output pubkey, commitment} to an output tuple {O,I,C} in prepartion to insert the output tuple into the curve tree. - O = torsion cleared valid output pubkey checked for identity. - I = key image generator. - C = torsion cleared valid Commitment checked for identity. - None of {O,I,C} should have torsion nor == identity. - Introduces the OutputPair variant, which can either be Legacy or Carrot V1 types. Legacy outputs are not checked for torsion at consensus, and use the legacy biased hash to point fn to derive the key image generator (I). Carrot V1 outputs **are** checked for torsion at consensus, and use the unbiased hash to point to derive the key image generator (I).
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
consensus or confidential-proof validationprivacy or spend-authorization protocol
AI analysis · Informational 12/100
This commit adds new code for an upcoming Monero privacy feature called FCMP++. It creates a helper function that converts an output's public key and commitment into a special three-part tuple used by the new system. The commit is defensive in nature: it carefully clears mathematical 'torsion' from points, rejects identity points, and explicitly avoids a subtle double-spend risk that could occur if the wrong version of a key were used around a network upgrade. There is no indication this commit fixes an active bug or vulnerability; it appears to be a building block for future functionality.
Security candidatewallet: derive encrypted payment ID dummy/real status from tx.extra, not cd.destsby waris ) · afcfd976 · Jul 21, 2026 · 3 filesMessage 50 · ThinModerate 59Details
Commit message · waris )
wallet: derive encrypted payment ID dummy/real status from tx.extra, not cd.dests
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 · Moderate 59/100
This Monero wallet patch changes how the wallet decides whether an encrypted payment ID is real or a dummy placeholder. Previously, the wallet relied on destination address data (cd.dests), which could be manipulated by a malicious signer or loaded transaction to make a real payment ID look fake, or a fake one look real. The patch now derives that status directly from the transaction's extra field, where the payment ID is actually stored, and adds a consistency check. This is a security fix for a potential information leak or user deception during multi-step transaction signing.
tests: tests_common library and gen_corpus executable
Adds two components to the tests directory: 1. `tests_common` a shared utility library for different types of tests 2. `gen_corpus` an executable to dynamically generate seed corpora for fuzzing during the build stage
Also updates the transaction fuzzing test to call `ver_non_input_consensus()` for different HF versions.
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidenceconsensus or confidential-proof validationcryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100
This commit adds new testing tools to Monero: a shared helper library for building test transactions and a build-time generator for fuzzing seed data. It also updates one fuzz test to exercise more transaction-validation code paths. There is no change to the live Monero network code, consensus rules, or wallet behavior—only test infrastructure.