Skylight Wallet

This commit only changes how the app pulls in its shared wallet library. It switches from a local folder reference to a pinned Git commit from the same project's online repository, and updates that pinned version to a newer commit. There is no visible code change in the app itself, and nothing in the commit message or diff indicates a security fix or vulnerability.

This commit updates a dependency pin for the core Monero library used by the Skylight Wallet app and switches several wallet helper packages from remote Git downloads to local file paths. The change itself is a routine dependency bump and local development path change. There is no direct evidence in the commit that this fixes a security vulnerability, but updating a pinned cryptographic/wallet library can sometimes include security fixes from upstream. We cannot confirm that without inspecting the upstream library changes, which are not provided.

This commit fixes a bug in the Skylight Wallet's Monero receive screen where the wallet could display one subaddress while labeling it with the index of a different subaddress. The fix bundles the address and its index into a single value so they are always read together consistently. If left unfixed, a user could copy and share a receiving address that is mismatched with the label, potentially causing payments to be credited to the wrong wallet entry or making reconciliation confusing. There is no direct evidence of malicious exploitation; it appears to be a correctness and usability fix.

This commit is a routine UI cleanup. It removes hard-coded placeholder text examples for server addresses from the app's translation files and instead asks the underlying wallet library for example addresses. There is no security-relevant change here—only where the example text comes from.

This commit only increases the app's build number from 407 to 408 in a configuration file. It changes no code, no dependencies, and no security settings. There is no security relevance.

This commit changes where the example server addresses come from in the wallet's connection setup screen. Previously, placeholder text like 'lws.example.com:18090' and 'node.example.com:18081' was hard-coded in the app's translation files. Now the app asks the underlying wallet-core library for an example address instead. There is no visible security bug being fixed here; it appears to be a code cleanup or consistency improvement.

This is a large bug-fix and refactoring update for the Skylight Wallet app. The most important security-relevant changes fix ways the app could send or store money incorrectly: amounts were being converted through imprecise 'double' numbers, which could slightly alter the value the user intended to send; the 'Max' send button could fail or produce wrong values for large balances; the address book was moved into shared wallet-core code so both apps use one secure storage format; and deleting a wallet now properly stops the background sync service first, preventing the deleted wallet from being recreated by a still-running background task. Several other changes improve error handling, sharing, and connection settings so users do not accidentally save a private-server address as a public one.

This commit fixes two practical bugs in a Monero wallet app. First, it stops comparing money amounts using floating-point 'double' numbers, which can round incorrectly and let a user think they are sending their full balance when they are not (or vice versa). It now compares exact integer 'piconero' units. Second, it makes the Tor connection logic respect the user's Tor setting: if Tor is set to 'external' or 'disabled', the app no longer blindly tries to start its built-in Tor and waits two minutes. These are correctness/reliability fixes rather than obvious remote-hack vulnerabilities, but they could affect privacy and funds handling.

This commit fixes a Monero wallet bug where the amount a user wanted to send could silently change because the app was converting the typed amount into a 'double' (a computer number format with limited precision) before turning it into the exact atomic units the blockchain actually uses. The patch keeps the amount as text the whole way through, so the value the user sees is the value that gets spent. It also fixes a related bug where tapping 'Max' for large balances could produce unusable scientific notation like '5e-7'.

This commit fixes a Monero wallet bug where the app could accidentally save a private 'view key' to a regular Monero node instead of a lightweight wallet server (LWS). The fix separates saved server addresses for the two connection modes so that switching modes doesn't leave the wrong server address in the settings field. If the wrong address were saved, the user's private view key could be exposed to a node operator, allowing them to see all incoming transactions for that wallet.

This commit fixes a bug in the wallet-deletion process. Previously, the app deleted wallet files while a background sync service still had them open in another process. That could leave deleted wallet data partially restored on disk, or cause the app to keep syncing a wallet the user asked to remove. The fix tells the sync service to stop first, then deletes the wallet through the core library's proper teardown path.

This commit only updates the app's version number and switches its internal wallet-core library to a newer pinned commit. No actual code changes are shown, and the commit message does not say anything about fixing a security problem. On its own, this diff does not demonstrate any vulnerability or security fix.

This commit fixes two real security gaps in a mobile cryptocurrency wallet. First, when the app was sent to the background and later reopened, it could return to an already-unlocked wallet with the password still in memory, letting anyone with the phone reach the seed phrase. The patch now locks the app on resume. Second, simply viewing the seed/secret keys only showed a warning sheet; now it also requires a fingerprint or face scan first. The commit message frames this as 'unifying lock requests between apps,' but the code comments and changes clearly describe the underlying security problems.

This commit removes a local QR-restore parser and switches the wallet to use a shared parser from another package. It also fixes two unrelated bugs in the send screen: one that could permanently block fee estimates after a single failure, and another that displayed tiny 'Max' balances in scientific notation, breaking sending. There is no obvious security vulnerability in the diff itself; the main concern is whether the new shared parser is as safe as the old one, which cannot be judged from this commit alone.

This commit adds Face ID and Touch ID support to unlock the Skylight Wallet app on iOS. It is a feature addition, not a security fix. There is no evidence in the commit of a vulnerability, bug, or security-relevant change beyond normal biometric authentication integration.

This commit fixes a security bug in how the Skylight Wallet app copies sensitive information to the clipboard. Previously, some screens copied wallet addresses and secret keys using the regular system clipboard, which could leave that data exposed in the clipboard history. The patch makes those screens use the app's secure clipboard helper instead, which marks the data as sensitive and clears it automatically. It also adjusts Android 13+ so the app doesn't show a duplicate 'copied' confirmation when the operating system already shows one.

This commit fixes a user-interface bug in the wallet's settings screen. Previously, when the on-screen keyboard appeared, it could cover the bottom of a settings form because the popup sheet was sized using the full screen height. The change subtracts the keyboard area from the available height so the sheet shrinks accordingly, keeping input fields visible and usable. There is no security issue here.

This commit only changes user-facing text strings in the Skylight Wallet app. It updates labels, descriptions, and warnings shown to users in English and Portuguese to be clearer and more informative about privacy and security risks. No code logic, security behavior, or functionality was modified.

This commit swaps out precompiled Monero wallet library files for newer versions across Android, iOS, Linux, and Windows. The only human-readable change is updating the iOS framework's bundle identifier from 'com.skylight.MoneroWallet' to 'org.magicgrants.MoneroWallet'. The actual code inside the binary libraries is not shown, so we cannot tell from this commit alone whether the update fixes security bugs, introduces them, or is purely routine maintenance.

This commit simply turns off automated desktop builds for Linux and Windows in the project's release pipeline. It does not change any wallet code, fix a bug, or introduce a security feature. The Android build remains active, and the release job no longer waits for the disabled desktop jobs.

This is a one-line shell script fix that changes how the build script reads the required Rust compiler version from a configuration file. The old method could fail to extract the version correctly in some cases, potentially causing a build to use the wrong Rust toolchain. The new method is simpler and more robust. There is no direct evidence this is a security vulnerability, but build reproducibility and toolchain correctness are security-relevant for software supply-chain integrity.

This commit is a build-maintenance change, not a security fix. It creates one central file (rust-toolchain.toml) that declares which Rust compiler version to use, and updates build scripts and Docker configuration to read from that file instead of hard-coding an older version. There is no change to wallet logic, cryptography, or user-facing behavior.

This commit simply updates version numbers and switches several software dependencies to newer pinned versions. There is no visible code change in the app itself, and the commit message gives no indication that any security problem is being fixed. Without inspecting the actual contents of the updated dependency versions, we cannot tell whether this update addresses a security issue or is just routine maintenance.

This commit is a routine product update that brings user-interface improvements from another wallet project ("spice") into Skylight Wallet. It changes labels and help text, updates the address-book design, adds a language picker to the welcome screen, and refreshes the privacy policy and terms of service. There is no evidence of a security fix or vulnerability being introduced.

This commit is a routine code cleanup. It removes several unused or dead utility files, widgets, and tests, and moves one small status icon definition into the screen that uses it. There is no change to how the app handles money, keys, network connections, or user data, and nothing in the commit suggests a security fix.