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
947167d ringct: revert range proof proving enum vals (jeffro256)
ACKs: plowsof, jpk68
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
consensus or confidential-proof validationprivacy or spend-authorization protocolmerge-commit duplicate discount
AI analysis · Low 43/100
This tiny change reassigns numeric values to two internal labels used for Monero's range proof types. Instead of the labels automatically getting consecutive numbers (0, 1), they are now explicitly set to 0 and 3. The commit message says it 'reverts' an earlier change that had assigned them consecutive values. This is likely a backward-compatibility or serialization fix, because stored data or network messages may already expect the value 3 for the newer bulletproof range proof. On its own the patch does not look like an active exploit, but a mismatch in these numeric values could in theory cause two versions of the software to disagree about transaction data, which can be a security concern in a cryptocurrency.
AI review queuedMerge pull request #11392by tobtoht · 66b4890d · Oct 13, 2026 · 1 fileMessage 58 · ThinLow 40Details
Commit message · tobtoht
Merge pull request #11392
bcbedbb wallet: persist rings before relaying a transaction (xmrack)
ACKs: selsta, jpk68
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 40/100
This change makes the Monero wallet save ring-signature data to its local database before sending a transaction to the network. If the first broadcast fails and the wallet later rebuilds the transaction, it can reuse the same ring members instead of accidentally picking a new set. Reusing rings helps preserve privacy by avoiding two different-looking transactions that could be linked together.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This is a one-line code change that adds an explicit copy-assignment operator to a small helper class for the Polyseed mnemonic system. It only silences a compiler warning and does not change program behavior or fix any security issue.
5bd76fd blockchain_import: use pool supplements for block verification (selsta)
ACKs: thomasbuilds, jpk68
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationcryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 32/100
This Monero code change refactors how the blockchain import tool verifies blocks. Previously, the tool fed each transaction individually into the core for verification before processing the block. Now it builds a 'pool supplement' from the block's transactions and passes that directly to the block verifier, matching how the network protocol already handles blocks. The change also moves shared helper code into a common header and adds a duplicate-transaction check that was missing before.
This Monero update fixes a bug in how the transaction pool (mempool) handles transactions whose recorded arrival time is in the future. Before the fix, a transaction with a future receive_time could be treated as extremely old and wrongly removed from the pool, or cause misleading statistics. The patch clamps such times to the current time so they are not penalized. A new test confirms future-timestamped transactions stay in the pool while genuinely expired ones are still cleaned up.
This change is a performance optimization for the Monero transaction pool. It caches a 'prunable hash' when a transaction first enters the pool, so that later RPC lookups can reuse the cached value instead of recalculating it every time. There is no direct security vulnerability in the patch; it is intended to make the node faster and the RPC behavior more consistent. The commit message and diff do not describe any security bug or exploit.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationcryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 40/100
This change moves and tightens a limit on how many blocks a Monero node can request at once when syncing. Previously the limit was checked against a larger value (2048) and only logged an error without stopping startup. Now the same limit (100) is enforced earlier and more strictly, returning failure if exceeded. This prevents a node operator from configuring an oversized block-sync request that could strain memory or network handling.
d714a87 wallet2: reject spend proofs for coinbase transactions (selsta)
ACKs: jpk68, PyXMR2025, smhussa22
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
proof-of-work or emission validationsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 46/100
This update changes Monero wallet code so it refuses to create 'spend proofs' for coinbase transactions (the special transactions that pay mining rewards) and also rejects spend-proof strings that claim zero signatures. Spend proofs are a feature that lets a wallet prove it paid someone. The change prevents the wallet from generating or accepting proofs in situations where the proof math does not apply, which could otherwise let someone create a misleading or invalid proof.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
AI review queuedsimplewallet: add --seed and deprecate --electrum-seedby selsta · 101aa635 · Oct 8, 2026 · 2 filesMessage 50 · ThinInformational 18Details
Commit message · selsta
simplewallet: add --seed and deprecate --electrum-seed
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 commit renames a command-line option in Monero's wallet program. The old option '--electrum-seed' is kept working but marked as deprecated, while a new '--seed' option is introduced. It is a routine user-interface cleanup, not a security fix.
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit fixes a test script used during automated testing of Monero's cold-signing feature. It does not change the actual Monero wallet or network code. The fix ensures the test creates the right number of accounts in an observer wallet before checking an address, so the test correctly verifies the intended behavior. There is no security vulnerability here.
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100
This commit fixes a test script used to verify Monero's 'cold signing' feature, where transactions are signed on an offline device. The change only adjusts how the test creates and checks wallet accounts. There is no change to Monero's actual wallet, cryptography, or network code, so it does not affect real users or funds.
0e28dc9 cryptonote_protocol: reset sync time estimate once per sync (jpk68)
ACKs: selsta, PyXMR2025
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Informational 20/100
This patch fixes a minor logic bug in how Monero estimates how long blockchain synchronization will take. Previously, the sync start time and start height were reset every time a new batch of blocks was requested, which could make the time estimate jump around or look wrong. Now they are set only once per sync. There is no indication this is a security issue; it is a user-experience/accuracy fix.
AI review queuedMerge pull request #11432by tobtoht · 42757be7 · Oct 8, 2026 · 2 filesMessage 58 · ThinModerate 58Details
Commit message · tobtoht
Merge pull request #11432
97d682b wallet2: erase all matching payments in import_key_images (jpk68)
ACKs: selsta, PyXMR2025
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 58/100
This patch fixes a bookkeeping bug in Monero's wallet. When a user spent funds from one of their own accounts and the same transaction also sent change or payments to other subaddresses within that same account, the wallet was only removing the first matching incoming record instead of all matching ones. This could leave phantom 'incoming' payments showing money that was actually the user's own change, making the wallet balance and history look wrong. The fix now removes all matching records that belong to the spending account while preserving genuine incoming payments to other accounts. A new functional test confirms the corrected behavior.
AI review queuedMerge pull request #11414by tobtoht · e3dd61d9 · Oct 8, 2026 · 1 fileMessage 58 · ThinLow 41Details
Commit message · tobtoht
Merge pull request #11414
edba670 simplewallet: hold export lock through CSV write (Samy)
ACKs: jpk68, selsta
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 41/100
This patch changes how Monero's command-line wallet holds internal locks while exporting transaction history to a CSV file. Previously, the code briefly released a lock during the export process. The fix keeps the lock held continuously while sensitive wallet data is being written out. The change is defensive and prevents potential race conditions or use of partially-unlocked wallet state during an export that includes private keys.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
parser or protocol pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 66/100
This update tightens how Monero's built-in HTTP server reads incoming request headers. It now rejects requests that have conflicting Content-Length values, oversized numbers, or any Transfer-Encoding header. These rules prevent attackers from tricking the server into misreading where a request body ends, which can lead to request smuggling or desync attacks against the node.
AI review queuedMerge pull request #11468by tobtoht · e62d1986 · Oct 8, 2026 · 2 filesMessage 58 · ThinInformational 15Details
Commit message · tobtoht
Merge pull request #11468
d1b7cd4 contrib: remove rlwrap files (jpk68)
ACKs: selsta, tobtoht, PyXMR2025
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathdocumentation-only discountmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply deletes two text files from the 'contrib/rlwrap' directory. These files were lists of command names used by a third-party command-line helper tool (rlwrap) to provide auto-completion for Monero's command-line programs. Removing them has no effect on Monero's actual code, network, wallets, or blockchain, and does not change any security behavior.