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 11 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.

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.

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.

Security candidatewallet: display private view keys for hardware walletsby jpk68 · ae8291f9 · Aug 3, 2026 · 4 filesMessage 50 · ThinInformational 18Details
Commit message · jpk68

wallet: display private view keys for hardware wallets

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
privacy or spend-authorization protocolsigning or wallet path
AI analysis · Informational 18/100

This change lets users of Ledger hardware wallets see their private view key in the Monero command-line wallet, something previously hidden with the message 'On device. Not available.' The key is already cached inside the wallet software for normal operation; the patch simply exposes it through the existing `viewkey` command when the user asks. It does not appear to leak the key to anyone else or bypass hardware protections for the spend key.

Security candidatewallet2: validate key image domain in reserve proofsby selsta · b7817d08 · Aug 3, 2026 · 1 fileMessage 50 · ThinModerate 60Details
Commit message · selsta

wallet2: validate key image domain in reserve proofs

Reported by zkao, a tool by zkSecurity

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationprivacy or spend-authorization protocolsigning or wallet path
AI analysis · Moderate 60/100

This change adds a safety check when a Monero wallet verifies a 'reserve proof'—a document that supposedly proves someone owns enough funds without revealing which coins they are. The fix rejects reserve proofs that contain a mathematically invalid 'key image' (the special value zero, or a point outside the allowed cryptographic subgroup). Without this check, a maliciously crafted proof might trick the wallet into accepting or behaving unexpectedly on data that violates the protocol's assumptions.

Security candidatewallet_api: reject transaction file signing with hardware walletsby selsta · eeb82456 · Aug 3, 2026 · 1 fileMessage 50 · ThinLow 46Details
Commit message · selsta

wallet_api: reject transaction file signing with hardware wallets

Reported by zkao, a tool by zkSecurity

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 46/100

This change blocks a specific command—signing unsigned transaction files—from being used when a Monero wallet's private keys live on a hardware device (Ledger/Trezor). Before the patch, the software apparently allowed users to attempt this operation, which hardware wallets do not actually support. The patch now returns a clear error instead of proceeding. The risk is that a user or third-party tool could be misled into thinking a transaction was properly signed when it was not, potentially causing loss of funds or a failed/confused workflow. No exploit code is shown in the commit.

Security candidaterpc: hide sensitive txs from restricted block templatesby selsta · 8a393ed8 · Aug 3, 2026 · 8 filesMessage 50 · ThinModerate 63Details
Commit message · selsta

rpc: hide sensitive txs from restricted block templates

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

This Monero patch changes how block templates are built for restricted RPC users. Before, a remote user calling the get_block_template RPC on a restricted node could receive a block template containing sensitive transactions—specifically transactions that were relayed privately (such as Dandelion++ stem transactions). The patch adds a flag so restricted RPC callers get a template that only includes publicly broadcast transactions, while local/unrestricted callers still get the full template. This reduces information leakage about pending private transactions to untrusted RPC clients.

Security candidatecryptonote_protocol: avoid copying block span in add_blocksby jpk68 · e6d0d1e7 · Aug 2, 2026 · 1 fileMessage 50 · ThinInformational 16Details
Commit message · jpk68

cryptonote_protocol: avoid copying block span in add_blocks

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

This is a tiny performance tweak in Monero's network code. It changes one function call so that a batch of downloaded blocks is moved rather than copied into an internal queue. There is no security fix here and no indication it addresses a vulnerability.

Security candidatesimplewallet: use the swept account for index=all in sweep_mainby Cole Munz · e26eab8c · Aug 1, 2026 · 1 fileMessage 73 · AdequateLow 32Details
Commit message · Cole Munz

simplewallet: use the swept account for index=all in sweep_main

sweep_main() takes the account to sweep as a parameter, but the index=all
expansion still counts subaddresses on m_current_subaddress_account. sweep_all
and sweep_below pass the current account, so sweep_account is the one command
that ends up with the wrong set.

When the current account has fewer subaddresses than the account being swept,
the set is too small and outputs in the higher minor indices never make it into
the sweep. If none of the target's unlocked outputs land in that range,
create_transactions_all throws "No unlocked balance in the specified
subaddress(es)" for an account that plainly has a balance.

27d551d12f8d added the account parameter and pointed create_transactions_all at
it, but left this loop on the old field. The RPC path already does it the right
way, with get_num_subaddresses(req.account_index).

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
privacy or spend-authorization protocolsigning or wallet path
AI analysis · Low 32/100

This is a one-line bug fix in Monero's command-line wallet. The 'sweep_account' command, when asked to sweep all subaddresses of a different account than the one currently selected, accidentally looked at the wrong account's list of subaddresses. This could cause some funds to be left behind or the command to wrongly report that the target account had no spendable balance. It does not let an attacker steal funds; it is a user-facing functional bug that could surprise a wallet user.

Security candidatecryptonote_basic: keep additional derivations aligned in key image helperby Cole Munz · 5f767c6e · Aug 1, 2026 · 2 filesMessage 73 · AdequateHigh 76Details
Commit message · Cole Munz

cryptonote_basic: keep additional derivations aligned in key image helper

generate_key_image_helper only appended to additional_recv_derivations when
generate_key_derivation succeeded. A tx pubkey that is not a valid point makes
that call fail, so every later derivation shifted down one slot.

is_out_to_acc_precomp indexes that vector by the output index, so once the
list is short the lookup either falls off the bounds check or reads the
derivation belonging to a different output. Either way the helper reports that
the output does not belong to the address, and the wallet cannot build a key
image for an output it owns. Anyone who can put a transaction in front of the
wallet chooses those pubkeys.

The main tx pubkey a few lines up already handles a failed derivation by
keeping its slot and padding with identity, and wallet2 does the same in the
three places it builds this list (wallet2.cpp:2393, :7887, :13397). Do it here
too.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
privacy or spend-authorization protocolcryptography-sensitive path
AI analysis · High 76/100

This patch fixes a bug in how Monero wallets build key images for transaction outputs they own. When a transaction contained an invalid extra public key, the wallet would misalign its internal list of cryptographic derivations. This caused the wallet to either look at the wrong entry or fail to recognize its own output, preventing it from creating a key image. Because anyone can craft a transaction with such an invalid key, this could be used to stop a wallet from spending its own funds. The fix pads the failed derivation with a placeholder so the list stays aligned with output indexes.

Security candidatecryptonote_core: fully parse incoming block batchesby selsta · 967aa9f7 · Jul 30, 2026 · 1 fileMessage 50 · ThinLow 44Details
Commit message · selsta

cryptonote_core: fully parse incoming block batches

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

This change alters how Monero processes batches of incoming blocks. Previously, if any block in a batch was already known, the code would skip fully parsing the remaining blocks. Now it parses all blocks regardless. This could have hidden a bug where incomplete parsing led to inconsistent state, but the patch itself is small and the exact security impact is not stated by the vendor.

Security candidatecryptonote_protocol: avoid overlapping reserved spansby selsta · e59781ab · Jul 30, 2026 · 2 filesMessage 50 · ThinModerate 59Details
Commit message · selsta

cryptonote_protocol: avoid overlapping reserved spans

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

This commit fixes a bug in how Monero nodes request blocks from peers during blockchain synchronization. Before the fix, a node could accidentally reserve the same range of blocks twice from different peers, wasting bandwidth and potentially causing synchronization confusion. The fix adds a check to skip over any block ranges that are already reserved. A new test confirms the behavior.

Security candidatecryptonote_protocol: include pruned weights in sync sizingby selsta · f543a36d · Jul 29, 2026 · 10 filesMessage 50 · ThinLow 45Details
Commit message · selsta

cryptonote_protocol: include pruned weights in sync sizing

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

This Monero commit changes how a node calculates the size of upcoming block batches during sync. Previously, when a peer sent 'pruned' blocks (a compressed form), the node did not fully count those blocks toward its sync-size budget and only checked that their reported weight was non-zero. The patch makes the node use the pruned blocks' reported weights in its size calculations and verifies those weights against data already stored in its own chain. The main effect is to prevent a malicious or buggy peer from making the node request far more data than expected, which could slow or disrupt syncing. It is a hardening/DoS-mitigation change rather than a direct coin-theft bug.

Security candidatecryptonote_protocol: limit queued blocks dynamicallyby selsta · 89d8db06 · Jul 29, 2026 · 7 filesMessage 50 · ThinLow 38Details
Commit message · selsta

cryptonote_protocol: limit queued blocks dynamically

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

This Monero commit rewrites how the peer-to-peer block download queue is limited. Instead of capping the number of 'spans' (batches) of blocks, it now caps the total number of queued blocks based on the measured download speed and a user-configurable target time. The change also fixes a couple of small arithmetic edge cases, such as avoiding division by zero when measuring microseconds and guarding against invalid or infinite block rates. The commit message and diff do not describe any security bug; it reads as a performance and robustness improvement to sync behavior.

Security candidateremove translationsby tobtoht · 74e03c43 · Jul 28, 2026 · 26 filesMessage 18 · OpaqueInformational 15Details
Commit message · tobtoht

remove translations

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100

This commit removes the entire translation/internationalization system from the Monero command-line tools. It deletes translation files, build scripts, documentation, and the code that loaded and applied translated text. The remaining code now always displays English text. There is no security fix or vulnerability here; it is a feature-removal cleanup change.

Security candidatecryptonote_core: remove dead codeby Thomas · e7278c0a · Jul 28, 2026 · 7 filesMessage 58 · ThinInformational 15Details
Commit message · Thomas

cryptonote_core: remove dead code

Never had a caller:
- Blockchain::init taking HardFork*&: added in 8f863e742, no caller in
any revision since
- tx_memory_pool::get_txpool_weight, set_txpool_max_weight: added as
get_txpool_size and set_txpool_max_size in bc61ae69b alongside
--max-txpool-size, which is wired through tx_memory_pool::init
instead; renamed size to weight in 5ffb2ff9b, still uncalled
- get_transaction_version: added in b750fb27b, no caller since

Dead when their last user went:
- core::get_blocks taking vector<pair<blobdata, block>>, both overloads:
last caller removed in 9faef1f83; ed2c81ed9 later converted the
already-dead signatures from std::list to std::vector. The
vector<block> overload is still used by core_tests and is kept
- blocks_container: 9e82b694d removed the in-memory blockchain that
used it
- tx_by_fee_and_receive_time_entry: 445319d3f replaced the sorted
container it keyed with a boost::bimap
- m_store_blockchain_interval: its do_call went with the original
blockchain_storage format in 9e82b694d
- m_fork_moaner: its do_call went with the "We are most likely forked"
message in f0371210e

Also drops two break statements after a return in ver_mixed_rct_semantics
and the doc comments belonging to the removed declarations.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Why it was queued
signing boundarycryptography-sensitive path
AI analysis · Informational 15/100

This commit is a routine cleanup that removes unused functions, type aliases, and unreachable code from Monero's core blockchain and transaction-pool modules. The removed code had no callers, so the change cannot be used to attack the network or users. It is purely a maintenance refactor.

Security candidateringct: cleanup proveRctCLSAGSimpleby jeffro256 · 6620c2db · Jul 27, 2026 · 1360 filesMessage 50 · ThinInformational 15Details
Commit message · jeffro256

ringct: cleanup proveRctCLSAGSimple

1. Document parameters
2. Document inner variables
3. Remove dead variables
4. Remove unneseccary allocations

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Why it was queued
privacy or spend-authorization protocolcryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update pathauthentication pathparser or protocol path
AI analysis · Informational 15/100

This commit is titled as a cleanup of a single RingCT function (proveRctCLSAGSimple), but the supplied diff is actually a massive repository import/addition of 1,360 files (696,994 insertions) including the entire Monero codebase, build system, CI workflows, documentation, tests, and submodules. There is no actual code change to proveRctCLSAGSimple visible in the provided diff. No security-relevant change is present in the materials supplied.

Security candidatep2p: stop buffered dispatch after fatal notificationsby selsta · 1bae55ae · Jul 27, 2026 · 4 filesMessage 50 · ThinModerate 59Details
Commit message · selsta

p2p: stop buffered dispatch after fatal notifications

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

This patch changes how Monero's peer-to-peer networking layer handles bad or rejected messages. Previously, when a message handler decided to drop a peer, it often returned a generic success-like code (1) or a 'handler not defined' error. The patch makes these handlers return a specific connection error code, and makes the lower-level protocol stop processing further buffered messages from that peer when it sees a fatal error. This prevents a misbehaving or malicious peer from forcing the node to keep handling queued messages after the node has already decided to disconnect. The change also ensures notifications (one-way messages) return OK instead of a handler-not-defined error when a command is filtered, avoiding spurious errors.

Security candidatetxpool: fix time_in_pool age calculationby selsta · 265f7b28 · Jul 26, 2026 · 1 fileMessage 45 · ThinInformational 19Details
Commit message · selsta

txpool: fix time_in_pool age calculation

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

This commit fixes a simple arithmetic bug in how long a transaction has been waiting in the memory pool ("time in pool") was calculated. The old code subtracted the current time from the receive time in the wrong order, which could produce a very large, nonsensical age value instead of a small positive number. The fix ensures the age is always the current time minus the receive time, or zero if the clock somehow runs backward. This is a correctness fix for statistics/ranking of pending transactions, not a direct funds-theft or code-execution vulnerability.

Security candidatewallet2: check for overflow when calculating fee from weightby selsta · e2a4f68e · Jul 26, 2026 · 1 fileMessage 55 · ThinModerate 59Details
Commit message · selsta

wallet2: check for overflow when calculating fee from weight

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
memory safetysigning or wallet path
AI analysis · Moderate 59/100

This commit adds an overflow check when the Monero wallet calculates transaction fees from a transaction's weight. Before the patch, multiplying a large 'weight' value by a non-zero 'base_fee' could silently wrap around to a tiny number, potentially causing the wallet to propose an incorrect (possibly far too low) fee. The fix now throws an internal wallet error instead of silently producing a wrong result.

Security candidatedevice_trezor: improve error message for view key exportby jpk68 · 6e35278b · Jul 26, 2026 · 1 fileMessage 50 · ThinInformational 17Details
Commit message · jpk68

device_trezor: improve error message for view key export

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
privacy or spend-authorization protocol
AI analysis · Informational 17/100

This commit changes how Monero's Trezor hardware wallet integration handles one specific error. Previously, if a user cancelled the view-key export on their Trezor device, the code fell through to a generic 'Get secret keys exception' message and returned false. Now it immediately throws a clearer error: 'Key export rejected on device.' This is a user-experience and diagnostic improvement, not a fix for an exploitable security flaw.

Security candidateOptimize hashing of generic typesby SChernykh · 8b012e4d · Jul 24, 2026 · 4 filesMessage 60 · AdequateLow 45Details
Commit message · SChernykh

Optimize hashing of generic types

Use a proper hash function instead of f(x)=x to achieve better distribution of hash values

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

This commit changes how Monero hashes certain internal data types. Previously, some types were hashed using a simple identity function that directly used raw bytes as the hash value, which can cause many items to land in the same hash-table bucket and potentially leak information through timing or collision patterns. The patch replaces that with SipHash-2-4, a keyed, cryptographically designed hash function, using a secret random key generated at startup. This is a defensive hardening change; the commit message frames it only as a performance/distribution optimization, not as a security fix.

Security candidatecrypto: add x25519 wrapper APIby jeffro256 · 6b86d333 · Jul 24, 2026 · 6 filesMessage 45 · ThinInformational 12Details
Commit message · jeffro256

crypto: add x25519 wrapper API

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

This commit adds a new internal cryptography helper for X25519 curve operations in Monero. It does not change existing wallet, network, or consensus logic. There is no indication in the commit or supplied references that this fixes or introduces a security vulnerability; it appears to be a routine feature addition with tests.

Security candidatecrypto: add FCMP++ generators T, U, & Vby jeffro256 · 9696cae5 · Jul 23, 2026 · 2 filesMessage 76 · AdequateInformational 15Details
Commit message · jeffro256

crypto: add FCMP++ generators T, U, & V

Sources in FCMP++ repo:
- T: https://github.com/monero-oxide/monero-oxide/blob/0e438aed2cce5c0ab8a935916c1a89bb0077f97f/monero-oxide/ed25519/src/compressed_point.rs#L76-L79
- U: https://github.com/monero-oxide/monero-oxide/blob/0e438aed2cce5c0ab8a935916c1a89bb0077f97f/monero-oxide/ringct/fcmp%2B%2B/generators/src/lib.rs#L16-L18
- V: https://github.com/monero-oxide/monero-oxide/blob/0e438aed2cce5c0ab8a935916c1a89bb0077f97f/monero-oxide/ringct/fcmp%2B%2B/generators/src/lib.rs#L20-L22

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
privacy or spend-authorization protocolcryptography-sensitive path
AI analysis · Informational 15/100

This commit adds three new cryptographic generator points (named T, U, and V) to Monero's code. These are special numbers used in a new privacy feature called FCMP++. The commit also adds helper functions to recreate and access these generators. There is no indication of a security bug or vulnerability in this change; it is a straightforward addition of constants needed for future protocol work.

Security candidatecrypto: add Ed25519->X25519 conversion functionsby jeffro256 · 6c395945 · Jul 22, 2026 · 2 filesMessage 60 · AdequateInformational 18Details
Commit message · jeffro256

crypto: add Ed25519->X25519 conversion functions

Reviewed-by: koe <ukoe@protonmail.com>
Reviewed-by: j-berman <justinberman@protonmail.com>

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 18/100

This commit adds two new math helper functions that convert points between two related elliptic-curve formats used in cryptography (Ed25519 and X25519). It is a pure addition of utility code; there is no bug fix, no change to existing behavior, and no indication it addresses a security flaw. The code includes a safety check that rejects the special 'identity' (zero) point, which is a sensible defensive measure.