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
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedMerge pull request #11587by tobtoht · c17c0fdc · Nov 2, 2026 · 1 fileMessage 58 · ThinModerate 60Details
Commit message · tobtoht
Merge pull request #11587
9805a82 simplewallet: clear recovery seed arguments after parsing (Samy)
ACKs: 0xFFFC0000*, jpk68, selsta
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 60/100
This update changes the Monero command-line wallet so that when a user types their secret recovery seed directly on the command line, the wallet now tries to erase that seed from the program's argument list in memory right after reading it. Before this change, the seed could sit in memory and also be visible to other users on the same machine through process listings or shell history. The change also adds a warning in the help text that command-line seeds may appear in process listings or shell history.
36b87ef p2p: restore safe DB sync after public peer disconnects (Samy)
ACKs: selsta, thomasbuilds, jpk68
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Moderate 51/100
This patch changes how Monero nodes decide when to switch back to a slower, safer database synchronization mode after a peer disconnects. Previously, the node could leave fast sync mode based on the highest reported blockchain height from any remaining peer, including peers on anonymous networks like Tor or I2P. Now, the node only uses publicly reachable peers to decide whether to re-enable safe sync. This reduces the chance that a single anonymous peer can trick a node into staying in fast sync, which could theoretically make certain denial-of-service or chain-manipulation attacks easier.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationcryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Moderate 59/100
This Monero update tightens how a node checks another node's claims about being fully synced. Previously, a peer could trick a node into thinking it was synchronized by simply claiming a high block height. The patch now verifies that the peer's claimed top block actually matches the local node's known blockchain tip, and rejects absurdly large height values. This reduces the risk of a malicious or buggy peer prematurely ending a node's initial sync, which could leave the node on a stale or forked view of the network.
This is a large feature merge for Monero that adds database support for FCMP++ (Full Chain Membership Proof++) curve trees. It changes how outputs are indexed, adds new database tables, and includes a migration from database version 5 to 7. The changes are primarily structural and preparatory for a future privacy upgrade, not a finished activated protocol change. The code is gated behind a compile-time flag ENABLE_FCMP_INTEGRATION that is off by default.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
AI review queuedwallet_rpc_server: reopen log file on `SIGUSR1`by Samy · 01dfcd6d · Nov 1, 2026 · 2 filesMessage 45 · ThinInformational 18Details
Commit message · Samy
wallet_rpc_server: reopen log file on `SIGUSR1`
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This change adds a feature to the Monero wallet RPC server that lets administrators rotate log files on Unix-like systems by sending a SIGUSR1 signal. It mirrors an existing log-rotation capability already present in the main Monero daemon. There is no indication in the commit that this fixes a security vulnerability; it is a usability/operational improvement.
AI review queuedMerge pull request #11396by tobtoht · 3fd0f88c · Oct 25, 2026 · 4 filesMessage 58 · ThinInformational 19Details
Commit message · tobtoht
Merge pull request #11396
bcd1791 wallet: batch account balances for RPC (Samy)
ACKs: selsta, jpk68
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit refactors how the Monero wallet RPC server reports account balances. Instead of asking the wallet one account at a time for its balance, it adds a new internal batching helper that scans all relevant transactions once and returns balances for all requested accounts. The change is accompanied by unit tests that verify the new batch result matches the old per-account result. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a performance and consistency improvement.
561e6a8 wallet2: accept omitted key images when already synchronized (selsta)
ACKs: jpk68, jeffro256, UkoeHB
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
privacy or spend-authorization protocolsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 32/100
This change lets a Monero wallet accept signed transaction files even when the file does not include the usual list of key images, as long as the wallet already knows those key images itself. It is a usability fix for stateless or offline signers, not a clear security bug fix. The patch adds checks to make sure the wallet really does know the key images before it proceeds, so it appears defensive rather than dangerous.
a52a889 cryptonote_protocol: validate known top height (Samy)
ACKs: jpk68, selsta, thomasbuilds
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationcryptography-sensitive pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Moderate 61/100
This Monero update tightens how a node checks a peer's claim about its copy of the blockchain. Before, a node would trust a peer if it simply recognized the peer's 'top block' hash, even if the peer lied about the block height. Now, for public internet peers, the node verifies that the claimed height actually matches the known block. If the height is wrong, the peer is penalized and disconnected. This prevents a type of network-level misinformation where a malicious or buggy peer could make others believe the chain is taller or shorter than it really is.
This patch fixes how Monero's blockchain code builds empty 'block templates' when a miner or pool explicitly asks for a template based on the current chain tip. Before the fix, the code used a rough estimate of block weight instead of the accurate current median, which could produce templates that don't match the real main-chain rules. The mismatch could let a miner create a block that other nodes reject, or cause inconsistent rewards/fees between normal and explicit tip templates. A new test confirms that explicit-tip templates now behave identically to normal ones.
AI review queuedMerge pull request #10866by tobtoht · 76d425f8 · Oct 25, 2026 · 6 filesMessage 58 · ThinLow 47Details
Commit message · tobtoht
Merge pull request #10866
8e3b4b7 mnemonics: decode seeds with explicit language (Samy)
ACKs: thomasbuilds, jpk68, selsta
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 47/100
This Monero update lets wallet software decode a recovery seed using a specific language the user provides, rather than always guessing the language automatically. Some words exist in multiple language word lists, so the same seed phrase can produce different wallets depending on which language is used. The change is meant to prevent users from accidentally restoring the wrong wallet when their seed is valid in more than one language. It also lets the wallet RPC server try alternative languages when verifying a seed against an existing wallet.
074909c ringct: fix use-after-free of thread results in rct verification (jpk68)
ACKs: Ap4sh, selsta
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationprivacy or spend-authorization protocolmerge-commit duplicate discount
AI analysis · Moderate 63/100
This patch fixes a use-after-free bug in Monero's ring signature verification code. The bug occurred because a local results container was declared after the thread pool waiter object. In C++, local objects are destroyed in reverse order of creation, so the waiter (which waits for worker threads to finish) was being destroyed before the results container. If a worker thread still accessed the results container after the waiter was gone, it could read or write freed memory. The fix simply moves the results container to be declared before the waiter, ensuring it is destroyed after all threads are done with it. This is a memory-safety and potential correctness issue in transaction verification, but the patch is small and the practical exploit path is uncertain.
bcdd241 zmq: fix overflow in get_output_histogram recent_cutoff check (jpk68)
ACKs: Ap4sh, selsta
63/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
memory safetymerge-commit duplicate discount
AI analysis · Moderate 50/100
This patch fixes a time comparison bug in Monero's restricted RPC daemon. The old code constructed a clock time point from a user-supplied number of seconds, which could overflow or produce a wildly wrong date. It then compared that date to 'now' to decide whether the requested histogram cutoff was too old. The new code converts 'now' to a plain second count, subtracts the allowed restricted window, and compares the resulting boundary directly against the user's value. This avoids constructing a time point from untrusted input and makes the age check more reliable. The practical security effect is likely limited because the call is only relevant on restricted RPC endpoints and the worst outcome appears to be an incorrect rejection or acceptance of a histogram request, not direct loss of funds or remote code execution.
AI review queuedMerge pull request #11573by tobtoht · 36946ea9 · Oct 24, 2026 · 1 fileMessage 58 · ThinLow 32Details
Commit message · tobtoht
Merge pull request #11573
0006899 simplewallet: serialize account, address and output commands with refresh (Samy)
ACKs: jpk68, selsta
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 32/100
This Monero wallet command-line patch adds or moves idle locks around several account, address, and output commands. The goal appears to be preventing the wallet's background refresh thread from running at the same time as these commands, which could otherwise read or modify wallet state while it is being updated. The commit message frames it as serialization with refresh, not as a security fix. There is no direct evidence in the diff of an exploitable vulnerability, crash, or incorrect balance/address result, but missing or misplaced locks are a classic source of race-condition bugs.
AI review queuedMerge pull request #11572by tobtoht · fbc36ef8 · Oct 24, 2026 · 2 filesMessage 58 · ThinModerate 57Details
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 57/100
This patch fixes how Monero validates the number of participants in a multisig wallet. It replaces hand-rolled math for counting combinations with a safer library function and corrects a check that was looking at the wrong variable (threshold instead of total). The old code could allow invalid or oversized multisig setups, which might cause wallet creation failures or incorrect multisig behavior.
AI review queuedMerge pull request #11565by tobtoht · ffdb8a73 · Oct 24, 2026 · 2 filesMessage 58 · ThinModerate 59Details
Commit message · tobtoht
Merge pull request #11565
b0d90b7 wallet2: bind incoming transaction proofs to recipient outputs (selsta)
ACKs: jpk68, UkoeHB
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 59/100
This Monero wallet code change refactors how transaction proofs are generated. Previously, incoming transaction proofs could be linked to outputs that were not actually destined for the recipient. The patch binds each proof to only the specific recipient output(s), and replaces shared secrets with random values when no matching output exists. This appears to fix a privacy weakness where a proof might incorrectly or over-broadly demonstrate receipt of funds.
da38ceb wallet2: require an output match before decrypting payment IDs (selsta)
ACKs: jpk68, UkoeHB
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
privacy or spend-authorization protocolsigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 63/100
This change tightens when a Monero wallet tries to decrypt a short encrypted payment ID. Previously, the wallet would attempt decryption even when the transaction outputs were received via an additional (non-main) transaction public key. Now it only decrypts the payment ID when at least one output was received using the main transaction public key. This prevents a wallet from incorrectly associating a payment ID with a transaction that was not actually intended for the main address, which could lead to misattribution of payments or privacy issues.
AI review queuedMerge pull request #11563by tobtoht · d622e631 · Oct 24, 2026 · 2 filesMessage 58 · ThinInformational 23Details
Commit message · tobtoht
Merge pull request #11563
c3a3aec wallet: use tail subsidy for suggested confirmations (selsta)
ACKs: Ap4sh, jpk68
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 23/100
This commit changes how Monero wallets estimate how many confirmations a transaction should have before it is considered safe. Previously, the wallet used the actual reward from the most recent block, which can vary. Now it uses a fixed long-term reference reward. This makes the suggested confirmation count more stable and predictable, and removes the need for the wallet to query the latest block reward. It is a correctness/usability fix rather than a direct security patch, though bad confirmation advice could theoretically lead users to trust a transaction before it is fully settled.
e7a1a23 daemon: reopen log file on `SIGUSR1` (Samy)
ACKs: jpk68, selsta
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
AI review queuedMerge pull request #11557by tobtoht · c3ab634a · Oct 24, 2026 · 2 filesMessage 58 · ThinModerate 54Details
Commit message · tobtoht
Merge pull request #11557
00aad61 wallet: relock keys before multisig save (Samy)
ACKs: jpk68, selsta
58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 54/100
This patch fixes a bug in Monero's multisig wallet setup. Previously, when exchanging multisig key data, the wallet would sometimes save its keys file while the keys were still temporarily decrypted. The fix ensures the keys are re-locked before writing the wallet file. A new test confirms a wallet can be safely saved and reloaded during an intermediate multisig exchange step.
AI review queuedMerge pull request #11551by tobtoht · 25d4adc9 · Oct 24, 2026 · 5 filesMessage 68 · AdequateModerate 62Details
Commit message · tobtoht
Merge pull request #11551
0467659 wallet: use parsed daemon host for proxy verification (Samy)
ACKs: jpk68, selsta
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationsigning or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 62/100
This Monero wallet update fixes how the wallet checks whether a daemon address is a special privacy-protected .onion or .i2p address when using a proxy or SSL. Before the fix, the wallet could be tricked by unusual addresses containing spaces, tabs, null characters, or IPv6 scope symbols into thinking an ordinary internet address was a trusted .onion/.i2p address, which would let it skip required SSL certificate checks. That could allow a malicious daemon to impersonate a trusted node and potentially spy on or manipulate wallet traffic. The patch now properly parses the URL and rejects suspicious characters before deciding whether strong verification is needed.
✓ Descriptive subject✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy pathmerge-commit duplicate discount
AI analysis · Informational 11/100
This commit only updates a submodule pointer for an external dependency called 'polyseed' from one commit hash to another. The actual code changes are not visible in this diff because submodules only store a reference to another repository's commit. There is no information in the commit message or diff indicating what changed inside polyseed or whether any of those changes relate to security.
AI review queuedMerge pull request #11548by tobtoht · 11dc667e · Oct 24, 2026 · 2 filesMessage 68 · AdequateInformational 15Details
Commit message · tobtoht
Merge pull request #11548
4746009 tests: fix compiler warning about dangling-else (SNeedlewoods)
ACKs: jpk68, jeffro256
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit fixes two compiler warnings about 'dangling else' statements in test code. It adds curly braces so that the intended code is clearly grouped with the 'if' statement. There is no change to the actual behavior of the tests or the Monero software, and no security issue is present.