Wallet Logo

Lightning (Remove Funds by Dec 31st)

Latest release: Varies with device ( 2nd October 2020 ) 🔍 Last analysed 4th February 2021 . Under development Not functioning anymore
1 thousand

Jump to verdict 

Help spread awareness for build reproducibility

Please help us spread the word discussing build reproducibility with Lightning (Remove Funds by Dec 31st)  via their Twitter!

Do your own research!

Try out searching for "lost bitcoins", "stole my money" or "scammers" together with the wallet's name, even if you think the wallet is generally trustworthy. For all the bigger wallets you will find accusations. Make sure you understand why they were made and if you are comfortable with the provider's reaction.

If you find something we should include, you can create an issue or edit this analysis yourself and create a merge request for your changes.

The Analysis 

Update: This app is not supported by its provider anymore. As the name reads “Lightning (Remove Funds by Dec 31st)” and the description talks about “3 months” we assume this app still being on Google Play is an accident.

From the description:

  1. Install the app and follow the setup instructions.
  2. Send a small amount of BTC to your wallet address (not more than you are willing to lose, it’s alpha)
  3. Wait a few minutes for the wallet to sync. Once completed, the app will open payment channels automatically. The funding transactions need to confirm just like regular on-chain transactions.

If it “sync”s and “open payment channels automatically”, it is probably a non-custodial app, although that is not said explicitly in the description.

But there is also a link to their GitHub.

There is no word on the Android build on the main Readme.md but under mobile we find something …

$ git clone https://github.com/lightninglabs/lightning-app
$ cd lightning-app/
$ docker run --rm --volume=$PWD:/mnt --workdir=/mnt  -it beevelop/cordova bash
root@bf7373350a59:/mnt# npm install
added 2140 packages from 1995 contributors and audited 943144 packages in 68.29s
found 11 vulnerabilities (8 moderate, 3 high)
  run `npm audit fix` to fix them, or `npm audit` for details
root@bf7373350a59:/mnt# cd mobile
root@bf7373350a59:/mnt/mobile# npm install
root@bf7373350a59:/mnt/mobile# cd android/
root@bf7373350a59:/mnt/mobile/android# yes | /opt/android/tools/bin/sdkmanager "build-tools;28.0.3"
root@bf7373350a59:/mnt/mobile/android# ./gradlew bundleRelease
> Task :app:bundleReleaseJsAndAssets
warning: the transform cache was reset.
Loading dependency graph, done.
error Unable to resolve module `../../assets/rpc` from `/mnt/src/action/grpc-mobile.js`: The module `../../assets/rpc` could not be found from `/mnt/src/action/grpc-mobile.js`. Indeed, none of these files exist:
  * `/mnt/assets/rpc(.native||.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)`
  * `/mnt/assets/rpc/index(.native||.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)`. Run CLI with --verbose flag for more details.

> Task :app:bundleReleaseJsAndAssets FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:bundleReleaseJsAndAssets'.
> Process 'command 'node'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/4.10.1/userguide/command_line_interface.html#sec:command_line_warnings

1 actionable task: 1 executed

So we threw what we know at it but failed there.

We did not take the route using Android Studio, as that should never be necessary as Android Studio itself uses gradle to build Android projects. For our purpose a tool with graphical interface, involving clicking buttons is not practical as build verification will be fully automated as it needs to be reevaluated after each release.

So for now we hope for better build instructions so we can soon give it another try and conclude this provider probably shares the source but it’s not verifiable.

Verdict Explained

We still have to analyze this product.

As part of our Methodology, we ask:

Did we get to a conclusion on the verdict of this product yet? If not, we tag it Development

This product still needs to be evaluated some more. We only gathered name, logo and maybe some more details but we have not yet come to a conclusion what to make of this product.

But we also ask:

Is the product still supported by the still existing provider? If not, we tag it Defunct!

Discontinued products or worse, products of providers that are not active anymore, are problematic, especially if they were not formerly reproducible and well audited to be self-custodial following open standards. If the provider hasn’t answered inquiries for a year but their server is still running or similar circumstances might get this verdict, too.