lightninglabs / lightning-app

An easy-to-use cross-platform Lightning wallet

Lightning

An easy-to-use cross platform lightning wallet

N.B. This is still early technology and there’s a risk of losing all of your funds. We recommend not putting in more money than you are willing to lose.

Getting Started

The app comes for two threat models:

1. Pocket Money: prebuilt and signed releases with auto update (recommended for most users).

2. Tin Foil Hat: if you'd rather build it yourself and do without auto updates, see the instructions below.

Contributing

See the ToDo (next release) column on our project board. Issues that are easy to pick up for outside contributors are labeled help wanted.

Developing Locally

To build the mobile app locally, see the README in the /mobile directory for instructions.

To build the desktop app locally follow the instructions below:

Install lnd

We will use lnd to make GRPC calls from the ReactJS environment

git clone https://github.com/lightningnetwork/lnd $GOPATH/src/github.com/lightningnetwork/lnd
cd $GOPATH/src/github.com/lightningnetwork/lnd
make && make install tags="experimental autopilotrpc signrpc walletrpc chainrpc invoicesrpc routerrpc"

If you have any issues with this step, make sure to review the Preliniaries to installing LND

Install btcd

We will use btcd as the backend operating mode

git clone https://github.com/btcsuite/btcd $GOPATH/src/github.com/btcsuite/btcd
cd $GOPATH/src/github.com/btcsuite/btcd
GO111MODULE=on go install -v . ./cmd/...

Set up & run

Cloning this git repo git clone https://github.com/lightninglabs/lightning-app and from the project root folder run the following commands:

npm install

npm test

To start the app in development mode (simnet):

npm run electron-dev

Running in development mode can allow you to run in full node mode instead of the default neutrino mode, and will also allow you to run in simnet node for testing. The app will use it's own lnd data/lnd dir and does not share state with other lnd installations on your system. See setup local cluster on how to set up your simnet cluster for development.

Review UI style guide

To build the UI style guide

npm run storybook

Building the Packaged App

To build the packaged version of the app e.g. for macOS run:

cp $GOPATH/bin/lnd ./assets/bin/darwin
npm run electron-pack

The packaged app will then be available in the dist directory. The packaged version of the app will run on Bitcoin mainnet.

Starting the Packaged App (light client)

To run the packaged version of the app e.g. for macOS run:

./dist/mac/Lightning.app/Contents/MacOS/Lightning

The app is configured for mainnet by default but you can opt-in to testnet:

./dist/mac/Lightning.app/Contents/MacOS/Lightning --bitcoin.testnet --bitcoin.node=neutrino --neutrino.addpeer=btcd-testnet.lightning.computer --neutrino.feeurl=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json

Starting the Packaged App (full node)

btcd

Start btcd in a separate terminal session and wait until it's fully synced (can take a while):

btcd --txindex --rpcuser=kek --rpcpass=kek

To run the packaged version of the app e.g. for macOS run:

./dist/mac/Lightning.app/Contents/MacOS/Lightning --bitcoin.mainnet --btcd.rpcuser=kek --btcd.rpcpass=kek

bitcoind

Start bitcoind in a separate terminal session and wait until it's fully synced (can take over a day):

bitcoind -txindex=1 -rpcuser=kek -rpcpassword=kek -rpcbind=localhost -zmqpubrawblock=tcp://127.0.0.1:28332 -zmqpubrawtx=tcp://127.0.0.1:28333

To run the packaged version of the app e.g. for macOS run:

./dist/mac/Lightning.app/Contents/MacOS/Lightning --bitcoin.mainnet --bitcoin.node=bitcoind --bitcoind.rpcuser=kek --bitcoind.rpcpass=kek --bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332 --bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333

Lnd data and logs

Lnd data and logs are written to the following locations in production:

• Linux: ~/.config/lightning-app/lnd
• OSX: ~/Library/Application Support/lightning-app/lnd
• Windows: %USERPROFILE%\AppData\Roaming\lightning-app\lnd

lightning-app's Issues

Fix window draggability on Windows and Linux

Currently, because of a difference in how Electron implements WebkitAppRegion: 'drag' in Windows and Linux, draggability was removed in order to enable clicks on the menu. Need to restore draggability in a cross-platform way. May be solved by implementing issue #5.

Generate / Display QR code when generating a Request for lightning payment and ability to scan QR code when making a Payment request

It would be useful for a POS operator to be able to display a Request for payment QR code to a customer when using the application. Hence, if a QR code is generated for a lightning payment request just like the Bitcoin receiving address QR code it would be very useful.

Also, at the same time like on the https://starblocks.acinq.co webpage as soon as you make a purchase it displays the payment request code on the checkout page with a QR code to scan. It would be useful to provide the ability to provide a scan button to invoke the webcam / scanner to scan a QR code when making payments.

Note: This isn't an issue, but a feature request.

Handshake failed with fatal error SSL_ERROR_SSL

After installing dependencies and running setup, I am getting the following:

Handshake failed with fatal error SSL_ERROR_SSL: error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE

can not create channel

error: encoding/hex: odd length hex string

Add autopilot history/settings page

Currently, autopilot runs in the background without exposing any details of its operation. While this is helpful and intuitive to beginners, it may be confusing to more advanced users who are unsure why channels and transactions are being created. An autopilot history page could be helpful in explaining what actions have been taken by autopilot.

Eventually, a settings page could be added that would enable users to tune the behavior of autopilot for their particular use cases.

Add progress bar for chain sync

Would be nice to have a visualization of where things are in the chain sync. Also, for advanced users, could be good to indicate stage of syncing, such as header download, filter download, rescan, etc. Initially requested by paulcapestany.

Full support for lighting:// protocol payment requests

When clicking a lightning payment request link, the app should open, bring up the pay page, and populate the payment request and amount fields. Currently, the app will open, but won't change pages or populate fields.

Update to latest build of Electron

Getting a "Windows protected your PC" error when running.

Not sure it's important at this stage, but getting an error when running on a windows system.

Display appropriate error message when balance is low in channel when paying

Currently while attempting to make a payment and if the channel balance is low, then the error message displayed is "Payment route failure". This is the same message that's displayed even when a channel isn't created and connected. Instead I feel it would be more useful for the user if it were to display "Balance low on channel to make payment"

Provide the ability to swtich between Bitcoin units - SAT (Satoshi), mBTC, BTC etc..

Currently I'm unable to switch between units. It would be beneficial if it was possible to switch between the various Bitcoin units - SAT (Satoshi), mBTC, BTC etc such that those accustomed to a particular unit would find it easy to pay / request transactions.

lightning-app dislikes certain usernames

Problem

v0.1-alpha will fail to run for a user that contains 'lnd' within the username. Possibly also 'lnd' within the hostname (originally I tested lnd@lnd, lnd2@lnd2, lnd3@lnd3...).
Tested on Ubuntu 16.04, 17.04, 17.10.
The error message lnd Already Running prevents the interface from loading and lnd never appears in ps.

Solution

The immediate workaround for me was to create a new VM with a different username/hostname not containing lnd.
I believe the culprit to be the ps.lookup function in apps/desktop/main.dev.js. I suspect that it's doing somethine like grepping the ps output, seeing lnd in a directory name or user name and assuming it's running. Not quite sure.

This was a bit of a wild goose chase :)

Don't show QR code for receiving during initial sync

Deported by djseeds on slack:

I think the wallet QR code should probably be disabled during chain sync, because right now it generates a QR code of `bitcoin:Opening Wallet...`

Before the neutrino backend is fully synced, it won't be able to fetch an address from the RPC server as it doesn't start up until the chain backend has finished syncing.

The send/receive tab itself should be shown as inactive, and should ignore user input until neutrino has fully synced.

Bootstrapping in endless fail loop

lnd: 2017-10-14 07:52:51.226 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [nodes.lightning.directory]
lnd: 2017-10-14 07:52:55.458 [INF] BTCN: Disconnecting peer 127.0.0.1:18333 (outbound), cannot serve compact filters
lnd: 2017-10-14 07:52:55.459 [INF] BTCN: Lost peer 127.0.0.1:18333 (outbound)
lnd: 2017-10-14 07:52:55.463 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-14 07:53:00.467 [INF] BTCN: Disconnecting peer 127.0.0.1:18333 (outbound), cannot serve compact filters

repeats forever

Mac client

Feature Request: Channel history

I've opened and closed a couple channels at this point, but looking back, there's no record I ever had those now-closed channels. Users probably don't want to see those all the time, but having a "show history" button to show your closed channels would be nice. Also nice would be a "purge history" button, or the ability to erase record of individual channels.

Add transaction detail page

Currently, the transactions page only has a truncated txid and an amount. It should allow the user to drill down and get the transaction details such as to, from, blockheight, number of confirmations, segwit/non-segwit, whether the transaction was part of a channel funding/closing etc.

Add Commmas to Large Numbers in Wallet

https://twitter.com/lwsnbaker/status/918611275210297344

Initializing Wallet / Opening Wallet...

I downloaded the windows version of this, ran the program, gave it network access when the popup came up. Next step is to send myself some sats from a faucet. I assume to do that I need to copy my address in the Receive section and send to it. Problem is that the address text line contains either "Opening Wallet..." or "Initializing Wallet" for like half an hour. Does it have to finish "Syncing to Chain" before I can use my wallet? I would have thought I could just have an address i could immediately use, even if the client couldn't see my transactions until its done syncing.

Another problem, if I click the "Wallet Address" text, it copies the text in the address line (eg "Opening Wallet..."). Might want to disable copying the wallet address until there's an address to copy.

The UI looks neat so far tho! Looking forward to testing it out once I can drink from a faucet!

Convert Settings (Logs) page into status page

Take the relevant information from log output and convert it into a set of status indicators that would be more easily consumable by users.

Add an actual settings page

Currently, the settings page is log output. Need to determine which settings should be exposed and provide ways to change those settings.

Illegitimate request of funds results in a transaction in progress.

I requested funds from a testnet faucet, the transaction should be invalid but shows up as a transaction in progress.

Add channel detail page

Currently, the Channels page shows the channel ID and balances. The user should be able to drill down to get the channel details, such as the time the channel has been open, the transaction history/total volume for the channel, the public key of the other channel party, fees and fee rates, whether the channel was an autopilot channel and other related stats. Some of this data may be considered advanced, so this information should probably be split into a basic channel detail and a more advanced one.

Add wallet creation/backup/restore

Currently, the app uses the wallet automatically generated by lnd without providing a facility for creating new wallets, backing up old wallets (via seed), or restoring wallets.

Add a console section to the settings page

A "console" page should be added to the settings page. This would let users manually enter lncli commands like adding peers, listing their channels, changing the debuglevel, etc.

Such a page would also aide in debugging as users will be able to input directed commands in order to get a better feel for what the issue at hand is.

Add cross-platform continuous integration

Change title bar and open/close/minimize to platform-specific widgets

Currently the open/close/minimize widgets are the same cross-platform. Other Electron apps like Keybase use the platform-specific title bar and widgets. Originally requested by moli.

Remove menu bar from Windows build

In the windows build, the menu bar still appears with the "Lightning" and "Edit" drop-down menus. This is despite mainWindow.setMenu(null) in main.dev.js.

Prevent copying 'Opening Wallet', 'Initializing Wallet' values in Wallet Address field and disable QR code until address available

Prevent copying 'Opening Wallet', 'Initializing Wallet' values in Wallet Address field and disable QR code until address available.

Feature Request: Delete "in-progress" transaction requests.

I have a couple transaction requests that probably will never be fulfilled. I'd like to delete them.

Paying to your own Bitcoin Wallet address - Missing funds in wallet?

I'm not sure what's happening here but when receiving Bitcoin (on-chain) funds to my Lightining app Bitcoin address, I had received the funds in 2 confirmations (both the tx id and the wallet balance updated right after 2 confirmations)

I tried to pay my Bitcoin Wallet address generated in the lightning app (I know, that's dumb but I was experimenting) and I've waited 2 transaction confirmations. The transactions have confirmed but I haven't received the funds I had sent to myself.

Wallet balance and transaction before paying myself: In this image you can see the log that the new address has been generated by the wallet and I've sent coins to it.

Wallet balance and transactions after paying myself:

Here's the tx id: https://testnet.smartbit.com.au/tx/7c200913e9ecb63dee1868b638a8850713a3906751be4c9467dd262ae8c185cc

and one more tx (this is the first time I tried it and haven't received this one either): https://testnet.smartbit.com.au/tx/fb2c4c2dae3c2886ee3e1280c6657bad0a39d94eb6244b439ba8706900749d6b

Problem syncing chain

lnd: 2017-10-13 23:09:56.718 [WRN] LTND: open ../lnd.conf: Le fichier spécifié est introuvable. 2017-10-13 23:09:56.774 [INF] LTND: Version 0.3.0-alpha 2017-10-13 23:09:56.775 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0 2017-10-13 23:09:56.775 [INF] LTND: Primary chain is set to: bitcoin unable to create chain control: unable to create neutrino: EOF
lnd Error: unable to create neutrino: EOF
lnd: 2017-10-13 23:09:56.718 [WRN] LTND: open ../lnd.conf: Le fichier spécifié est introuvable. 2017-10-13 23:09:56.774 [INF] LTND: Version 0.3.0-alpha 2017-10-13 23:09:56.775 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0 2017-10-13 23:09:56.775 [INF] LTND: Primary chain is set to: bitcoin unable to create chain control: unable to create neutrino: EOF
lnd Error: unable to create neutrino: EOF

Header doesn't pass sanity check

Repo:

• during initial sync had to stop and restart lightning app a few times
• now can't get past head block 1210149
• after failure with message:

lnd: 2017-10-13 19:17:35.023 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer

• it disconnects the peer at 35.199.154.3:18333 and then reconnects to it:

2017-10-13 19:17:35.023 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:17:35.023 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:17:40.576 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)

• and then goes back and syncs again:

lnd: 2017-10-13 19:17:40.577 [INF] BTCN: Syncing to block height 1126632 from peer 35.199.154.3:18333 2017-10-13 19:17:40.577 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333

• wash, rinse, repeat

Difficulty of block 121049 is : 486,604,799 == 1D00 FFFF and sanity check mentions difficulty target of:
00000000ffff0000000000000000000000000000000000000000000000000000

System info:

Windows 10 Pro x64 - version 1703, OS Build 15063.674

My log file:

Pubkey: 03ab3a8098216569f291fe04eafda8c15b6e8a81640b452281e82b8b5350449de6
Logs
lnd: 2017-10-13 19:06:06.150 [WRN] LTND: open ../lnd.conf: The system cannot find the file specified. 2017-10-13 19:06:06.151 [INF] LTND: Version 0.3.0-alpha
lnd: 2017-10-13 19:06:06.153 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0 2017-10-13 19:06:06.153 [INF] LTND: Primary chain is set to: bitcoin
lnd: 2017-10-13 19:06:06.150 [WRN] LTND: open ../lnd.conf: The system cannot find the file specified. 2017-10-13 19:06:06.151 [INF] LTND: Version 0.3.0-alpha
lnd: 2017-10-13 19:06:06.153 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0 2017-10-13 19:06:06.153 [INF] LTND: Primary chain is set to: bitcoin
lnd: 2017-10-13 19:06:06.416 [INF] BTCN: Loaded 1825 addresses from file 'C:\Users\Richard\AppData\Local\Lnd\data\testnet3\bitcoin\peers.json'
lnd: 2017-10-13 19:06:06.558 [INF] CMGR: DNS discovery failed on seed x19.testnet-seed.bitcoin.jonasschnelli.ch: lookup x19.testnet-seed.bitcoin.jonasschnelli.ch: no such host 2017-10-13 19:06:06.558 [INF] CMGR: DNS discovery failed on seed x19.seed.tbtc.petertodd.org: lookup x19.seed.tbtc.petertodd.org: no such host
lnd: 2017-10-13 19:06:06.603 [INF] CMGR: 1 addresses found from DNS seed testnet-seed.bluematt.me
lnd: 2017-10-13 19:06:06.827 [INF] CMGR: 25 addresses found from DNS seed testnet-seed.bitcoin.schildbach.de
lnd: 2017-10-13 19:06:06.886 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:06:06.887 [INF] BTCN: Syncing to block height 1126091 from peer 35.199.154.3:18333 2017-10-13 19:06:06.887 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:06:07.412 [INF] LNWL: Opened wallet
lnd: 2017-10-13 19:06:08.539 [INF] LNWL: The wallet has been unlocked without a time limit
lnd: 2017-10-13 19:06:08.543 [INF] LTND: LightningWallet opened
lnd: 2017-10-13 19:06:08.552 [INF] LNWL: Started rescan from block 00000000000000b57db6ee38e2318105ebbc87e4e7a7999e2e9798592a447730 (height 930000) for 5 addresses
lnd: 2017-10-13 19:06:08.562 [INF] RPCS: RPC server listening on 127.0.0.1:10009
lnd: 2017-10-13 19:06:08.564 [INF] LTND: Waiting for chain backend to finish sync, start_height=930000 2017-10-13 19:06:08.564 [INF] RPCS: gRPC proxy started at localhost:8080
lnd: 2017-10-13 19:06:08.629 [INF] LNWL: Catching up block hashes to height 930000, this might take a while
lnd: 2017-10-13 19:06:08.636 [INF] LNWL: Done catching up block hashes 2017-10-13 19:06:08.636 [INF] LNWL: Finished rescan for 5 addresses (synced to block 00000000000000b57db6ee38e2318105ebbc87e4e7a7999e2e9798592a447730, height 930000)
lnd: 2017-10-13 19:07:51.886 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:07:51.886 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:07:52.213 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:07:57.415 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:07:57.416 [INF] BTCN: Syncing to block height 1126093 from peer 35.199.154.3:18333 2017-10-13 19:07:57.416 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:08:12.620 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:08:32.615 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:08:52.620 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:09:12.629 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:09:32.625 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:09:42.415 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:09:42.415 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:09:48.268 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:09:48.268 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:09:48.268 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:09:50.811 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:09:50.811 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:09:50.811 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:09:52.624 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:09:56.374 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:09:56.375 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:09:56.375 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:09:58.543 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:09:58.543 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:09:58.543 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:10:04.174 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:10:04.175 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:10:04.175 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:10:08.363 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:10:08.363 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:10:08.363 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:10:12.282 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:10:13.876 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:10:13.876 [INF] BTCN: Syncing to block height 1126093 from peer 35.199.154.3:18333 2017-10-13 19:10:13.876 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:10:32.288 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:10:52.282 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:11:12.309 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:11:32.295 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:11:43.877 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:11:43.877 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:11:49.643 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:11:49.644 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:11:49.644 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:11:52.276 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:11:52.413 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:11:52.413 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:11:52.413 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:11:58.198 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:11:58.198 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:11:58.198 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:12:01.212 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:12:01.212 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:12:01.212 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:12:06.999 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:12:07.000 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:12:07.000 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:12:11.162 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:12:11.162 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:12:11.162 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:12:12.332 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:12:16.891 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:12:16.891 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:12:16.891 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:12:22.399 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:12:22.399 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound) 2017-10-13 19:12:22.399 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:12:28.305 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:12:28.306 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:12:28.306 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:12:32.311 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:12:32.922 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:12:32.922 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:12:32.922 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:12:38.785 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:12:38.786 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:12:38.786 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:12:43.749 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:12:43.749 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:12:43.750 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:12:49.635 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:12:49.636 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:12:49.636 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:12:52.295 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:12:55.478 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:12:55.478 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:12:55.478 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:13:01.202 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:13:01.203 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:13:01.203 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:13:05.386 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:13:05.386 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:13:05.386 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:13:10.942 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:13:10.943 [INF] BTCN: Syncing to block height 1126206 from peer 35.199.154.3:18333 2017-10-13 19:13:10.943 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:13:12.386 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:13:32.326 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:13:52.318 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:14:12.365 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:14:32.328 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:14:52.324 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:14:55.942 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:14:55.942 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:15:01.430 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:15:01.431 [INF] BTCN: Syncing to block height 1126324 from peer 35.199.154.3:18333 2017-10-13 19:15:01.431 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:15:12.332 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:15:32.328 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:15:52.322 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:16:12.340 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:16:32.331 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:16:46.430 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound) 2017-10-13 19:16:46.430 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:16:52.316 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:16:52.355 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:16:52.356 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:16:52.356 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:16:58.039 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:16:58.039 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound) 2017-10-13 19:16:58.039 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:17:03.902 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:17:03.902 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:17:03.902 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:17:07.078 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:17:07.078 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:17:07.078 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:17:12.320 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:17:13.656 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:17:13.657 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:17:13.657 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:17:17.363 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:17:17.363 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:17:17.363 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:17:23.156 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:17:23.157 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:17:23.157 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:17:26.393 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:17:26.393 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:17:26.394 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:17:31.987 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:17:31.988 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:17:31.988 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:17:32.327 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:17:35.023 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:17:35.023 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:17:35.023 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:17:40.576 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:17:40.577 [INF] BTCN: Syncing to block height 1126632 from peer 35.199.154.3:18333 2017-10-13 19:17:40.577 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:17:52.317 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:18:12.340 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:18:32.350 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:18:52.343 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:19:12.345 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:19:25.576 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:19:25.576 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:19:31.241 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:19:31.242 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:19:31.242 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:19:32.340 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:19:34.126 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:19:34.127 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound) 2017-10-13 19:19:34.127 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:19:39.759 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:19:39.760 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:19:39.760 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:19:44.027 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:19:44.027 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:19:44.027 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:19:50.161 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:19:50.162 [INF] BTCN: Syncing to block height 1210149 from peer 35.199.154.3:18333 2017-10-13 19:19:50.162 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:19:52.347 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:19:52.515 [WRN] BTCN: Header doesn't pass sanity check: block target difficulty of 00000000ffff0000000000000000000000000000000000000000000000000000 is higher than max of 0000000000000202f00000000000000000000000000000000000000000000000 -- disconnecting peer 2017-10-13 19:19:52.515 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:19:52.515 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:19:58.196 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:19:58.197 [INF] BTCN: Syncing to block height 1126861 from peer 35.199.154.3:18333 2017-10-13 19:19:58.197 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:20:12.347 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:20:32.342 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:20:52.349 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:21:12.355 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:21:32.346 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:21:43.196 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:21:43.196 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:21:48.839 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:21:48.840 [INF] BTCN: Syncing to block height 1127112 from peer 35.199.154.3:18333 2017-10-13 19:21:48.840 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:21:52.344 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:22:12.369 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:22:32.359 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:22:52.353 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:23:12.358 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:23:32.348 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:23:33.841 [INF] BTCN: Lost peer 35.199.154.3:18333 (outbound)
lnd: 2017-10-13 19:23:33.841 [WRN] BTCN: No sync peer candidates available
lnd: 2017-10-13 19:23:39.314 [INF] BTCN: New valid peer 35.199.154.3:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
lnd: 2017-10-13 19:23:39.315 [INF] BTCN: Syncing to block height 1127294 from peer 35.199.154.3:18333 2017-10-13 19:23:39.315 [INF] BTCN: Downloading headers for blocks 930001 to 1000007 from peer 35.199.154.3:18333
lnd: 2017-10-13 19:23:52.349 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:24:12.466 [INF] RPCS: [listchannels] fetched 0 channels from DB
lnd: 2017-10-13 19:24:32.372 [INF] RPCS: [listchannels] fetched 0 channels from DB

show full transaction IDs on "Transactions" tab

I am trying to check the status of my (on chain) transactions independently

Error: panic: Rollback failed

On windows 8.1:

lnd Error: panic: Rollback failed: truncate C:\Users\fresheneesz\AppData\Local\Lnd\data\testnet3\bitcoin\reg_filter_headers.bin: Access is denied. goroutine 28 [running]:
lnd Error: github.com/lightningnetwork/lnd/vendor/github.com/lightninglabs/neutrino.(*blockManager).handleHeadersMsg(0xc0424d42a0, 0xc042166bb0) /Users/bryanvu/work/src/github.com/lightningnetwork/lnd/vendor/github.com/lightninglabs/neutrino/blockmanager.go:1085 +0x1d3a github.com/lightningnetwork/lnd/vendor/github.com/lightninglabs/neutrino.(*blockManager).blockHandler(0xc0424d42a0) /Users/bryanvu/work/src/github.com/lightningnetwork/lnd/vendor/github.com/lightninglabs/neutrino/blockmanager.go:347 +0x434 created by github.com/lightningnetwork/lnd/vendor/github.com/lightninglabs/neutrino.(*blockManager).Start /Users/bryanvu/work/src/github.com/lightningnetwork/lnd/vendor/github.com/lightninglabs/neutrino/blockmanager.go:200 +0x11b

Feature Request: Report mempool transactions before they're confirmed

I'm used to things like Electurm and Bitcoin Core that find relevant transactions in the mempool and show pending unconfirmed transactions in my history immediately. I'd imagine this is possible with this client too. This client doesn't report transactions until after they've confirmed - would be super helpful if it did!

Cant create channel ("not enough witness outputs...")

I click the "create channel" button and nothing happens.

Looking in the log I can see "FNDG: Initiating fundingRequest.. " and later on in the line "..not enough witness outputs to create funding transaction.."

I then try to re-send the funds to from->to lightning wallet address again and get "insufficient funds to construct transaction"

Maybe not enough confirmations for the initial transaction from the testnet faucet?

Problem syncing chain (testnet overloaded?)

I'm seeing following message in the log: No sync peer candidates available

It was syncing fine at first but slowly.

Could this be a testnet capacity issue? Is there a way to connect the app to my local testnet node for syncing?

panic after unknown message received.

I had a bunch of 'unknown message received' errors followed by go panic.
A restart was required to get the wallet app going again.

lnd: 2017-10-16 22:16:04.870 [ERR] PEER: unknown message received from peer xxx.xxx.xxx.xxx:9735
lnd: 2017-10-16 22:16:04.988 [ERR] PEER: unknown message received from peer xxx.xxx.xxx.xxx:9735
lnd Error: panic: runtime error: index out of range goroutine 1414 [running]:
github.com/lightningnetwork/lnd/lnwallet.genHtlcSigValidationJobs(0xc4210c8320, 0xc4208bafc0, 0xc42000c180, 0x1, 0x1, 0xc420189268, 0xc4201892b8, 0x1000000, 0xc4202e2e00, 0x20) /Users/bryanvu/work/src/github.com/lightningnetwork/lnd/lnwallet/channel.go:2631 +0x8a0
github.com/lightningnetwork/lnd/lnwallet.(*LightningChannel).ReceiveNewCommitment(0xc4212342c0, 0xc420c9ac90, 0xc42000c180, 0x1, 0x1, 0x0, 0x0) /Users/bryanvu/work/src/github.com/lightningnetwork/lnd/lnwallet/channel.go:2723 +0x5cf
github.com/lightningnetwork/lnd/htlcswitch.(*channelLink).handleUpstreamMsg(0xc421602000, 0x1322660, 0xc42107c980) /Users/bryanvu/work/src/github.com/lightningnetwork/lnd/htlcswitch/link.go:776 +0xc8a
github.com/lightningnetwork/lnd/htlcswitch.(*channelLink).htlcManager(0xc421602000) /Users/bryanvu/work/src/github.com/lightningnetwork/lnd/htlcswitch/link.go:466 +0xcb5
created by
github.com/lightningnetwork/lnd/htlcswitch.(*channelLink).Start /Users/bryanvu/work/src/github.com/lightningnetwork/lnd/htlcswitch/link.go:272 +0x116

--edit--
Shortly after restart it happened again, 7 unknown messages from the same peer followed by the same panic.

ATPL: Autopilot Agent starting 2017-10-15 20:52:04.767 [ERR] DISC: Router rejected channel edge: pkScript mismatch

I received this error in the log when I started the Lightning App. Any idea what this indicates?

ATPL: Autopilot Agent starting 2017-10-15 20:52:04.767 [ERR] DISC: Router rejected channel edge: pkScript mismatch: expected 00209121200672048a92798683b436b498a36f5fa00a3504b680149fb60d14427c53, got 002083fa767a13244df8c33bb5f279a8b275f397d4a974eca76b43f88b0c0eae4e4c 2017-10-15 20:52:04.767 [ERR] FNDG: channel announcement failed: pkScript mismatch

Force close fallback unresponsive

When a channel is shown as "inactive" the user should be able to clic on the x within the channels row and still attempt to close. The internal logic should detect that the peer we have the channel open with isn't currently online/inactive and prompt the user to confirm that they want to attempt a force close. A force close differs from a regular close in that lnd will need to wait a relative CSV delay before sweeping.

This worked in the past, so a regression must have been introduced recently (ish).

Uncaught Error: Module version mismatch. Expected 50, got 48.

Hi @casesandberg! While installation I was asked to install additional packages:

npm install react, react-dom, grpc

and after that I hit the problem, any idea how it might be solved?:

remote.js:217 Uncaught Error: Module version mismatch. Expected 50, got 48.
Error: Module version mismatch. Expected 50, got 48.
    at Error (native)
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:173:20)
    at Object.Module._extensions..node (module.js:583:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:173:20)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/private/tmp/lightning-app/node_modules/grpc/src/node/src/grpc_extension.js:38:15)

Unable to close ChannelPoint because Channel ID not found

I'm unable to remove a Channel that shows up automatically after I launch the application. The channel ID displays is CID:0 and it never closes even if I attempt to click the 'Close' button. Also I don't get the confirmation prompt as I try to close this channel (where it asks the user 'Are you sure you would like to close this channel?' Are we supposed to get this confirmation always on attempting to close any channel?)

Also does this have anything to do with the 'autopilot' functionality newly added?

CID 0 when I launch the application for the first time as soon as the chain sync completes and I open the 'Channels' page I get this channel with CID 0 that I can't close.

On attempting to close the channel:

Logs:

lnd: 2017-10-15 17:37:01.768 [ERR] RPCS: [closechannel] unable to close ChannelPoint(438d819095d015a6c1d7497d185966c214ffdaffaabe68cba5ccd5d5a2fd4a03:1): channel with chan_id=034afda2d5d5cca5cb68beaaffdaff14c26659187d49d7c1a615d09590818d42 not found lnd: 2017-10-15 17:37:06.805 [INF] RPCS: [listchannels] fetched 5 channels from DB lnd: 2017-10-15 17:37:10.501 [ERR] RPCS: [closechannel] unable to close ChannelPoint(438d819095d015a6c1d7497d185966c214ffdaffaabe68cba5ccd5d5a2fd4a03:1): channel with chan_id=034afda2d5d5cca5cb68beaaffdaff14c26659187d49d7c1a615d09590818d42 not found lnd: 2017-10-15 17:37:26.804 [INF] RPCS: [listchannels] fetched 5 channels from DB lnd: 2017-10-15 17:37:46.805 [INF] RPCS: [listchannels] fetched 5 channels from DB

LND testnet faucet

Please add LN testnet faucet to the Readme

Feature Request: Channel info

There should be some additional info you can access about a channel:

• The channel address - This one's really important. Is the CID a standard that other people (like eclair) should be using? Right now I can't even tell if I've already connected to an address because it doesn't show the address you're connected to.
• Whether the channel was created by autopilot or not
• Fees and fee rates
• Which transaction(s) funded/closed the channel
• Which lightning transactions have been sent through it
• How long its been open for (or date created)
• the transaction history/total volume for the channel
• If its closing, whether its waiting for a normal closing transaction to confirm vs waiting for a time-lock refund transaction to resolve

Would it also be possible to know how much of the network you can access through your channel(s)? It would be interesting/useful to know that your channels give you access to X% of the network of known endpoints, and which of your connections give you access to what percent. If channels are charging fees to create or send, that info would be useful to evaluate whether you should keep one open over another.

From bryanvu: "Some of this data may be considered advanced, so this information should probably be split into a basic channel detail and a more advanced one."

Error building 'boringssl' on linux

While running npm run setup, this error occurs:

make: Entering directory '/home/whythat/00_util/lightning-app/apps/desktop/node_modules/grpc/build'
  CC(target) Release/obj.target/boringssl/third_party/boringssl/crypto/bio/fd.o
../third_party/boringssl/crypto/bio/fd.c: In function ‘fd_ctrl’:
../third_party/boringssl/crypto/bio/fd.c:192:11: error: this statement may fall through [-Werror=implicit-fallthrough=]
       num = 0;
       ~~~~^~~
../third_party/boringssl/crypto/bio/fd.c:193:5: note: here
     case BIO_C_FILE_SEEK:
     ^~~~
cc1: all warnings being treated as errors
make: *** [boringssl.target.mk:439: Release/obj.target/boringssl/third_party/boringssl/crypto/bio/fd.o] Error 1

GCC 7.2.0.
System Linux 4.9.51-1-MANJARO.

Force close fails if other channel participant is offline

App crashes when overwhelmed with Log output

If log output exceeds a certain rate of lines per second, the app will crash.

Unable to query bootstrapper BOLT-0010 DNS Seed

After (successfully) syncing the chain the client doesn't establish any channels.

The log shows:

lnd: 2017-10-13 16:54:21.005 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
lnd: 2017-10-13 16:54:21.009 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [nodes.lightning.directory]
lnd: 2017-10-13 16:54:21.319 [ERR] DISC: Unable to query bootstrapper BOLT-0010 DNS Seed: [nodes.lightning.directory]: lookup _nodes._tcp.nodes.lightning.directory: dnsquery: DNS server failure. 2017-10-13 16:54:21.319 [INF] DISC: Obtained 0 addrs to bootstrap network with
lnd: 2017-10-13 16:54:22.697 [INF] RPCS: [listchannels] fetched 0 channels from DB

(repeats every couple seconds)

I've tried restarting the client and turning off windows firewall.

I can ping the server from a command prompt without any problems:

C:\>ping nodes.lightning.directory

Pinging nodes.lightning.directory [45.77.115.33] with 32 bytes of data:
Reply from 45.77.115.33: bytes=32 time=121ms TTL=56
Reply from 45.77.115.33: bytes=32 time=120ms TTL=56
Reply from 45.77.115.33: bytes=32 time=120ms TTL=56
Reply from 45.77.115.33: bytes=32 time=123ms TTL=56

Ping statistics for 45.77.115.33:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 120ms, Maximum = 123ms, Average = 121ms

System: Windows 7 64bit

Wallet balance doesn't auto-update dynamically after completion of chain sync

The Lightning app's wallet balance displays as '0' after every sync completes. The ideal result would be to auto-update and display the correct balance after the sync completes instead of display it as '0'. The user currently has to click on the balance or 'Channel' screen (for example pay, request etc) in order to view the updated balance.

0 balance after sync:

Balance updated on clicking 'Channel':

Handle lnd.conf gracefully

Currently, in order to get the app's lnd to use the default lnd configuration and to ignore any other pre-existing lnd installations, the app is configured to look for lnd.conf in a directory where it shouldn't exist. This should be handled either by not looking for lnd.conf or having the app look for an lnd.conf in a different directory than lnd normally uses.