XMR
← All projectsMonero Project

Monero

Reference Monero node, command-line wallet, consensus, networking, and cryptographic protocol implementation.

Cryptographic librariesMoneroNode implementationsPrivacy protocolsNormal
Repository coverage

936 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

278security candidates305second-pass queue583AI analyses
116commits · 30 days
247commits · 60 days
684commits · 180 days
899commits · 365 days
Backfill bands
Sep 27 → Mar 3192 seen34 candidatesComplete
Mar 31 → Jul 29369 seen101 candidatesComplete
Jul 29 → Aug 28128 seen36 candidatesComplete
Aug 28 → Sep 2788 seen21 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

53/100 average clarity
22Strong · 80–100
158Adequate · 60–79
690Thin · 40–59
66Opaque · 0–39
14security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
jeffro256664153257
koe424258
tobtoht35281200155
Cole Munz424177
Masamune222164
SNeedlewoods906152
selsta17751100051
j-berman443035058
jpk68931655046
Samy451129048
Thomas271015057
SChernykh1188062
Analysis record

Published AI watches

Last scanned 36 minutes ago

Informational 15 AI analysisMessage 68 · Adequate
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11439

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…

f8632a38by tobtoht+355−02 files
No security note in commit
Informational 24 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11741

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
f9e6b2c1by tobtoht+77−598 files
No security note in commit
Low 25 AI analysisMessage 53 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

db: cleanup following PR #11425

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
e108199dby koe+77−598 files
No security note in commit
Low 30 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11732

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
4ab1a673by tobtoht+1−01 file
No security note in commit
Informational 19 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11739

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
90ab1660by tobtoht+52−5218 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11438

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
7b6d76b1by tobtoht+144−02 files
No security note in commit
Low 26 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11737

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
dfa1a30dby tobtoht+56−104 files
No security note in commit
Moderate 51 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11710

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
e64f2bc1by tobtoht+8−42 files
No security note in commit
Informational 19 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11714

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…

da768cd9by tobtoht+18−12 files
No security note in commit
Moderate 59 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11720

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
c4a1491bby tobtoht+34−02 files
No security note in commit
Moderate 61 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11724

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
084af8f6by tobtoht+3−61 file
No security note in commit
Moderate 67 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11726

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
b5402182by tobtoht+266−62 files
No security note in commit
Low 27 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11697

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
df52dd3eby tobtoht+301−1512 files
No security note in commit
Moderate 57 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11696

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
49ee3f43by tobtoht+9−422 files
No security note in commit
Low 37 AI analysisMessage 68 · Adequate
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11693

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
a2ef2c6aby tobtoht+5−241 file
No security note in commit
Low 44 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11655

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
61055c9dby tobtoht+47−392 files
No security note in commit
Moderate 57 AI analysisMessage 58 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11603

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
7b3f6271by tobtoht+2−01 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11492

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
4014125fby tobtoht+364−02 files
No security note in commit
Low 27 AI analysisMessage 66 · Adequate
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

Merge pull request #11653

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
8b99fe43by tobtoht+55−02 files
No security note in commit
Moderate 65 AI analysisMessage 45 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

wallet2: handle .keys saves and overlapping paths

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
4cc0e506by Samy+266−62 files
No security note in commit
Repository ledger

Explore captured commits

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

AI review queuedwallet: copy parsed crypto fieldsby Ap4sh · 04c6da4b · Jul 3, 2026 · 4 filesMessage 45 · ThinLow 46Details
Commit message · Ap4sh

wallet: copy parsed crypto fields

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 46/100

This commit changes how Monero's wallet code copies sensitive cryptographic data (secret keys, transaction hashes, payment IDs) from one memory location to another. Previously it used direct pointer casting, which can violate strict type alignment rules and may cause undefined behavior on some platforms. The patch replaces those casts with explicit memory copies (memcpy). This is a defensive hardening change: it reduces the risk of crashes or misaligned memory reads, but the commit itself does not claim to fix an active exploit or known vulnerability.

Security candidatecryptonote: scope 202612 PoW workaroundby selsta · dc8bc028 · Jul 3, 2026 · 5 filesMessage 68 · AdequateModerate 60Details
Commit message · selsta

cryptonote: scope 202612 PoW workaround

The block 202612 PoW workaround previously applied to any block at
height 202612. Restrict it to the object hashes of the known historical
mainnet, testnet, and stagenet block hashing blobs so new chains do not
inherit the fixed PoW hash, which would prevent sync or mining past that
height if their difficulty is higher.

Reported-by: DataHoarder
Co-authored-by: jeffro256 <jeffro256@tutanota.com>

68/100 · AdequateMessage clarity
✓ 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 narrows a long-standing special-case workaround for Monero block 202612. Previously, any new blockchain fork would have inherited a hard-coded proof-of-work hash at that exact height, which could stop nodes from syncing or miners from producing valid blocks if the network's difficulty was higher than the fixed value. The change now applies the workaround only to the known historical mainnet, testnet, and stagenet blocks, so new or private chains compute proof of work normally.

Security candidatePrevent inaccurate missing spans when adding a blockby j-berman · 700ec36e · Jun 30, 2026 · 2 filesMessage 50 · ThinLow 34Details
Commit message · j-berman

Prevent inaccurate missing spans when adding a block

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathparser or protocol path
AI analysis · Low 34/100

This commit fixes a race condition in Monero's block synchronization code. When multiple threads check which blocks are missing and write newly received blocks to the database at the same time, one thread can read an outdated database height and wrongly conclude that a block is missing. The patch adds a new mutex to synchronize these checks, reducing false 'missing span' reports that could slow or disrupt syncing. The commit message and comments do not frame this as a security vulnerability, but as a correctness/robustness fix.

AI review queuedtests: fix Windows unit test failuresby selsta · eaf139a2 · Jun 30, 2026 · 2 filesMessage 78 · AdequateInformational 19Details
Commit message · selsta

tests: fix Windows unit test failures

Preserve line endings for test fixtures so file hashes remain stable
across platforms.

Temporarily release the wallet keys lock while inspecting the keys file,
then reacquire it and verify the lock state. This lets the test read the
file on Windows, where the lock prevents a concurrent read open.

Avoid passing possibly negative char values to std::isprint(), which is
undefined behavior except for EOF.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit fixes three test-only issues that caused unit tests to fail on Windows. It ensures test data files keep consistent line endings so their cryptographic hashes match, lets a test briefly release a file lock so it can read a wallet keys file on Windows, and avoids a minor undefined-behavior case when checking whether characters are printable. None of these changes affect the Monero wallet or node code that users rely on; they only make the test suite more reliable.

Security candidatecryptonote_basic: remove legacy address parserby Ap4sh · dc45f673 · Jun 30, 2026 · 4 filesMessage 45 · ThinInformational 16Details
Commit message · Ap4sh

cryptonote_basic: remove legacy address parser

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 16/100

This commit removes an old, unused way of representing Monero wallet addresses. The old format used a simple checksum that added up bytes, which is weaker than modern formats. The change deletes the legacy parser and the test that checked it still worked. There is no direct evidence this was exploitable, but removing weak legacy code reduces future risk.

Security candidatechore: remove msvc remnantsby jpk68 · 7eb70c78 · Jun 30, 2026 · 12 filesMessage 47 · ThinInformational 15Details
Commit message · jpk68

chore: remove msvc remnants

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100

This commit removes leftover code that was only used when building Monero with Microsoft Visual C++ (MSVC). It deletes special-case build rules, compiler-specific macros, and Windows-only helper code. There is no change to how Monero handles money, keys, network messages, or cryptography on supported platforms. It is a cleanup change, not a security fix.

Security candidatetxpool: re-relay txs that haven't been relayed and need to beby j-berman · 5a2bd895 · Jun 30, 2026 · 1 fileMessage 81 · StrongLow 35Details
Commit message · j-berman

txpool: re-relay txs that haven't been relayed and need to be

Fixes the following circumstance:
1. Wallet submits tx to node.
2. Node adds tx to pool and queues for relay.
3. Node shuts off before the relay executes in the strand.
4. Node restarts.
5. Now, the fix ensures the node will re-relay the tx in the
get_relayable_transactions loop.

Also makes sure that stem txs don't have last_relayed_time set
to max, which would prevent them from ever being re-relayed on
a restart as well.

Context: https://github.com/seraphis-migration/monero/issues/365#issuecomment-4811722029

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive path
AI analysis · Low 35/100

This patch fixes a bug in how Monero nodes remember whether they have shared new transactions with peers. If a node received a transaction but shut down before it could broadcast it, the node would previously never try again after restarting, so the transaction could sit forgotten in the node's memory pool. The fix makes the node re-broadcast such unshared transactions during its normal cleanup loop. It also fixes a related timing issue for privacy-preserving 'stem' transactions so they are not permanently blocked from re-broadcasting.

Security candidatecrypto: fe_reduce_vartimeby j-berman · 9f521668 · Jun 29, 2026 · 2 filesMessage 25 · OpaqueLow 34Details
Commit message · j-berman

crypto: fe_reduce_vartime

25/100 · OpaqueMessage clarity
✓ Descriptive subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive path
AI analysis · Low 34/100

This commit refactors how Monero converts byte strings into elliptic-curve field elements and adds a helper function to 'reduce' oversized field elements back into a safe range. The change is defensive: it separates the low-level byte-to-field conversion from the point-decompression logic and introduces a normalization routine so that outputs of addition/subtraction can safely be reused as inputs to further additions/subtractions. There is no direct evidence in the commit message or diff of an exploitable vulnerability, but the new helper addresses a known class of subtle correctness issues in Curve25519-style field arithmetic.

Security candidatecrypto: fast fe_batch_invert using Montgomery's trickby j-berman · 4f2a8a42 · Jun 29, 2026 · 6 filesMessage 81 · StrongInformational 13Details
Commit message · j-berman

crypto: fast fe_batch_invert using Montgomery's trick

https://iacr.org/archive/pkc2004/29470042/29470042.pdf 2.2

Also includes:
- fe_equals function
- breaks out fe_from_bytes_vartime function

Co-authored-by: Jeffro <jeffro256@tutanota.com>

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive path
AI analysis · Informational 13/100

This commit adds a faster way to compute many mathematical inverses at once in Monero's cryptography code, plus helper functions and tests. It is a performance and code-organization change, not a security fix or vulnerability. There is no evidence in the commit or supplied references that it addresses a security issue.

Security candidatesrc: update checkpoints to match v0.18.5.1by selsta · c914c27c · Jun 29, 2026 · 4 filesMessage 45 · ThinInformational 22Details
Commit message · selsta

src: update checkpoints to match v0.18.5.1

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 22/100

This commit updates Monero's built-in blockchain checkpoints to match the v0.18.5.1 release. Checkpoints are hard-coded reference points that help nodes quickly verify they are following the correct chain and protect against certain history-rewriting attacks. The README version references are also updated from v0.18.4.1 to v0.18.5.1. There is no code-level vulnerability being patched here; it is a routine network-consistency maintenance update.

Security candidateblockchain: improve incoming block scan table handlingby selsta · 265e95a8 · Jun 29, 2026 · 1 fileMessage 50 · ThinLow 34Details
Commit message · selsta

blockchain: improve incoming block scan table handling

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 34/100

This commit refactors how Monero's blockchain code builds a lookup table used when checking incoming blocks. It replaces a slower, manual scan through offsets with a sorted binary search, and removes duplicate amount handling. The change appears to be a performance and correctness cleanup rather than a clear security fix, but the old code's linear search and duplicate-amount logic could theoretically hide or mishandle edge cases in block validation.

Security candidateOptimized handle_notify_new_transactions's duplicate tx check - Check sha256 digests instead of full blobs (much less memory used) - Replace `find->insert` sequence with a single `insert` - 2x fewer hashset accesses - Preallocate the required size for the hashset (no full-table rehashes)by SChernykh · 330062a0 · Jun 29, 2026 · 1 fileMessage 73 · AdequateInformational 19Details
Commit message · SChernykh

Optimized handle_notify_new_transactions's duplicate tx check
- Check sha256 digests instead of full blobs (much less memory used)
- Replace `find->insert` sequence with a single `insert` - 2x fewer hashset accesses
- Preallocate the required size for the hashset (no full-table rehashes)

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathparser or protocol path
AI analysis · Informational 19/100

This commit is a performance optimization in Monero's transaction-processing code. It changes how the node detects duplicate transactions sent by a peer: instead of comparing the entire transaction data (which uses lots of memory), it compares small SHA-256 fingerprints. It also streamlines how those fingerprints are stored. There is no direct evidence this fixes a security bug, but it removes a memory-pressure path and hardens duplicate detection against subtle blob differences.

AI review queuedwallet2: avoid linear scans in pool state updatesby selsta · d40944c4 · Jun 28, 2026 · 2 filesMessage 45 · ThinInformational 19Details
Commit message · selsta

wallet2: avoid linear scans in pool state updates

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 · Informational 19/100

This commit is a performance optimization in the Monero wallet. It replaces repeated linear list scans with hash-set lookups when checking which transactions are in the memory pool. The change should make wallet refresh faster when there are many pending transactions, but it does not appear to fix a security vulnerability or change behavior in a way that is directly exploitable.

Security candidateFix spelling typos in comments and string literalsby Thomas · fecef767 · Jun 27, 2026 · 32 filesMessage 50 · ThinInformational 15Details
Commit message · Thomas

Fix spelling typos in comments and string literals

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathparser or protocol path
AI analysis · Informational 15/100

This commit only fixes spelling mistakes in comments, documentation, and user-facing error/log strings. No program logic, calculations, or security behavior was changed. It is not a security fix and cannot be exploited.

AI review queuedwallet2: remove unused pool tx removed callbackby selsta · b1f45614 · Jun 26, 2026 · 2 filesMessage 68 · AdequateInformational 16Details
Commit message · selsta

wallet2: remove unused pool tx removed callback

on_pool_tx_removed has no implementation beyond the empty default callback
and is not wired through the wallet API layer.

The only call site passed txid after erasing the payment entry that owned it,
leaving a dangling reference.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 16/100

This commit removes a leftover wallet callback function that did nothing useful. The callback was called after a transaction record had already been deleted, so the transaction ID it received was technically invalid (a 'dangling reference'). Because the callback had no real implementation and was not exposed through the public wallet API, this appears to be a cleanup of dead code rather than a fix for an actively exploitable bug. The main risk is avoiding undefined behavior if someone later tried to use that invalid reference.

Security candidatetests: add CLSAG fuzz testsby selsta · 01e06da4 · Jun 25, 2026 · 15 filesMessage 70 · AdequateInformational 15Details
Commit message · selsta

tests: add CLSAG fuzz tests

Co-authored-by: Nym Seddon <unseddd@shh.xyz>

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidenceprivacy or spend-authorization protocol
AI analysis · Informational 15/100

This commit only adds new software tests (fuzz tests) for Monero's CLSAG ring signature verification code. It does not change any production code that handles transactions, wallets, or network data. Fuzz tests feed random or crafted data to a function to check it behaves safely, but the tests themselves are not a vulnerability or a fix. There is no indication this commit addresses a known security bug.

Security candidatetests/fuzz: fix cold-outputs importby jeffro256 · 70bdd2d9 · Jun 25, 2026 · 4 filesMessage 55 · ThinInformational 16Details
Commit message · jeffro256

tests/fuzz: fix cold-outputs import

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
fuzzing or regression evidenceauthentication path
AI analysis · Informational 16/100

This commit updates a Monero fuzz test that feeds random or crafted data to the wallet's cold-output import code. It only changes test files and test code; no production wallet or node code is modified. The change makes the fuzzer use the newer, safer import path (import_outputs_from_str) and adds a testnet wallet setup. On its own, this is a test-harness cleanup, not a fix for a live security bug.

Security candidatep2p: restore safe sync mode when target height dropsby selsta · d8f3b81f · Jun 24, 2026 · 1 fileMessage 50 · ThinLow 46Details
Commit message · selsta

p2p: restore safe sync mode when target height drops

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathparser or protocol path
AI analysis · Low 46/100

This small patch changes Monero's peer-to-peer sync logic so that when the node's estimated target blockchain height suddenly drops, it re-enables 'safe sync mode' if the target is now very close to the node's current height. Safe sync mode is a more conservative way of downloading and verifying blocks. The change is defensive: without it, a node might stay in a faster but less safe sync mode even when the network no longer appears to be far ahead, which could make it more vulnerable to a malicious peer manipulating its view of the chain height. The commit message does not call this a security fix, and no independent researcher is credited.

AI review queuedwallet: store fee for not_enough_{unlocked_,}balanceby tobtoht · 06221f20 · Jun 24, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · tobtoht

wallet: store fee for not_enough_{unlocked_,}balance

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 only adds a 'fee' field to two existing wallet error types (not_enough_unlocked_money and not_enough_money). It does not change how transactions are validated, how fees are calculated, or how money is handled. It simply lets the wallet remember and report what fee was involved when an error about insufficient balance occurs. There is no security issue visible in this change.

AI review queuedtests: remove dead transactions_generation_from_blockchainby Thomas · 8a744a63 · Jun 23, 2026 · 3 filesMessage 73 · AdequateInformational 15Details
Commit message · Thomas

tests: remove dead transactions_generation_from_blockchain

Functional test commented out since 2014 (296ae46ed); never #included or
called (main.cpp only runs transactions_flow_test).

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit simply deletes an old, unused test file and its header. The code being removed was entirely commented out since 2014, was never compiled into the test program, and was never run. It has no effect on the live Monero software or its users.

Security candidatecommon: remove unused data_cache.hby Thomas · b5136b1a · Jun 23, 2026 · 2 filesMessage 60 · AdequateInformational 15Details
Commit message · Thomas

common: remove unused data_cache.h

Dead since 40eb82873 (2025-10) moved verRct caching into the mempool;
only a stale #include remained in blockchain.cpp.

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 15/100

This commit simply deletes an unused header file and removes its leftover include statement. It is a cleanup change with no functional or security effect on the running software.

AI review queuedhttp: parse server Content-Length strictlyby alhudz · 07f7c752 · Jun 23, 2026 · 2 filesMessage 45 · ThinModerate 51Details
Commit message · alhudz

http: parse server Content-Length strictly

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 · Moderate 51/100

This commit tightens how Monero's built-in HTTP server reads the 'Content-Length' header. Previously, the server would accept malformed values like '5abc' or '0x10' and silently use only the leading digits as the body length. Now it rejects the whole value unless it is a plain number. This kind of lenient parsing can cause request smuggling or desynchronization between the server and other HTTP components, which attackers can sometimes exploit to bypass security controls or poison caches.

AI review queuedsimplewallet: fix some more typosby jpk68 · 14e17537 · Jun 22, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · jpk68

simplewallet: fix some more typos

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 · Informational 15/100

This commit fixes three spelling mistakes in user-facing error messages inside Monero's command-line wallet. There are no code logic changes, no security fixes, and no functional impact.

Security candidatecmake: set message mode everywhereby tobtoht · 9ed0a114 · Jun 21, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · tobtoht

cmake: set message mode everywhere

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathdocumentation-only discount
AI analysis · Informational 15/100

This commit only changes two CMake build messages from plain 'message(...)' to 'message(STATUS ...)'. That is a cosmetic/logging change: it tells CMake to print these lines as informational status messages instead of bare output. It does not change any compiled code, cryptographic logic, wallet behavior, or security boundary.

AI review queuedhttp: share deterministic header field parserby selsta · 389f3660 · Jun 21, 2026 · 4 filesMessage 45 · ThinModerate 66Details
Commit message · selsta

http: share deterministic header field parser

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 · Moderate 66/100

This commit replaces a complex regular-expression-based HTTP header parser with a single, stricter, hand-written parser shared between the client and server code. The old parser could silently accept malformed or ambiguous headers, which in HTTP can lead to security problems such as request smuggling, cache poisoning, or unexpected behavior. The new parser rejects headers that do not follow a well-defined format and validates the characters allowed in header names. It also adds many tests that demonstrate malformed headers are now rejected. The commit itself does not describe this as a security fix, but the change clearly reduces attack surface in the way Monero's HTTP stack processes incoming and outgoing headers.