Monero

This commit changes one line in Monero's RPC server so that the get_alt_blocks_hashes endpoint is no longer available when the node is running in restricted mode. Previously, any caller could ask a restricted node for the list of alternative (orphaned/uncles) block hashes. The change suggests the developers decided this information should be treated as privileged, but the commit message does not explain why.

This commit fixes a minor logging bug in the Monero peer-to-peer protocol code. The previous code accidentally added a number to a character (using '+' instead of '<<'), which produced incorrect characters in a debug peer-overview string. The fix simply prints the number and character separately. There is no security impact.

This commit removes two old command-line debug options, --test-drop-download and --test-drop-download-height, that were added in 2015 to help developers manually test network behavior by discarding downloaded blocks. The commit deletes the option definitions, the code that read them, the code that skipped block processing when they were set, and related shell-completion hints. There is no security fix here; it is a cleanup of unused debugging flags.

This commit is a large repository initialization or merge that adds the entire Monero codebase plus build/CI files. The stated purpose is to speed up the blockchain export tool by reading the database more efficiently. There is no indication in the commit message or the visible changes that this is a security fix or introduces a security vulnerability.

This commit is a large-scale spelling and typo correction across comments, documentation, and a few string literals. It changes no program logic, no function behavior, and no executable code paths. There is no security relevance.

This commit fixes a bug in the Monero wallet's RPC 'describe transfer' feature. Previously, the code used the wrong index (real_output_in_tx_index) to look up the real ring member in the list of possible transaction sources. The fix uses the correct index (real_output). This could have caused the RPC response to report the wrong global index and public key for the real source of funds, potentially misleading wallet users or downstream tools that rely on this data.

This commit updates the RapidJSON submodule used by Monero and adds a Windows-specific workaround in the Trezor hardware wallet transport code. The workaround undefines the Windows macro 'GetObject' before including RapidJSON headers, because that macro conflicts with a RapidJSON method name. This is a compatibility fix for a known upstream issue, not a direct security patch. It likely prevents build or runtime problems on Windows when communicating with Trezor devices, but the commit itself does not describe any vulnerability or exploit.

This commit removes the 'output blackballing' feature from the Monero wallet software. Blackballing let users mark certain blockchain outputs as 'spent' so their own wallet would avoid picking them as decoys in ring signatures. The change deletes the supporting utility, the wallet commands, the API methods, and the database table used to store these marks. It is a feature-removal cleanup, not a fix for an active security vulnerability in the code itself.

This commit fixes a bookkeeping bug in the Monero wallet's key-unlock mechanism. Previously, if a user entered the wrong password while trying to decrypt wallet keys, the internal counter that tracks active unlockers was increased but never decreased. That left the wallet thinking it was still unlocked even though the keys had not actually been decrypted. The fix rolls back the counter and removes the wallet's entry from the tracking map when decryption fails. The included test confirms that after a failed unlock attempt, a later correct password still works and keys remain properly locked in between.

This commit is titled as a fix for the blockchain database's 'remove_block' function, specifically that the cursor should be set before deletion. However, the actual supplied diff is enormous (665,233 added lines across 1,321 files) and appears to be a full repository import or merge rather than a focused patch. The specific code change described in the title cannot be verified from the provided diff because the relevant file (src/blockchain_db/lmdb/db_lmdb.cpp) is not shown in the diff excerpt. The security relevance is therefore uncertain based only on the materials given.

This commit updates a bundled external component called RandomX from one version to another (v1.2.2). The actual code changes are not visible because the diff was not provided, and no verified references were supplied. Without seeing what changed, it is impossible to tell whether this update fixes a security problem, fixes a regular bug, or just refreshes the dependency.

This commit updates the wallet's method for estimating the current blockchain height. Previously, the wallet used a fixed old hard-fork point and a fixed rollback adjustment. Now it uses the latest hard-fork data and updated rollback figures. The change is primarily about keeping the estimate accurate as the network evolves. It is not a direct fix for a code execution or theft vulnerability, but an inaccurate estimate could in theory affect wallet behavior such as when it considers itself synced or which outputs it scans.

This commit changes how Monero stores and loads a list of sensitive multisignature wallet keys. Previously, the code used a generic 'copy the raw bytes' path for a container of secret keys. That generic path could leave copies of secret key bytes in temporary memory or use a copy method not safe for non-trivial types. The patch forces the keys to be converted through an explicitly cleared intermediate type and adds a compile-time guard so the generic blob-copy helper can only be used on simple, safe types. In short: it reduces the chance that secret key material leaks or gets mishandled during wallet serialization.

This commit swaps the two arguments in two calloc() calls so they follow the conventional order (number of elements first, then element size). On standard platforms this produces identical memory allocation results and does not change program behavior or fix any security bug. It only silences compiler warnings.

This commit is a large but straightforward code reorganization. It moves wallet data structures (such as transaction records, address book entries, and settings enums) out of the giant wallet2 module into a new smaller library called wallet2_basic. The existing wallet2 code now references these shared types instead of defining them itself. There is no user-facing behavior change, no new feature, and no obvious security fix or vulnerability introduced in the visible diff.

This commit fixes a privacy gap in Monero's restricted ZeroMQ RPC mode. Before the patch, someone using the --restricted-zmq-rpc option could still see exact times when transactions arrived and were last relayed through the get_transaction_pool ZMQ call. The HTTP restricted mode already hid those timing details, but the ZMQ path did not. The patch adds the same on/off privacy filter to the ZMQ path so restricted callers now get zeroed-out timestamps, matching restricted HTTP behavior. Timing metadata can help an observer deanonymize or trace transactions, so this is a privacy hardening fix.

This commit adds a safety check to a Monero wallet command called rescan_spent. Previously, the command could be run even when the wallet was connected to a daemon it did not trust. The fix now refuses to run the command unless the daemon is marked as trusted. This matters because an untrusted daemon could potentially lie about which coins have been spent, which may confuse the wallet's balance or, in the worst case, be used to manipulate transaction creation.

This commit removes a Windows-only debug assertion helper called LOCAL_ASSERT that was effectively dead code. It does not change how the software handles errors in normal builds, and it does not introduce a security vulnerability.

This commit is a build-system cleanup. It changes how the Monero software finds and links the Unbound DNS library during compilation, switching to a more standard CMake method. There is no direct evidence in the commit that it fixes a security vulnerability in running Monero software.

This commit is a routine build-system cleanup. It removes the Boost Chrono library from the link lists of components that don't actually use it, and adds it to the one component that does. There is no change to program logic, no bug fix, and no security relevance visible in the diff.

This is a code-quality refactor, not a security fix. It replaces an older, heavier C++ scope-cleanup helper with a lighter, modern one. The change touches several parts of the program but does not add or remove any security behavior; it only changes how cleanup actions are expressed internally.

This change makes Monero's HTTP digest authentication code handle failures in the MD5 hashing functions more gracefully. Previously, if OpenSSL's MD5 operations failed (for example, because MD5 was disabled in the cryptographic library), the code would silently continue with invalid or empty hash values, potentially allowing authentication to proceed incorrectly. Now the code checks each hashing step and aborts the authentication attempt cleanly if MD5 cannot be computed.

This is a routine code modernization change. It replaces an older, deprecated Boost networking function called strand.wrap with the newer equivalent bind_executor in two files. There is no indication this fixes a security bug; it simply keeps the code compatible with newer versions of the Boost library.

This commit fixes a thread resource leak in Monero's cryptography code. Previously, a helper macro called CTHR_THREAD_CLOSE was defined as doing nothing, meaning threads were created and joined but never properly detached. On systems using POSIX threads (pthreads), this can leave thread resources unreleased, causing gradual memory use growth. The fix makes CTHR_THREAD_CLOSE call pthread_detach, which tells the system it can clean up the thread after it finishes. This is a reliability and resource-management fix rather than a direct remote exploit, but resource exhaustion can sometimes affect service availability.

This Monero patch fixes a RingCT amount-decoding function that previously ignored extra bytes beyond the first 8 in a 32-byte amount field. A pre-v10 'long amount' transaction could hide non-zero padding after the real amount. The receiver's wallet would fail to decode it, but a third-party wallet checking a proof might accept it, creating a mismatch between what the sender proves and what the recipient can actually spend. The change makes the decoder reject such malformed amounts.