Monero

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.

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.