Monero

This commit fixes a bug in Monero's wallet RPC server where the rescan_blockchain command was not passing through a new keep_key_images option. A hard rescan normally destroys key images (the proof that a coin has already been spent), so the patch also blocks the contradictory combination of a hard rescan while trying to preserve key images. The change is mostly a missing-parameter fix, but mishandling key images could in theory affect wallet balance accuracy or spendability.

This commit changes Monero's CI testing workflow to optionally reduce the number of slow-hash iterations during automated pull-request tests, so the tests run faster. It does not change the real Monero mining or transaction verification code used by ordinary nodes or wallets. The production default of about 1 million iterations stays the same unless someone explicitly compiles with a special override flag. The main risk is accidental: if a binary were built with the reduced iteration count and used in production, the proof-of-work would be much weaker. But the commit only applies the override inside GitHub's test runners for pull requests.

This commit updates the Fish shell auto-completion scripts for Monero command-line tools. It changes the suggested file extensions for SSL private keys and certificates from .pem to .key and .crt respectively. This is a cosmetic/usability improvement for tab-completion only and does not change how the actual software handles SSL files or introduce any security vulnerability.

This commit is a routine code cleanup: it removes a duplicate copy of a helper function that converts a number of seconds into a human-readable phrase like '5 minutes' or '2 days', and makes the wallet use a shared version already present elsewhere. There is no change to security-sensitive logic, no bug fix, and no vulnerability.

This commit changes a single English sentence in a user prompt. It rewords 'Are you sure to overwrite it?' to 'Are you sure you want to overwrite it?' There is no functional, security, or behavioral change to the wallet software.

This commit replaces older, compiler-specific thread-local storage keywords (__thread) with standard C/C++ ones (thread_local and _Thread_local). It is a portability and standards-compliance cleanup. There is no direct evidence in the commit that this fixes an exploitable security vulnerability.

This commit simply deletes 33 translation files that contained no actual translations—only English placeholder text. It is a cleanup change with no security relevance.

This small patch fixes a wallet function that estimates the current blockchain height by looking at known past 'fork' events. Before the fix, if a fork was scheduled in the future, the code only added blocks when time had already passed the fork, but did nothing sensible when the fork was still ahead. The new code subtracts the remaining time from the estimate, and returns 0 with an error log if the calculation would go negative. This prevents the wallet from producing a nonsensical or underflowing height estimate, which could affect transaction creation, fee calculations, or lock-time checks.

This commit is a routine code cleanup: it moves some serialization declarations out of a core cryptographic header file into a new dedicated header. There is no indication this fixes a security bug or changes how data is actually processed; it only reorganizes where certain type definitions live to make the codebase easier to maintain.

This commit removes the entire 'pay-to-use RPC' feature from the Monero node software. Previously, node operators could optionally require remote users to do small proof-of-work payments (or mining shares) before serving RPC requests. The patch deletes the payment logic, command-line options, RPC commands, tests, and shell completions. It is a feature-removal cleanup, not a fix for an active vulnerability, and it makes RPC access free again on nodes that had not separately restricted it.

This commit simply removes an unused dependency called 'psutil' from the Monero test suite. It updates documentation and build checks to no longer require psutil, and deletes a helper function that reported available RAM during a mining test. There is no indication this fixes or introduces a security issue.

This commit simply deletes an unused experimental utility for building cryptographic transcripts (data-to-be-hashed) in the Seraphis crypto work area. It removes the source files, the CMake build target, and test-suite links. There is no runtime code change, no bug fix, and no security patch.

This commit only fixes the formatting of copyright comments across many source files. It removes blank lines between the copyright line and the license text, adds missing copyright lines, fixes minor whitespace issues, and removes an unused debug macro. There are no changes to program logic, security behavior, or functionality.

This patch fixes a corner case in Monero's wallet refresh logic. When scanning a coinbase (miner) transaction with no outputs, the wallet could previously call an internal output-generation helper with zero outputs, which may cause an error or undefined behavior during refresh. The fix skips that work when there are no outputs. It is a defensive hardening change rather than a clear exploit path for stealing funds.

This patch fixes the way Monero's network code reads incoming message headers. Previously, the code directly cast raw byte buffers to structured header types, which can crash or behave incorrectly on some processors when the memory address is not properly aligned. The fix copies the bytes into a properly aligned variable first using memcpy. This is a robustness/correctness fix that may prevent denial-of-service crashes from malformed or specially positioned network data, but the commit message does not frame it as a security vulnerability.

This commit refactors how some Monero ZeroMQ publication messages are serialized to JSON. It introduces a new internal JSON writer library and switches a few ZMQ-PUB message types over to it. The change is primarily a code cleanup and modernization; it does not appear to fix a known security bug or introduce an obvious new vulnerability. One small improvement is that serialization errors are now checked and logged instead of silently producing malformed output.

This Monero code change fixes how the transaction memory pool tracks 'sensitive' transactions—those that have not yet been publicly broadcast, such as Dandelion++ stem-phase transactions. Previously, incremental RPC queries could leak these sensitive transactions to clients that should not see them. The patch adds a per-transaction 'sensitive' flag so that RPC responses can skip these transactions. This is a privacy/confidentiality fix, not a direct theft-of-funds bug.

This Monero update fixes a problem where the daemon's 'get blocks' RPC reply could grow too large and exceed network packet limits. The patch makes the mempool (pool of pending transactions) portion of the response respect a size budget, so it won't be added if the blocks part already fills most of the safe packet size. It also adds internal limits on how many transaction details and how much total transaction blob data are returned. The likely goal is to prevent oversized replies that could cause connection failures or denial-of-service issues for wallets and other nodes.

This commit fixes a cleanup oversight in the Monero wallet. When the wallet clears private user data during background synchronization, it now also clears 'additional transaction keys' (m_additional_tx_keys). Previously, these extra keys were left behind while other similar secrets were wiped. This could mean sensitive cryptographic material persists longer than intended, potentially increasing exposure if an attacker later accesses wallet memory or state. The change is small and defensive, matching how related secrets are already handled.

This is a routine test-code cleanup. The change swaps a third-party Python package called 'monotonic' for Python's built-in 'time.monotonic()' in the test suite. It does not touch the Monero wallet, daemon, consensus, cryptography, or network code, and it does not fix or introduce any security vulnerability.

This commit adds a safety check to the Monero wallet's remote-control interface (RPC server). The check prevents a specific operation—creating a cryptographic 'spend proof'—from running while the wallet is performing a background synchronization. Without this guard, the operation could potentially use incomplete or inconsistent wallet state, which might lead to incorrect proof results or unexpected behavior. The issue was reported by an independent contributor, ro1m.

This commit is a code cleanup: it moves existing multisig signer-selection logic out of the middle of a large transaction-building function into two smaller, named helper functions. The actual behavior appears unchanged. There is no indication this fixes a security bug or introduces a vulnerability.

This commit removes an unused RPC command called finalize_multisig from the Monero wallet's remote-control interface. The command previously did nothing except return an error. Removing it is a cleanup change, not a security fix.

This commit updates Monero's SSL certificate generation code to use newer OpenSSL 3.0 APIs instead of older, deprecated ones. It is primarily a compatibility and cleanup change: it replaces low-level RSA key creation with the modern EVP_RSA_gen function when OpenSSL 3.0+ is available, and removes an unused elliptic-curve certificate function. There is no direct security vulnerability being fixed here, but keeping up with current APIs reduces future maintenance risk and avoids deprecation warnings.

This is a routine code cleanup that adjusts which header files are included in a utility source file. It removes one unused include, replaces broad library includes with more specific ones, and reorganizes the include order. There is no indication this fixes a security vulnerability or changes program behavior.