Package Details: lnd 0.12.1_beta-1

Git Clone URL: (read-only, click to copy)
Package Base: lnd
Description: The Lightning Network Daemon, for secure off-chain bitcoin transactions.
Upstream URL:
Licenses: MIT
Conflicts: lnd-git
Provides: lncli, lnd
Submitter: dmp1ce
Maintainer: dmp1ce
Last Packager: dmp1ce
Votes: 2
Popularity: 0.000000
First Submitted: 2018-07-20 13:43
Last Updated: 2021-03-14 23:16

Latest Comments

1 2 Next › Last »

Spixmaster commented on 2021-03-03 18:36

The PKGBUILD has the issue that it cannot be reinstalled. First the yay cache (~/.cache/yay/lnd/) needs to be emptied. Otherwise, this error message appears error cloning lnd: fatal: Zielpfad 'lnd' existiert bereits und ist kein leeres Verzeichnis. which means that the directory "lnd" already exists.

dmp1ce commented on 2019-09-27 13:57

@setpill OK. Thank you for creating the -bin.

setpill commented on 2019-09-27 13:44

FYI I talked to roasbeef on IRC yesterday and he indicated a new release is "a week or two" away. I have also created in the interim, and for those who prefer a binary package (signed by upstream).

dmp1ce commented on 2019-09-26 21:15

@setpill, it sounds like this package is in a bit of mess. Go isn't compiling and the gpg keys are expired.

I'll ask the devs about the expired key.

For the Go version, I'll think I'll just wait until upstream fixes. Unless someone gives me a patch to compile with a previous Go version.

setpill commented on 2019-09-26 17:02

Unfortunately, it seems that the latest release will not build on the current version of Go (1.13). There is a fix ( but a new release has not yet been cut. Perhaps a workaround with a patch could be done, but it is a bit too much fiddling for me. In any case; the source verification that I added to prepare():

  pushd "$pkgname"
  git verify-tag "v$_pkgver"

NB: The latest tag was signed with a now-expired key. Using libfaketime I was able to work around it for testing purposes.

dmp1ce commented on 2019-09-26 01:00

@setpill, I tried to grab the LND archive from github but the build wouldn't work for me. If you want to give it a try and send me the patch, I'll take a look.

Git uses SHA1 or SHA256 I think. HTTPS also has security.

But the tag I'm using could change on the repository. Also, a DNS attack could break HTTPS assurances.

setpill commented on 2019-09-20 14:16

Please add checksum/gpg verification of package source. Preferably sha512 or something equally not-broken.

dmp1ce commented on 2019-06-27 11:01

Use lnd-git if you want the latest. I'm going to skip RCs.

mosh5382 commented on 2019-06-26 17:59

They have released 0.7.0 but it is only and RC2. Not sure if you want to update for release candidates but this is all pretty beta anyway so why not!

dmp1ce commented on 2018-12-22 14:19

@smmalis37 I think we will need to wait until the next release. Using you suggestions I still wasn't able to get 0.5.1-beta building.