Skylight Wallet

This commit removes leftover debugging code from a background task that checks for new wallet transactions. It deletes a console log message and, more importantly, removes a temporary '+1' fudge added to the transaction count. That fudge could have caused the app to think there was one more transaction than actually existed, which might trigger unnecessary notifications or confusion, but it does not appear to let an attacker steal funds or take control.

This commit is mostly a routine iOS build-system update for a Monero wallet app. It swaps a single-architecture iOS framework for a universal 'xcframework' that supports both real iPhones and the simulator, and makes a few small platform-specific cleanups in the Dart code. There is no clear security bug being fixed here; it looks like normal development work to get the iOS app building and running correctly.

This is a large work-in-progress commit for a Monero wallet app. It mainly adds iOS support (CocoaPods setup, a bundled MoneroWallet framework, notification and logging export features) and hardens error handling in the Tor/SOCKS networking code. There is no clear security fix or vulnerability being patched. A few debug leftovers, such as a hardcoded '+1' in transaction counting and a test notification fired on every wallet home screen load, look like unfinished development code rather than intentional malicious changes. The bundled binary framework cannot be inspected from the diff, so its provenance and safety are unknown.

This change stops a GitHub Actions workflow from accidentally including pre-built binary files (called 'artifacts') when it creates automated pull requests. Those binaries were being deleted from the repository and the workflow now removes them before opening a PR. This is a repository hygiene and supply-chain safety fix, not a direct vulnerability in running software.

This commit updates pre-built Monero library files (binary .so files) and points a dependency to a newer version of the upstream monero_c code. The actual source code changes are not visible because the files are compiled binaries. There is no information in the commit message or supplied references saying this update fixes a security problem, introduces a vulnerability, or changes any behavior at all. On its own, this looks like a routine dependency refresh.

This commit fixes a bug where the transaction history auto-refresh would break when a transaction was still pending (not yet mined). It also makes small user-interface tweaks, such as making list items easier to tap and widening text boxes in transaction details. There is no clear security vulnerability being patched.

This commit simply adds two GitHub usernames to a workflow so they are automatically asked to review future pull requests. It does not change any application code, build logic, secrets, permissions, or security settings.

This commit corrects a simple typo in a GitHub Actions workflow file. The workflow was supposed to trigger when the file itself changed, but the path had an extra '.yml' extension ('build-builder-image.yml.yml' instead of 'build-builder-image.yml'). This is a routine configuration fix with no security implications.

This commit adds automated GitHub Actions workflows to build a Monero wallet library from an external source and create pull requests with the compiled binaries. It also renames a Dockerfile and moves an existing script that removes an executable-stack flag from a Linux library. The changes are mostly build-infrastructure housekeeping. There is no direct evidence of a security vulnerability being introduced, but the workflow does clone and build code from a third-party repository (vtnerd/monero_c) without pinned commit verification at build time, and it later edits pubspec.lock using a remote branch's current commit hash. That creates a supply-chain risk if the upstream repository is compromised, but it is not a confirmed incident.

This commit adds a user-facing checkbox that lets mobile users choose to route the app's Tor traffic through the separate Orbot/InviZible app instead of a manually entered proxy port. It also changes the default external Tor port from 9150 to 9050 and makes a hardcoded error message translatable. There is no obvious security vulnerability in the diff; it is a feature/configuration improvement.

This commit adds user-configurable Tor settings to the Skylight Wallet app. Users can now choose between built-in Tor, an external Tor proxy, or disabling Tor entirely. It also updates how the app fetches exchange rates and blockchain heights so they respect the new Tor setting. There is no clear security bug in the patch itself, but it introduces a 'Tor disabled' mode and changes how network traffic is routed, which could affect user privacy if the settings are mishandled or bypassed.

This is a small GitHub Actions workflow fix. It corrects a path trigger so the workflow runs when the workflow file itself changes, and adds a missing 'attestations: write' permission needed for newer GitHub artifact attestation features. There is no direct security vulnerability in the diff; it is a maintenance/configuration correction.

This commit adds a new GitHub Actions workflow file that automatically builds and publishes a Docker builder image when the main branch changes. It is a routine CI/CD configuration change with no apparent security defect.

This commit removes a temporary workaround that stored unconfirmed outgoing transactions in the app's local settings. The app now relies on the underlying Monero wallet library to report pending transactions directly. The change also updates the transaction list UI so that transactions with no block height (height == -1) are shown as unconfirmed. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a cleanup of technical debt that may reduce the risk of stale or misleading transaction data.

This commit updates four precompiled Monero library files (binary .so files for Android and Linux) to a newer version. The actual source code changes inside those binaries are not visible in the commit, and no description of why the update was made is provided. There is nothing in the commit message or diff that indicates a security fix, vulnerability, or malicious change.

This commit simply updates the Flutter software development kit version from 3.38.3 to 3.38.5 and the Dart SDK version from 3.10.1 to 3.10.4 in build configuration files. There is no indication of a security fix or vulnerability being addressed.

This commit fixes a GitHub Actions release workflow that was supposed to sign Android and Linux app files with GPG. Before the fix, the signing command likely failed because it could not unlock the GPG private key without a passphrase. The change passes the GPG passphrase from a GitHub secret into the signing step so the automated signing can complete. It is a build-pipeline fix, not a vulnerability in the wallet application itself.

This commit simply updates the build script to download a newer version of the standard AppImage packaging tool (appimagetool) and records the matching SHA256 checksum. There is no indication of a security vulnerability or malicious change in the diff itself.

This commit only changes the app's version number from 1.0.2+6 to 1.0.3+7 in a configuration file. There are no code changes, no security fixes, and no functional changes visible in the diff.