Skylight Wallet

This commit adds a password prompt for the Skylight Wallet app when running on desktop computers (Linux, Windows, macOS). Previously, the app only used the phone's biometric/PIN lock, which isn't reliably available on desktop. The change makes desktop users create and enter a wallet password to protect their funds. It is a security improvement, not a vulnerability fix, though the password is held in memory while the app runs and is not persisted on desktop.

This commit is a routine user-interface layout fix. It limits how wide three wallet setup screens can stretch on desktop computers by wrapping them in a centered container with a maximum width. There is no security-relevant change.

This commit is a routine UI polish for the Skylight Monero wallet. It makes screens adapt better to large monitors and tablets, adds a desktop copy-address button, fixes a macOS notification bug, and replaces a full-screen transaction details page with a popup dialog. There is no clear security vulnerability in the changes, but one small behavior change is worth noting: the old receive screen copied the address silently when tapped, while the new code shows a confirmation message. Most of the diff is reformatting and layout work.

This commit adds Linux support to a Monero wallet app. Most changes are ordinary cross-platform plumbing, but two items deserve a closer look: a new helper script edits a binary shared library to clear an 'executable stack' flag, and the app now stores wallet files, Tor data, and logs in the user's home directory under a hidden folder on Linux. The commit itself does not describe these as security fixes, and there is no external advisory or researcher attribution supplied.

This commit only increases the app's build number from 3 to 4 in a configuration file. It makes no code changes and has no security relevance.

This is a one-line defensive fix in a Dart wallet app. It prevents the app from notifying UI listeners about a connection change if the underlying wallet object has already been deleted. The change likely avoids a crash or inconsistent UI state when a wallet is removed, but it is not a security vulnerability that an attacker can directly exploit.

This commit adds a safety check to a cryptocurrency wallet so that, when the server can no longer create new subaddresses, the app warns the user and falls back to reusing an already-used subaddress instead of silently failing or leaking privacy. It is a defensive/privacy-hardening change, not an obvious vulnerability fix, but it addresses a real privacy edge case: address reuse weakens transaction privacy.

This commit is a routine cleanup of a Monero wallet app. It mainly moves repeated startup steps into a single helper function, caches whether the server supports subaddresses in local app storage, and improves loading indicators on the connection setup screen. There is no obvious security bug introduced, but the change is not purely cosmetic because it alters when and how the app checks server capabilities and stores that result.

This commit only increases the app's build number from 2 to 3 in a configuration file. There are no code changes, no security fixes, and no functional changes of any kind.

This commit adds a feature that checks whether the user's chosen Monero light-wallet server supports subaddresses. Before this change, the app could show a subaddress even when the server did not support it, which could cause incoming transactions to be missed. The change also removes a stored user preference that always defaulted to showing the primary address, and instead auto-detects server capability and defaults to showing a subaddress when supported. The most notable security-relevant side effect is that the app now sends the wallet's secret view key to the light-wallet server during the check, and it does so over plain HTTP unless the user has enabled SSL/Tor. That is a privacy-sensitive design choice, but it is consistent with how Monero light wallets already operate.

This commit only adds and updates the project's README file. It introduces no code changes, no configuration changes, and no functional modifications to the wallet application. There is no security relevance in the diff itself.

This commit adds a visual loading spinner to the wallet restore screen and prevents the restore button from triggering multiple restore attempts at once. It is a user-experience improvement, not a security fix.

This commit only changes the app's build number from 1 to 2 in a configuration file. It does not modify any code, fix any behavior, or affect security in any way.

This commit adds a transaction fee priority selector to a Monero wallet app. It lets users choose Low, Normal, or High transaction priority and shows estimated fees. The change also moves OpenAlias address resolution onto a background thread. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a user-facing feature improvement.

This commit simply adds correct currency symbols (like £ for British pounds or ¥ for Japanese yen) to the wallet's display. It is a user-interface improvement with no security relevance.

This commit fixes a bug where restoring a wallet from a recovery phrase left the wallet in a disconnected state. After the fix, the app automatically refreshes the wallet, loads account statistics, and connects to the network daemon once the restore completes. There is no indication this was a security vulnerability; it appears to be a functional bug fix for wallet connectivity.

This commit is a routine build configuration change. It sets up proper Android release signing (so the app can be published on app stores) and updates the app's package name and copyright strings across Android, iOS, macOS, and Windows from placeholder/example values to the real project identity (MAGIC Grants / Skylight Wallet). There is no security vulnerability here.

This commit makes two tiny cleanups: it removes two harmless warning log messages that were printed when a background timer ran before a wallet was opened, and it removes the 'const' keyword from one UI padding value. There is no security issue here.

This commit adds a 'demo mode' to the wallet app. When the app is built with a special environment flag and the user types 'demo' as the server address, the app skips the real network connection test and pretends it succeeded. This is a development/testing convenience, but it could let someone bypass the actual connection check if they can trigger or build the app in demo mode.

This commit fixes a minor memory leak that could occur after a wallet is deleted in the Skylight Wallet app. It adds safety checks so background timer tasks stop trying to work with a wallet that no longer exists, and it prevents an error in one stats-loading task from crashing the whole refresh process. The changes are defensive and improve stability, but they do not appear to be a security fix for an actively exploitable vulnerability.

This commit fixes a cleanup bug: when a user deletes their wallet, the app now also removes the saved address book (contacts) and any pending outgoing transactions from phone storage. Before this fix, those details could remain on the device after the wallet was supposedly deleted, which is a privacy and data-retention issue rather than a direct money-stealing bug.