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 2 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 queuedsimplewallet: reject donations when not on mainnetby jpk68 · 773e3070 · Aug 11, 2026 · 1 fileMessage 50 · ThinLow 32Details
Commit message · jpk68

simplewallet: reject donations when not on mainnet

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

This change stops the Monero command-line wallet's built-in 'donate' command from working on test networks. Previously, the wallet tried to convert the official donation address to a testnet/stagenet equivalent, which could send real-looking donations to an address the user did not expect. Now it simply refuses to donate unless you are on the main Monero network.

AI review queuedwallet_rpc_server: expose change amount in transfer entriesby SlowBearDigger · d7f32ed8 · Aug 11, 2026 · 3 filesMessage 50 · ThinInformational 19Details
Commit message · SlowBearDigger

wallet_rpc_server: expose change amount in transfer entries

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

This commit adds a new 'change_amount' field to Monero wallet RPC responses that describe transfers. When you send Monero, part of the input often comes back to you as change. Previously, callers of the wallet RPC had to calculate this themselves from other fields; now it is exposed directly. This is a straightforward feature addition, not a security fix or vulnerability.

Security candidateBlockchain: improve check_block_timestamp() overloadsby jeffro256 · 53ff15b0 · Aug 11, 2026 · 2 filesMessage 40 · ThinModerate 59Details
Commit message · jeffro256

Blockchain: improve check_block_timestamp() overloads

40/100 · ThinMessage clarity
✓ Specific, descriptive subject! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 59/100

This commit refactors how Monero checks whether a new block's timestamp is valid. It splits one timestamp-check function into two: a general helper and one specifically for the main chain. The change also moves the 'future time' check (rejecting blocks stamped more than 2 hours ahead of local time) and the 'not enough blocks' check into the general helper, and it makes the median timestamp output optional. The commit appears to be a code-quality and consistency improvement rather than a clear-cut security fix, but it does tighten behavior when there are fewer than 60 prior blocks and removes a const qualifier from one function. Without a vendor statement, we cannot say it fixes a known vulnerability.

AI review queuedDockerfile: add rustby tobtoht · 23dfb88f · Aug 11, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · tobtoht

Dockerfile: add rust

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit simply adds the Rust programming language toolchain to the project's Docker build environment. It is a routine build-infrastructure change with no apparent security relevance.

AI review queuedp2p: don't reset timeout timer for handshakesby j-berman · 7e0c68b4 · Aug 11, 2026 · 1 fileMessage 68 · AdequateLow 49Details
Commit message · j-berman

p2p: don't reset timeout timer for handshakes

The handshake timeout should just be an absolute timeout, we don't
care about partial messages received during the handshake.

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

This change fixes a peer-to-peer networking timeout behavior. Previously, the handshake timeout timer could be reset by incoming partial data, potentially allowing a remote peer to drag out the handshake indefinitely. Now, the handshake timeout is absolute: if it expires, the connection is dropped regardless of partial progress. This prevents a likely denial-of-service vector where a malicious or slow peer stalls handshakes.

Security candidateBlockchain: static `prevalidate_miner_transaction`by jeffro256 · f60bdfbd · Aug 10, 2026 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · jeffro256

Blockchain: static `prevalidate_miner_transaction`

40/100 · ThinMessage clarity
✓ Specific, descriptive subject! No meaningful explanatory body
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Informational 15/100

This commit only adds the C++ keyword `static` to a single function declaration in a header file. It does not change what the function does, what data it can access, or how users interact with the software. There is no visible security effect.

AI review queuedp2p: use a bool for send()by j-berman · e8718e65 · Aug 10, 2026 · 4 filesMessage 72 · AdequateLow 48Details
Commit message · j-berman

p2p: use a bool for send()

Identified by @selsta

Callers can otherwise misinterpret int -1 as truthy success,
e.g. see make_payload_send_txs

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Explains rationale or failure mode
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 48/100

This patch fixes a type-safety bug in Monero's peer-to-peer networking code. The send() function used to return an integer where -1 meant failure, 0 meant 'connection not found', and 1 meant success. Some callers treated any non-zero value as success, so a -1 failure could be misread as success. The patch changes send() to return a proper true/false boolean so failures cannot be misinterpreted. The commit message explicitly points to make_payload_send_txs as an example of such a caller.

AI review queuedsimplewallet: show error for timed-out hardware walletsby jpk68 · 23d86a96 · Aug 10, 2026 · 1 fileMessage 50 · ThinInformational 22Details
Commit message · jpk68

simplewallet: show error for timed-out hardware wallets

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 change improves the user experience when unlocking a Monero wallet that is paired with a hardware wallet (like Ledger or Trezor). Previously, if the hardware wallet timed out or disconnected during unlock, the software would silently loop back to the password prompt without explaining why. Now it prints a clear error message telling the user to check that the hardware wallet is connected and unlocked. This is a minor reliability/usability fix, not a fix for a serious security vulnerability.

Security candidatecrypto: improve CSPRNG backtracking resistanceby selsta · 2e3ce7d4 · Aug 10, 2026 · 3 filesMessage 60 · AdequateModerate 65Details
Commit message · selsta

crypto: improve CSPRNG backtracking resistance

Reported by xmrack and the MAGIC Monero Fund.

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

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
entropy or randomnesscryptography-sensitive pathseed or entropy path
AI analysis · Moderate 65/100

This commit strengthens Monero's built-in random number generator so that if an attacker later steals the generator's internal memory state, they cannot easily figure out what random numbers were generated in the past. It also locks that sensitive state in RAM so it cannot be swapped to disk. The change is a defensive hardening patch, not a fix for an active exploit, and the exact real-world attack it prevents is not described in the commit materials.

AI review queuedguix: prepare for FCMP++by tobtoht · 98a5e3cc · Aug 10, 2026 · 6 filesMessage 28 · OpaqueInformational 18Details
Commit message · tobtoht

guix: prepare for FCMP++

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 18/100

This commit updates Monero's Guix reproducible-build scripts to add support for Rust dependencies needed by an upcoming feature called FCMP++. It does not change wallet logic, consensus rules, or network code. The changes are build-system plumbing: vendoring Rust crates, configuring Cargo to use them offline, and exposing the Rust standard library source. There is no direct evidence this commit fixes or introduces a security vulnerability.

Security candidatewallet: respect --no-dns for OpenAliasby Samy · 5cc215d5 · Aug 9, 2026 · 6 filesMessage 45 · ThinModerate 52Details
Commit message · Samy

wallet: respect --no-dns for OpenAlias

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 path
AI analysis · Moderate 52/100

This commit fixes a privacy and security bug where Monero wallets ignored the user's --no-dns setting and still performed DNS lookups for OpenAlias addresses (human-readable names like donate.getmonero.org). Now, when DNS is disabled or the wallet is offline, the wallet will not make those DNS queries. This prevents accidental network leaks and reduces the chance that a malicious or monitored DNS server could manipulate address resolution.

AI review queuedepee: validate Levin response command before bufferingby selsta · 6d3abd38 · Aug 8, 2026 · 1 fileMessage 50 · ThinModerate 57Details
Commit message · selsta

epee: validate Levin response command before buffering

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Moderate 57/100

This commit adds a safety check in Monero's network code that verifies an incoming response matches the command that was originally requested before the response is accepted and buffered. Without this check, a malicious or misbehaving peer could potentially send an unexpected response that the software would process incorrectly, possibly causing confusion, resource waste, or protocol errors. The patch is defensive and partial—it validates the command but does not by itself fix a fully demonstrated exploit.

AI review queuedsimplewallet: add clear commandby Thomas · 616613c1 · Aug 8, 2026 · 2 filesMessage 70 · AdequateInformational 15Details
Commit message · Thomas

simplewallet: add clear command

Clears the console screen, as one would expect from a shell.
tools::clear_screen() already existed, but its only caller was the
wallet lock screen; this exposes it as a command.

PAUSE_READLINE() is used because readline substitutes its own streambuf
for std::cout's while running, so without it the escape sequences would
be routed through readline_buffer::sync() and interleaved with prompt
redraws.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit adds a simple 'clear' command to the Monero command-line wallet that clears the terminal screen, similar to typing 'clear' in a shell. It is a user-interface convenience feature with no security relevance.

Security candidatecryptonote_basic: sanity check on key offsetsby j-berman · bfe69908 · Aug 7, 2026 · 1 fileMessage 60 · AdequateModerate 59Details
Commit message · j-berman

cryptonote_basic: sanity check on key offsets

Nice early check on allowed n key offsets per tx based on the
guaranteed ceiling for the entire chain.

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

This commit adds an early safety check to Monero's transaction parsing code. It rejects transactions that contain an impossibly large number of 'key offsets'—the references that identify which previous transaction outputs a transaction is spending from. The limit is based on the maximum allowed transaction size, so any transaction exceeding it cannot be valid anyway. The change is defensive and prevents malformed or oversized transaction data from being processed further.

AI review queueddevice_ledger: fix some commentsby jpk68 · e38cfe66 · Aug 7, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · jpk68

device_ledger: fix some comments

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only fixes spelling and wording in code comments (for example, changing 'Minimal' to 'Minimum' and 'lock' to 'unlock' where the comment was describing the wrong function). No actual program logic, function behavior, or security mechanism was changed.

Security candidatetx_pool: fix write abort and improve locking for relayable txsby jeffro256 · 77acf1f9 · Aug 7, 2026 · 1 fileMessage 50 · ThinLow 41Details
Commit message · jeffro256

tx_pool: fix write abort and improve locking for relayable txs

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

This patch tightens up how Monero's transaction pool records when to next re-broadcast relayable transactions. Previously, a database transaction was held open while iterating over all candidate transactions; now the lock is taken only when there are actual timestamp updates to write, and each update is wrapped in its own try/catch so one failing update does not abort the whole batch. The commit title says it fixes a 'write abort' and improves locking. The change reduces the chance that a transient database error or a single bad metadata update rolls back every scheduled relay update, which could have caused transactions to be re-relayed too soon or too late and potentially leak timing information about Dandelion++ routing.

Security candidatep2p: update peer's height on new block & widen window for relayby j-berman · a47a4365 · Aug 6, 2026 · 2 filesMessage 85 · StrongLow 38Details
Commit message · j-berman

p2p: update peer's height on new block & widen window for relay

- We select peers to relay to based on their latest known sync height.
- This change:
A) makes sure to update the peer's latest known sync height upon
validating the peer's newly relayed blocks.
B) Allows for a wider window so that if we haven't yet received the
peer's block or finished validating it, then the peer can still be
a valid candidate to receive our new 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
cryptography-sensitive pathparser or protocol path
AI analysis · Low 38/100

This Monero patch fixes how the node keeps track of other peers' blockchain heights and who gets to receive new transactions. Previously, a node might think a peer was behind and stop sending it transactions, even when the peer actually had the latest block. The patch updates the peer's height when a new block is validated and allows a small two-block tolerance when choosing transaction-relay peers. The main risk if this were buggy or absent is degraded network propagation: transactions or blocks might spread more slowly, which can hurt network health and potentially be exploited to gain timing advantages (for example, in mining or double-spend scenarios).

Security candidatewallet: fix split transaction change address displayby selsta · f98077b7 · Aug 6, 2026 · 3 filesMessage 73 · AdequateInformational 24Details
Commit message · selsta

wallet: fix split transaction change address display

Display the first non-zero change address after verifying that all
effective change uses the same address. Foreign change is already
rejected during signing, so this only fixes misleading display.

Reported by xmrack and the MAGIC Monero Fund.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 24/100

This commit fixes a display-only bug in Monero wallets. When a transaction is split into multiple parts, the wallet was showing the change address from the first transaction piece, even if that piece had no change. The fix makes it show the first piece that actually has change. The commit message says misleading display is the only effect because foreign change addresses are already rejected during signing, so no money could be sent to an attacker's address.

AI review queuedsrc: remove unused headersby jpk68 · cb88c71e · Aug 6, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · jpk68

src: remove unused headers

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit simply removes header files that were included in source code but not actually needed. It is a routine cleanup with no functional change to the Monero software and no security relevance.

Security candidatesrc: fix issues found through static analysisby jpk68 · fccaccbc · Aug 6, 2026 · 7 filesMessage 45 · ThinLow 26Details
Commit message · jpk68

src: fix issues found through static analysis

45/100 · ThinMessage clarity
✓ 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 26/100

This commit fixes several issues flagged by static analysis tools. Most changes add missing virtual destructors to C++ interface/base classes and remove unused function declarations. Missing virtual destructors can cause subtle memory bugs when objects are deleted through a base-class pointer, but the commit does not show any active crash or exploit path. It is a cleanup/hardening patch rather than a fix for a known active vulnerability.

AI review queuedwallet2: honor max_blocks bound during fast_refresh hash pullsby woodser · 669f90eb · Aug 6, 2026 · 2 filesMessage 50 · ThinLow 26Details
Commit message · woodser

wallet2: honor max_blocks bound during fast_refresh hash pulls

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

This change adjusts how a Monero wallet fetches block hashes during its fast refresh mode. Previously, fast_refresh could keep pulling hashes without respecting the caller's max_blocks limit, which could make a single refresh call run for a very long time and appear unresponsive. The patch caps the number of hash pulls per refresh call and lets the wallet resume later, improving responsiveness. It is a robustness/usability fix rather than a clear-cut security vulnerability, though unbounded network loops can sometimes be abused to delay or hang wallet operations.

AI review queuedChange p2p connection map from raw pointers to weak_ptrsby Lee Clagett · b8028e31 · Aug 5, 2026 · 11 filesMessage 50 · ThinModerate 61Details
Commit message · Lee Clagett

Change p2p connection map from raw pointers to weak_ptrs

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

This commit refactors how Monero's peer-to-peer networking layer tracks active connections. Previously, the code stored raw pointers to connection objects in a central map and used manual reference counting (add_ref/release) to try to prevent those objects from being destroyed while still in use. The patch replaces that with std::weak_ptr and std::shared_ptr, so the map only holds non-owning weak references and the connection objects are kept alive automatically by shared_ptr ownership. This is a defensive hardening change that reduces the risk of use-after-free, double-free, and race-condition crashes in network handling. It is not an obvious remote exploit by itself, but it fixes a class of memory-safety bugs that could be triggered by malicious or unstable peers.

Security candidatecryptonote_core: rm unnecessary db reads before block relayby j-berman · ce14fdc0 · Aug 4, 2026 · 1 fileMessage 50 · ThinLow 26Details
Commit message · j-berman

cryptonote_core: rm unnecessary db reads before block relay

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

This commit removes several database checks that Monero performed before forwarding a newly received block to other peers. Previously, the node verified that it had all the block's transactions and that no blockchain reorganisation had happened. Now it relays the block immediately with fewer checks. The stated goal is performance, but the change could allow invalid or stale blocks to be relayed more easily, potentially contributing to network confusion or denial-of-service. There is no direct evidence in the commit that this fixes a known security bug or that it introduces an exploitable vulnerability.

Security candidateblockchain: if block is known invalid, fail block verificationby j-berman · 20db2e71 · Aug 4, 2026 · 1 fileMessage 60 · AdequateModerate 58Details
Commit message · j-berman

blockchain: if block is known invalid, fail block verification

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Moderate 58/100

This change fixes a logic bug in Monero's blockchain handling. Previously, when the software saw a block it already knew about, it would simply mark it as 'already exists' and move on, even if that block had previously been flagged as invalid. After the patch, if a known-invalid block is seen again, the verification is now correctly marked as failed. This prevents an invalid block from being treated as harmless on re-submission and could stop certain denial-of-service or chain-integrity attacks.

AI review queueddevice_trezor: update protobuf definitionsby jpk68 · 576af29b · Aug 4, 2026 · 9 filesMessage 35 · OpaqueLow 27Details
Commit message · jpk68

device_trezor: update protobuf definitions

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 27/100

This commit updates Monero's Trezor hardware wallet integration to match newer Trezor firmware protobuf definitions. It adds support for new device features (brightness, language packs, authenticity proofs, debug tools, etc.), renames some message types, and moves protobuf extension options into a separate file. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a compatibility update to keep Monero working with current Trezor firmware.