monero-java

This commit updates the Java Monero wallet library so that exporting and importing signed key images now also carries an 'offset' value. The offset tells the wallet where the exported key images start among all the wallet's outputs. This is a feature/API alignment change rather than a clear security fix. There is no evidence in the commit message or diff that the author describes it as fixing a vulnerability, and no independent security references are provided.

This commit only updates generated Javadoc HTML documentation files. It does not change any source code, runtime behavior, or security logic. The visible differences are documentation additions for existing wallet API methods (such as trusted-daemon flags and key-image import/export) and regenerated index files. There is no security-relevant code change to assess.

This commit changes how a Monero wallet library requests data when signing transactions via RPC. It now explicitly asks the remote wallet to also return the raw transaction hex data and the transaction keys, matching behavior already present in the JNI wallet implementation. There is no direct evidence in the commit that this introduces a security vulnerability; it appears to be a parity/feature completeness change.

This commit adds a new option for users to explicitly tell a Monero wallet whether its connected daemon should be treated as 'trusted.' A trusted daemon can receive more sensitive data or perform more powerful operations than an untrusted one. The change is a feature addition that exposes an existing underlying wallet capability; it does not by itself create a vulnerability, but it makes it easier for users to accidentally or intentionally mark a remote daemon as trusted. That could increase the impact of other attacks if a user is tricked into trusting a malicious daemon.

This commit only changes a test file to fix a flaky test. The test was requesting a reserve proof for an amount slightly above a single account's balance, but the underlying Monero wallet validates against a stricter 'whole-wallet' balance that includes pending-spent outputs. Because unconfirmed transactions can make the strict balance higher than the reported account balance, the old test sometimes failed to trigger the expected error. The fix requests an amount above the whole-wallet balance instead. There is no change to production code, no security vulnerability, and no user-facing behavior change.

This commit only changes a test file. It updates how a Monero wallet test checks transaction destinations: instead of comparing each destination in the exact order it was sent, it now adds up the amounts sent to each address and compares the totals. This is a test-only adjustment to match how the upstream Monero software actually behaves, not a fix for a security problem in production code.

This commit changes one line in a test file. It fixes a test that checks sending Monero from multiple subaddresses in a single, unsplit transaction. Previously the test passed null (likely allowing default split behavior); now it explicitly disables transaction splitting. There is no change to production wallet code, no security fix, and no indication of a vulnerability.

This commit simply removes two comment lines in test code that said certain tests occasionally crashed on Apple Silicon Macs. No actual code behavior was changed, so it does not introduce or fix a security issue on its own. It only updates internal notes about previously observed test failures.

This commit fixes a bug where the wallet RPC component treated the same proxy address as different if one version included a scheme prefix like 'socks5://' and the other did not. Previously, this caused an unnecessary error when setting a daemon connection. The fix normalizes proxy URIs before comparing them, so equivalent addresses are recognized as the same. It is a usability and correctness fix rather than a clear-cut security vulnerability.