Monero GUI

This commit fixes a broken feature in the Monero wallet's setup wizard that restores a wallet by scanning a QR code. The feature had been completely non-functional since a prior redesign because the code that processes the scanned QR code was placed in a JavaScript library that cannot access the wizard's user-interface elements. The patch moves that code into the correct wizard page, updates it to use the current user-interface elements, and safely handles QR codes that contain only an address with no extra key data. This is a straightforward bug fix with no clear security relevance.

This commit adds automated user-interface tests for the Monero wallet setup wizard. It does not change how real users create or open wallets; it only adds test code and exposes a few internal UI control names so the tests can interact with wizard pages. There is no security fix or vulnerability here.

This commit changes the Monero GUI wallet creation wizard so that users always see and can edit the wallet save location, regardless of which wallet mode they chose. Previously, the location field was hidden in simpler modes and the wallet was saved to a default folder. The change also stops validating whether the default folder is writable, only checking custom locations. This is a user-experience and correctness fix rather than a clear security patch, though it removes a minor validation inconsistency.

This is a user-interface bug fix in the Monero wallet's Receive page. When a user switched between accounts, the page could show a label and QR code from one account while the displayed address belonged to another account, because the selected list row was not updated to match the new account. The fix makes sure the selected row and displayed address/label stay in sync. It is a consistency bug, not a cryptographic or network vulnerability.

This change alters the Monero GUI wallet setup wizard so that newly created or recovered wallets are kept only in memory, rather than being written to a temporary file on disk during the setup process. The old approach created temporary wallet files on the computer's storage and then deleted them after the user finished the wizard. The patch removes the code that created and cleaned up those temporary files. This is a defensive improvement: it reduces the chance that an unfinished or temporary wallet file containing sensitive data is left behind on disk, exposed to other users, recovered by forensic tools, or leaked through backups, swap files, or file indexing. The change also adds a small UI guard so the wizard cannot be interacted with while a hardware-device wallet is being created asynchronously.

This commit fixes a broken GitHub workflow script that verifies P2Pool software hashes. The script previously used the third-party 'requests' library, which is not installed on the slim Ubuntu runner used by the project. The change switches to Python's built-in 'urllib' library so the automated check can run again. It is a reliability/maintenance fix, not a security vulnerability patch.

This commit simply removes an unused Makefile variable called 'deldirs'. There is no change to compiled code, no security fix, and no user-facing behavior change.

This commit fixes a bug in the Monero GUI wallet where three functions that read transaction details could access memory beyond the bounds of an internal list when the list is empty. The old check used 'index > size - 1', which underflows when the list is empty (size 0), so the guard failed and the code could read from an invalid position. The new check 'index >= size' is safe even when the list is empty. This is a defensive fix that prevents a potential crash or reading of unintended data when the wallet processes an unsigned transaction with no outputs or fees recorded.

This commit fixes a precision-loss bug when the Monero GUI wallet passes payment amounts from the user interface (QML) to the underlying wallet code. Previously, amounts were converted too early from human-readable XMR strings into 64-bit integers, which could silently drop very small fractions of a Monero amount. The patch moves the conversion into the C++ backend where the wallet's own parsing function is used, preserving precision. This mainly affects QR-code/payment URIs and reserve proofs, not a remote exploit.

This commit is a large merge of pull request #4192 into the Monero GUI repository. The actual code change within that PR is a single, minor user-interface fix by contributor SNeedlewoods to prevent text overlap in certain languages. The rest of the diff is the initial population of the repository with the full Monero GUI source tree, build files, translations, images, and CI workflows. There is no security-relevant code change here.

This commit fixes a flaw in the Monero GUI wallet creation and restore wizard. Previously, when restoring or creating a wallet from keys, the temporary wallet was created with a blank password. If setting the user's chosen password later failed, the wizard would still save the wallet—leaving it protected by the blank password instead of the intended one. The change ensures the temporary wallet gets a random password and that the wizard aborts saving if the real password cannot be set.

This commit fixes a Qt 6 compatibility bug in the Monero GUI wallet. In Qt 6, passing a plain true/false value into a JavaScript callback argument list was being misread as a list size, so the callback received 'undefined' instead of the actual result. The fix explicitly wraps each value as a QJSValue. This is a reliability/functional bug, not a security vulnerability: there is no evidence it can be exploited to steal funds, run code, or bypass protections.

This commit only updates documentation and build scripts to remove the miniupnpc library from the list of dependencies. It does not change any actual program code, so it cannot directly introduce or fix a security vulnerability in the software itself. It is a housekeeping change reflecting that the project no longer needs miniupnpc.

This commit simply removes mentions of the libunwind library from build instructions and CI dependency lists. It is a documentation and build-configuration cleanup, not a code change. There is no indication of a security vulnerability being fixed.