Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
53/100 average clarity
22Strong · 80–100
158Adequate · 60–79
690Thin · 40–59
66Opaque · 0–39
14security candidates with opaque commit messaging
This commit only adds a new automated test tool (a fuzzer) for the Monero wallet. It does not change any production wallet, node, or consensus code. It cannot by itself introduce a vulnerability that affects real users, nor does it fix one…
This is a cleanup and refactoring patch for Monero's new FCMP++ (full-chain membership proof) database and transaction handling code. It renames a method, fixes typos and comments, tightens a constant name, adds a safety check that outputs…
Added runtime invariant check that locked outputs do not unlock below the default unlock blockRefactored transparent-amount commitment collection to reduce indirection and potential misuseClarified unlock-time semantics and coinbase detection in migration code
This commit is a cleanup and hardening patch following an earlier pull request. It adds a safety check to make sure outputs are not incorrectly treated as spendable before they should be, fixes several typos and variable-name issues, rewri…
Added invariant check that outputs unlock no earlier than the default unlock block before adding locked outputs to the databaseRefactored transparent-amount commitment collection to remove std::reference_wrapper indirection, reducing complexityCorrected constant-name typos in spendable-age calculations
This is a one-line fix in Monero's wallet software that adjusts how far ahead the wallet tries to 'skip' scanning after a blockchain reorganization (reorg). A reorg happens when the network briefly disagrees on the chain of blocks and then…
Incorrect scan resume height after blockchain reorgPotential missed transaction detectionBalance accuracy issue in wallet
This commit is a code cleanup that replaces the non-standard WIN32 preprocessor macro with the compiler-defined _WIN32 macro across 18 files. It does not change program logic or behavior; it only makes Windows-specific code detection more …
No functional code changes observedPreprocessor macro standardization onlyWindows-specific code paths remain identical in behavior
This commit only adds a new automated security test (a fuzzer) for Monero's wallet cache file parser. It does not change any production wallet code, fix a bug, or introduce a vulnerability. It is a testing-only addition intended to help fi…
Adds a fuzz target for wallet cache deserializationNo changes to production code pathsNo patch of a reported vulnerability
This Monero update adds a cache that remembers which transactions in the memory pool have already failed expensive input verification, so the node does not waste CPU re-checking the same bad transaction repeatedly. It is a performance and …
Adds caching of invalid input verification IDs to avoid repeated expensive ring signature verificationReduces CPU consumption for transactions that re-enter or remain in the mempool with unchanged invalid inputsCould mitigate a minor denial-of-service vector where a node repeatedly re-verifies a bad transaction
This patch changes how Monero's daemon calculates the total coinbase transaction sum (emission plus fees) for a range of blocks. Previously, the code called a general 'get_transactions' helper that could trigger a deadlock because it might…
Deadlock avoidance in consensus-related coinbase emission calculationChange from general transaction retrieval to direct, pruned database readAddition of functional test covering coinbase sum correctness
This change is a performance optimization for the Monero wallet's balance-reporting RPC. When a user asks for balances across many subaddresses, the code now pre-counts unspent outputs in one pass instead of re-scanning the entire transact…
This update adds a safety check in the Monero wallet's fast refresh process. Previously, if a malicious or buggy remote server told the wallet to start syncing from a block height beyond the wallet's known blockchain data, the wallet could…
Added bounds check on untrusted server-supplied start_height against local hash chain sizeDefensive hardening at wallet/daemon trust boundaryUnit test demonstrates rejection of out-of-bounds refresh request
This commit tightens filename validation in the Monero wallet's remote-control interface (RPC server). It now rejects wallet names that are just '.' or '..', contain a hidden null character, or contain path separators like '/' (and on Wind…
Path-traversal defense: blocks directory separators and parent-directory references in wallet filenamesNull-byte injection defense: rejects embedded NUL characters that could truncate or confuse downstream path handlingRPC input validation hardening in wallet_rpc_server
This Monero wallet update fixes a file-handling bug in the 'save wallet as' function. Previously, the code compared only the main wallet cache path and used a simple path check that could be fooled by symlinks or filenames ending in '.keys…
Path overlap / self-overwrite protection for wallet cache and keys filesSymlink and hardlink alias detection using boost::filesystem::equivalentRejection of ambiguous paths where .keys file and cache file could collide
This commit adds an optional, faster way to set up N-of-N Monero multisig wallets. Normally, all signers must complete a final verification round to prove they are active and have finished setup. The new 'fast non-interactive setup' skips …
New feature adds a non-default, opt-in fast setup path that intentionally weakens a liveness/verification guaranteeForce-update flag (force_update_use_with_caution) is used internally to bypass the normal post-KEX roundUser-facing and API documentation clearly warn that funds may become inaccessible if other signers do not complete setup
This change refactors how Monero's wallet fetches transaction data when creating or verifying 'spend proofs'—cryptographic receipts that prove you spent funds. Previously, spend-proof code fetched transactions directly from the network dae…
Refactoring of spend-proof transaction lookup to a single helperAddition of explicit RPC timeout parameter to transaction fetch helperImproved daemon RPC error/status reporting in get_tx_for_proof
This commit refactors how the Monero wallet fetches a transaction when verifying a payment proof (the check_tx_key feature). It replaces a direct daemon RPC call with a helper function called get_tx_for_proof, which is described in the com…
Replaces direct /gettransactions RPC with centralized helper for proof verificationCommit title explicitly frames change as 'verify v1 txid in check_tx_key'Removes local tx_hash == txid equality check in favor of helper-internal verification
This change stops a Monero wallet from creating 'InProofs' (receipt proofs) for transactions that the wallet itself sent. InProofs are meant to prove to someone else that you received money. If a wallet could generate an InProof for a tran…
Prevents generation of misleading InProofs for outgoing/self-sent transactionsAdds explicit runtime guard in wallet proof generation pathFunctional tests updated to assert refusal behavior
This patch fixes a bug in the Monero wallet where, if a pending transaction failed, the wallet could incorrectly mark coins as unspent even though they had already been spent by a separate confirmed transaction. This could let the wallet t…
Incorrect state reset on failure pathPotential double-spend attempt caused by stale UTXO selectionWallet balance/availability inconsistency after failed pending tx
This commit only adds a new automated fuzz-testing harness for Monero wallet features. It does not change any production wallet code, fix a bug, or alter network behavior. It is a test-only addition intended to help find bugs in the future…
Adds fuzz targets for payment URI parsing and transaction proof verificationNo changes to production wallet, consensus, or network codeNo bug fix or behavior change in existing source files
This Monero update fixes a bug in how nodes ask each other for blockchain history. Previously, a node could get stuck or drop a peer when it already knew about some blocks from another connection, because it would not ask for the next batc…
P2P protocol synchronization logic changePotential denial-of-service via peer dropping or sync stallNo authentication or cryptographic boundary crossed
This commit fixes a bug in how the Monero wallet saves itself to disk. Previously, the wallet could accidentally overwrite or corrupt its own files when the user chose a path that overlapped with existing wallet files, such as saving to a …
File overwrite / corruption prevention in wallet save path handlingSymlink and hardlink alias detection via filesystem equivalent() checksRejection of overlapping source/destination wallet files
This is a one-line build-system change that adds a missing library dependency ('wire') so another component can compile and link correctly. There is no indication it fixes a security vulnerability; it appears to be a routine build fix.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 47/100
This commit removes compiler directives that forced certain cryptographic data structures to be packed tightly without padding, and replaces some direct multi-byte memory reads with safer memcpy operations. On some processors, reading a multi-byte value from a memory address that is not aligned to that value's size can cause a crash or reduced performance. The change makes the code safer and more portable across different CPU architectures, but it does not appear to fix an exploitable remote vulnerability in the Monero network itself.
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 31/100
This commit fixes the way a Monero cryptographic function for ARMv8 processors describes its inline assembly code to the C compiler. Previously, the assembly block did not properly tell the compiler which memory and CPU registers it reads and writes. This can lead to subtle bugs where the compiler optimizes code incorrectly around the assembly, potentially causing wrong hash results or memory corruption on ARMv8 devices. The fix adds proper input/output constraints and a clobber list so the compiler knows exactly what the assembly touches.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationprivacy or spend-authorization protocol
AI analysis · Low 47/100
This commit adds a type check in Monero's JSON deserialization code. Before the fix, when reading a RingCT signature from JSON, the code assumed the 'prunable' field was a JSON object and accessed it directly. If someone supplied a non-object value (like a number or string), the code could read memory incorrectly or crash. The patch now throws a clear error if the type is wrong.
- Function to convert an {output pubkey, commitment} to an output tuple {O,I,C} in prepartion to insert the output tuple into the curve tree. - O = torsion cleared valid output pubkey checked for identity. - I = key image generator. - C = torsion cleared valid Commitment checked for identity. - None of {O,I,C} should have torsion nor == identity. - Introduces the OutputPair variant, which can either be Legacy or Carrot V1 types. Legacy outputs are not checked for torsion at consensus, and use the legacy biased hash to point fn to derive the key image generator (I). Carrot V1 outputs **are** checked for torsion at consensus, and use the unbiased hash to point to derive the key image generator (I).
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
consensus or confidential-proof validationprivacy or spend-authorization protocol
AI analysis · Informational 12/100
This commit adds new code for an upcoming Monero privacy feature called FCMP++. It creates a helper function that converts an output's public key and commitment into a special three-part tuple used by the new system. The commit is defensive in nature: it carefully clears mathematical 'torsion' from points, rejects identity points, and explicitly avoids a subtle double-spend risk that could occur if the wrong version of a key were used around a network upgrade. There is no indication this commit fixes an active bug or vulnerability; it appears to be a building block for future functionality.
Security candidatewallet: derive encrypted payment ID dummy/real status from tx.extra, not cd.destsby waris ) · afcfd976 · Jul 21, 2026 · 3 filesMessage 50 · ThinModerate 59Details
Commit message · waris )
wallet: derive encrypted payment ID dummy/real status from tx.extra, not cd.dests
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
privacy or spend-authorization protocolsigning or wallet path
AI analysis · Moderate 59/100
This Monero wallet patch changes how the wallet decides whether an encrypted payment ID is real or a dummy placeholder. Previously, the wallet relied on destination address data (cd.dests), which could be manipulated by a malicious signer or loaded transaction to make a real payment ID look fake, or a fake one look real. The patch now derives that status directly from the transaction's extra field, where the payment ID is actually stored, and adds a consistency check. This is a security fix for a potential information leak or user deception during multi-step transaction signing.
tests: tests_common library and gen_corpus executable
Adds two components to the tests directory: 1. `tests_common` a shared utility library for different types of tests 2. `gen_corpus` an executable to dynamically generate seed corpora for fuzzing during the build stage
Also updates the transaction fuzzing test to call `ver_non_input_consensus()` for different HF versions.
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidenceconsensus or confidential-proof validationcryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100
This commit adds new testing tools to Monero: a shared helper library for building test transactions and a build-time generator for fuzzing seed data. It also updates one fuzz test to exercise more transaction-validation code paths. There is no change to the live Monero network code, consensus rules, or wallet behavior—only test infrastructure.
Security candidatecryptonote_protocol: remove dead codeby Thomas · c2dc8a5b · Jul 20, 2026 · 4 filesMessage 58 · ThinInformational 15Details
Commit message · Thomas
cryptonote_protocol: remove dead code
block_queue: - print(): added with two debug call sites in the sync-speedup rewrite (5be43fcdb, 2017-07-02); 08abb670e (2017-08-12) removed one call and Pruning (b750fb27b, 2018-04-29) removed the last; dead since. - get_num_filled_spans_prefix(): added in 5be43fcdb (2017-07-02) without any caller; dead on arrival. - get_last_known_hash(): added in 5be43fcdb with one caller in the protocol handler; 08abb670e (2017-08-12) removed that caller while reworking reorg handling; dead since. - has_spans(): added in 7b7476075 (2017-08-16, kick idle synchronizing peers) without any caller; dead on arrival. - get_download_rate(): added by Pruning (b750fb27b, 2018-04-29) without any caller; dead on arrival. - has_unpruned_height(): declaration added by Pruning (b750fb27b); a definition never existed, so it was never callable.
cryptonote_protocol_handler: - get_synchronizing_connections_count(): from the original 2014 import (296ae46ed, 2014-03-03); its only reference was already commented out in the import, and 8efa1313f (2014-03-20) deleted that comment. Never had a live caller in the repo's history. - PASSIVE_PEER_KICK_TIME: added in 1ff638e92 (2017-10-19) with one use in the idle-peer kick threshold; Pruning (b750fb27b) removed the use, orphaning the macro. - LOCALHOST_INT: added in ae2a50659 (2015-02-20) for numeric localhost comparisons, second use added in c511abf00; 072102cfd (2017-05-27, abstracted network addresses) removed both uses.
cryptography-sensitive pathparser or protocol path
AI analysis · Informational 15/100
This commit simply deletes unused code from Monero's network synchronization module. It removes functions, macros, and declarations that were never called or had no definition. There is no change to active behavior, no bug fix, and no security-relevant change.
Security candidateringct: remove dead codeby Thomas · bf461566 · Jul 20, 2026 · 6 filesMessage 61 · AdequateInformational 15Details
Commit message · Thomas
ringct: remove dead code
- h2b, b2h (rctTypes) and sumKeys (rctOps): from the original RingCT import (9b1afe5f2, 2016-05-13); never referenced by any caller since the import. - cn_fast_hash128, hash_to_scalar128 (rctOps): from the same import. hash_to_scalar128 (and cn_fast_hash128 through it) was last used by the original MLSAG gen/ver hashing, which dbb5f2d6a (2016-07-09) replaced with keyV-based hash_to_scalar; dead since then. - bos_coster_heap_conv (multiexp): added in 9ff6e6a0a (2018-01-09) alongside bos_coster_heap_conv_robust; multiexp() only ever dispatched the robust variant, so the non-robust one was never called. The robust variant is kept, as tests/performance_tests still uses it (production dispatch moved to Straus/Pippenger in 939bc22/263431c).
61/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
privacy or spend-authorization protocol
AI analysis · Informational 15/100
This commit simply deletes unused functions and one unused inline helper from Monero's RingCT code. The removed code was never called by any part of the program, so the change cannot introduce or fix a security vulnerability on its own. It is a routine cleanup that reduces clutter and maintenance burden.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
proof-of-work or emission validationseed or entropy path
AI analysis · Informational 3/100
This commit updates the bundled RandomX library (used for Monero's mining proof-of-work) from one version to version 1.2.3. The actual code changes are not visible because the diff was not provided, and no security references were supplied. On its own, the commit message only says 'update to v1.2.3' and does not claim to fix any security issue.
general: replace auto_scope_leave_caller with scope_guard
And replace unused inclusions of misc_language.h
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathparser or protocol path
AI analysis · Informational 19/100
This is a large internal cleanup commit in the Monero codebase. It replaces an older scope-guard helper (auto_scope_leave_caller) with a newer, simpler scope_guard type, trims unused #include lines, and replaces a few value-initialization macros with direct C++ syntax. There is no direct evidence in the commit message or diff that this fixes a security vulnerability; it appears to be a refactoring and code-quality improvement. The changes touch many files but do not alter program logic in a way that is obviously exploitable.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100
This commit removes a custom hash comparison helper that was used to sort transaction hashes in the memory pool data structure. The code now relies on Boost's default comparison for the hash type. There is no visible security change: the removed comparator behaved the same as the standard less-than comparison for the hash data, and no behavior or interface changes are apparent.
crypto: derive key image generator & separate {un}biased hash to ec https://github.com/monero-project/research-lab/issues/142
Co-authored-by: Jeffro <jeffro256@tutanota.com> Co-authored-by: Luke Parker <lukeparker5132@gmail.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
privacy or spend-authorization protocolcryptography-sensitive path
AI analysis · Low 34/100
This commit adds new cryptographic routines to Monero and renames an existing one. It introduces a new way to derive 'key image generators' (used to prove a coin hasn't been spent twice) and a new 'unbiased' method for hashing data to an elliptic-curve point. The old method is now explicitly labeled 'biased' but remains in use for existing ring signatures. The changes are presented as a research-driven cryptographic improvement, not as a fix for an active bug or vulnerability.
/get_blocks.bin is HTTP binary RPC serialized with portable storage, not a P2P Levin message. The previously added pool limiter used LEVIN_DEFAULT_MAX_PACKET_SIZE as a response budget, but that constant does not apply to the RPC path.
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 · Low 49/100
This Monero code change fixes how the /get_blocks.bin RPC endpoint limits the size of transaction-pool data it returns. Previously, the code reused a P2P Levin packet-size constant that does not apply to HTTP RPC responses, and it tried to budget pool data against the size of the block data already sent. The patch removes that size-budget plumbing and instead caps the number of added pool transactions at a fixed maximum (20,000). This is a correctness fix for response-size limiting, but it also removes a cumulative byte-size cap that could, in edge cases, allow very large individual transactions to make responses bigger than intended.
Addresses several issues with miner block template:
1. Fixes key image conflict issue due to lazy transaction prefix - This line checks whether the next tx candiates has conflicting key images with the rest of the block template: https://github.com/monero-project/monero/blob/0f84863feda75574788e15c9691abecf57bc3f8f/src/cryptonote_core/tx_pool.cpp#L1744 - The function takes in a transaction prefix and parses the key images from it - However, the transaction may or may not actually ever be deserialized, depending on the state of `m_input_cache`: https://github.com/monero-project/monero/blob/0f84863feda75574788e15c9691abecf57bc3f8f/src/cryptonote_core/tx_pool.cpp#L1455-L1466 2. Deduplicates code between `tx_memory_pool::fill_block_template()` and `tx_memory_pool::get_block_template_backlog()`, and thus converging the backlog lists between the 2 functions 3. Saves time creating block templates by skipping transaction blob readings and deserializations for some txs 4. Stops template candidate search after block is reasonably full and we are iterating through txs which lower coinbase reward or exceed size limit by a "smallish" amount. Prevents us from unnecessarily reading thousands of useless tx metadatas under load. May help https://github.com/seraphis-migration/monero/issues/293 5. Fixes block templates when coinbase transactions are > 600 bytes 6. Fills closer to block weight limit for small coinbase transactions 7. Fixes "Invalidating block template cache" spam while popping blocks / during reorgs 8. More accurate "expected block reward" field in RPC
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
privacy or spend-authorization protocolproof-of-work or emission validationcryptography-sensitive path
AI analysis · Moderate 59/100
This Monero commit fixes a bug in how mining software picks transactions for the next block. The old code could accidentally include two transactions that spend the same 'key image' (like the same coin being spent twice), which would create an invalid block. It also cleans up and speeds up the transaction selection logic. The commit message explicitly calls this a 'key image conflict issue' and says it is fixed.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 46/100
This commit changes how Monero reads 64-bit chunks from cryptographic hashes during difficulty checks. Previously the code cast a byte array directly to a uint64_t pointer, which can violate strict aliasing rules and cause unaligned or misread memory on some platforms. The new code copies the bytes with memcpy first, then converts endianness. This is a correctness and portability fix; it likely prevents subtle consensus bugs where different nodes might interpret a hash's numeric value differently, but the commit itself does not describe any active security incident or exploit.
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100
This commit only changes two error log messages in Monero's blockchain code. It removes the phrase 'dropping connection' from messages that are printed when a peer sends an invalid chain request. The actual behavior—returning false and not dropping the connection—was already in place; the logs were simply inaccurate. There is no security fix here.
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive path
AI analysis · Low 29/100
This commit adds new cryptographic code to Monero that converts points on the Ed25519 curve into Weierstraß (short Weierstrass) form. It introduces helper functions, new curve constants, and unit tests, but does not appear to fix any known vulnerability. The change is a feature addition for the FCMP++ (Full Chain Membership Proofs) work. There is no direct evidence in the commit or supplied references that this patch addresses a security bug, but any new elliptic-curve conversion code carries implementation-risk that could affect correctness or side-channel resistance if used incorrectly.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 67/100
This commit adds a new cryptographic safety check for Monero's upcoming FCMP++ (Full Chain Membership Proof) system. It makes sure that certain elliptic-curve points used in transactions are free of small 'torsion' components—mathematical artifacts that can be exploited in some zero-knowledge proof attacks. The patch introduces helper functions to clear torsion and a new validation routine, plus tests. It does not by itself fix a known exploitable bug in live code; it is a defensive hardening measure for a feature that is still being integrated.
✓ 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 · Low 44/100
This commit fixes a bug in Monero's wallet software where exporting 'key images' (cryptographic proofs that help verify account balances without exposing private keys) could use an outdated cached value instead of the freshly generated correct one. The change ensures the wallet always exports the newly generated key image, and adds a test to confirm this behavior. If the wrong key image were exported, a wallet relying on it could fail to prove ownership of funds correctly, potentially causing accounting errors or denial of service in balance verification.
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.
✓ 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.
✓ 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.
✓ 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.
✓ 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.