Monero

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.