Skylight Wallet

This commit is purely a visual redesign of the app's dark theme. It changes color values—making backgrounds darker and switching accent colors to a Monero orange shade—but does not alter any security logic, data handling, or network behavior.

This is a large user-interface refresh for the Skylight Monero wallet. Most changes are cosmetic: new logo, fonts, colors, labels, and screen flows. The only functional security-relevant change visible in the diff is that the app now derives whether a server connection uses HTTPS automatically from the address type (routable vs. onion/local), instead of letting the user toggle an 'useSsl' switch. This is a hardening move, not a vulnerability. There is no evidence in the commit of an exploit, backdoor, or data leak.

This commit only renames the user-facing label for a setting from 'Verbose Logging' to 'Enable Logging to File' (and the Portuguese equivalent). It changes displayed text strings in localization files, not how logging works, what data is logged, or any security behavior. There is no security issue here.

This commit mostly moves existing features—log exporting, delete-wallet dialog, and biometric unlock—into a shared library called wallet-core, and tweaks on-screen keyboard behavior. It is a refactoring and bug-fix patch, not a clear security fix. There is no direct evidence in the commit that it repairs a vulnerability, though centralizing sensitive code like biometric auth and wallet deletion in a shared library can make future security maintenance easier.

This commit is a routine UI refactor. It removes the app's own transaction-details popup and starts using a shared one from a related 'wallet-core' library. It also adds a couple of new translated labels, such as 'Change' and 'Copied to clipboard'. There is nothing in the diff that looks like a security fix or vulnerability.

This commit is a large refactoring change that moves several wallet features—fiat exchange rates, background syncing, notifications, and preference storage—out of the Skylight Wallet app and into shared 'wallet-core' packages. The app now imports and configures those packages instead of containing its own implementations. The change itself is architectural: it deletes hundreds of lines of local code and replaces them with thin wrappers and configuration calls. There is no obvious new security bug in the diff, but because the actual logic now lives in external packages that are not shown, the full security effect cannot be judged from this commit alone.

This commit removes the old 'WalletModel' wallet engine and switches the Skylight Wallet app to use only the newer 'wallet-core' engine. It is a large cleanup/refactoring change: about 2,000 lines of the old engine code are deleted, feature flags are removed, and screens now always talk to the shared wallet-core adapter. There is no direct evidence in the commit of a security vulnerability being fixed; it reads as a completion of a migration that had already been running behind a feature flag.

This commit fixes a small user-interface timing bug in the Skylight Wallet mobile app. It makes the ongoing background-sync notification show 'Wallet up to date' only when the wallet is actually caught up, instead of briefly showing it too early or staying stuck on 'Syncing…' when the wallet is already synced. There is no security-relevant change here.

This commit fixes a minor user-interface bug in a cryptocurrency wallet app. When the user had disabled the fiat price API, a red warning icon was incorrectly shown as if the API had failed. The change simply hides that warning icon when the API is intentionally disabled. There is no security issue here.

This commit changes two wallet setup screens so that users running a 'full node' mode skip a 'wallet details' screen that is only relevant to users relying on a third-party light wallet service. It also moves the start of a fiat-rate service earlier in the flow. There is no direct security vulnerability in the diff; it is a UI/routing correction that may reduce user confusion and avoid exposing unnecessary setup steps.

This commit is a routine feature patch that wires up background and foreground wallet synchronization and adds incoming transaction notifications across mobile and desktop. It does not appear to fix a security vulnerability; it is part of an ongoing migration to a shared 'wallet-core' backend. The changes mostly move existing logic into helper functions and add notification gating so users are not spammed or re-notified.

This commit changes how the wallet reacts when the user switches between server types (a local node versus a lightweight server). Instead of immediately rebuilding and resyncing the wallet in the foreground, the app now delegates that work to a dedicated method. The stated goal is to fix a delayed or stale connection-status display. The diff itself is a one-line refactor and does not contain any obvious security bug or fix for one.

This is a large feature/refactoring commit that introduces a new shared wallet-core integration path behind a compile-time flag, while keeping the existing legacy wallet code intact. It also removes the old in-tree openalias_ffi plugin and switches OpenAlias resolution to a new wallet_openalias package. There is no direct evidence in the diff of a security vulnerability, malicious change, or undisclosed fix. The work appears to be a normal architectural migration.

This commit changes the automated release build script to add `--enforce-lockfile` to a Flutter package command. That flag tells the build tool to use exactly the dependency versions recorded in the project's lock file and not silently upgrade or change packages. It is a supply-chain hardening measure that reduces the chance of an unexpected or malicious package version sneaking into a release build, but it is not a fix for a known active vulnerability.

This commit changes the F-Droid build script to add the '--enforce-lockfile' flag when Flutter downloads its package dependencies. In plain terms, it tells the build tool: 'only install the exact versions of dependencies recorded in the lockfile, and fail if the lockfile is missing or out of sync.' This is a supply-chain hardening measure. It reduces the risk that a build silently picks up a newer, potentially malicious or buggy version of a dependency, but it is not a fix for a known active vulnerability.

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

This commit only adds helper shell scripts for building and verifying the app. There is no change to the app itself, no new feature, and no security fix or vulnerability introduced. The scripts are developer tooling for reproducible-build testing.

This commit fixes two reliability problems in a cryptocurrency wallet app. First, it adds a 20-second timeout when fetching fiat exchange rates, so the app no longer waits forever if the network stalls. Second, it adds a 5-second timeout when closing the Tor/ SOCKS network socket, preventing a slow shutdown from hanging the app. It also removes a line that set wallet key-derivation rounds to 1, which is a very low, insecure value. The commit message only mentions the fiat-rate loading issue, not the security change.

This commit changes how a cryptocurrency wallet app handles errors when restoring a wallet from a seed phrase. It now ignores certain 'connection' errors that occur before the wallet has actually connected to a server, and it also lowers the password-stretching strength (kdfRounds) to 1 during this restore step. The change appears aimed at letting users restore wallets even when the app cannot immediately reach its backend server, but it may also hide real errors and weakens the cryptographic protection of the wallet file during restore.

This commit only swaps out precompiled Monero wallet library files (binary blobs) for Android, iOS, Linux, and Windows. There is no source code change, no description of what changed in the libraries, and no security context provided. On its own, this diff tells us nothing about whether the update fixes a security issue, introduces one, or is simply routine maintenance.