6

If you recommend "Mastering the Lightning Network" in chapter 2 you find a table of possible Lightning Network implementations: Application Device Lightning Node Bitcoin Node Keystore Eclair Mobile Mobile Lightweight Electrum Self-Custody Breez Wallet Mobile Full Node Neutrino Self-Custody Phoenix Wallet Mobile Lightweight Electrum Self-Custody ...


5

Walletbalance is showing your on-chain balance of a lightning wallet. Regarding channel balances (locked on layer 2 and not available onchain): local balance is your local balance that you can spend on lightning network remote balance is balance in your channels but it's being owned by the other party in the channel, this is the amount you are able to ...


4

In each of your channels, you have a local balance. This is the balance that is yours in that channel. The counterparty of the channel has the remote balance. All lightning transactions change these balances with each one resulting in their sum being the same and matching the channel capacity. As all transactions in that channel just end up changing the ...


3

The Bitcoin Core wallet and the LND wallet are completely separate wallets. LND relies on Bitcoin Core as a source for the blockchain data, nothing more. The profitability of your node depends on where it is situated in the network's topology. If you want to run Lightning to earn money, you will need to pick reliable nodes as channel partners, but also try ...


2

Create an invoice for yourself: lncli addinvoice <amt> Pay the invoice specifying the outgoing channel and the last hop to take before paying you: lncli payinvoice --allow_self_payment --outgoing_chan_id <outgoing_chan> --last_hop <last_hop> <payreq_from_1> To get the outgoing channel id use lncli listchannels --active_only. I ...


2

Answer by Oliver Gugger (guggero): You can use the dumpchannels command of chantools: https://github.com/guggero/chantools#dumpchannels That will show you the commitment transaction inputs and outputs for both parties. Remember to shut down lnd first, otherwise chantools will block on trying to open the channel DB.


2

It is standard accounting practice in the US to show negative numbers in parentheses. I'd guess that the values here in parentheses and red show outgoing payments, while the ones in white without parentheses show incoming payments.


2

Assume the lightning network wants to support 100k payments per second globally. Now every time a payment is attempted, aborted or settled the balance of almost every channel in the payment flow changes. Assuming 5 channels being involved in a payment (and assuming no failed payments as the balance values would magically instantly known to all peers) this ...


2

The routing fees are charged with successful forwardings. Let's say you received 11 sats on one channel and forward 10 on another you have earned 1 Satoshi. This satoshi increases the total balance of your node and is technically added to the incoming channel. You could of course account the fee to the outgoing channel as that one defines the fee your node ...


1

The error message is about trying to update the onchain fees in the case of a force close. The onchain fees are renegotiated with your peer from time to time, so that you are safe in case your partner becomes unresponsive. From your log file, it looks like your channel has most of its balance on the remote side and thus you could not afford the higher ...


1

I am thinking of running my own lightning node in testnet. Going through the tutorials it seems the lightning node needs to be connected to bitcoin node inorder to get connected to bitcoin network. But running a full bitcoin node like bitcoind seems out of my scope as I don't want invest and maintain it. A Bitcoin testnet node block chain occupies less than ...


1

Your experience was coincidental, there's no requirement for bitcoind to be listening on a public interface while using lightningd.


1

I got a sweep TX (from a force closed channel) stuck, also due to low fees. This answer is inspired by OPs answer. I got it working with: lncli openchannel \ --sat_per_byte=${fees per byte for the funding transaction of the new channel} \ --min_confs=0 \ ${remote nodes id} \ ${local amount} The --min_confs=0 part is the important bit, it allows lnd to use ...


1

LND has two API interfaces: On port 8080 is a REST RPC interface On port 10009 is a GRPC interface. The REST interface on 8080 needs a macaroon file and an optional tls certificate. You can use CURL like this: MACAROON_HEADER="Grpc-Metadata-macaroon: $(xxd -ps -u -c 1000 ~/.lnd/admin.macaroon)" curl -X GET --cacert ~/.lnd/tls.cert --header "...


Only top voted, non community-wiki answers of a minimum length are eligible