New answers tagged

4

You basically answered the question already yourself. Besides the 1% channel reserve you as the funder are responsible for paying onchain fees in case you need to force close the channel by spending the commitment transaction. C Lightning (and lightning nodes in general) are rather overestimating onchain fees as they cannot rely on the fact that the fees ...


1

How then further transactions can happen without waiting for the secret R? Does it mean that the HTLC contracts get simply "carried over" in the subsequent transactions between A and B? Yes, that is correct. You go on adding HLTC outputs in the commitment transactions as more and more HTLCs are added, and delete those HTLCs that are either fullfiled with a ...


3

Lightning invoices are signed by the node issuing the invoice in order to verify the signature we need to know the node id. Thus it is included in the invoice. Lightning nodes provide an API to decode invoices. In c-lightning you can do (lnd below!) lightning-cli decodepay ...


0

Everything but the last Comand looks correct. There is no command channel in c-lightning. In order to open a channel you need to execute cli/lightning-cli fundchannel id satoshi [feerate] [announce] [minconf] Fund channel with {id} using {satoshi} (or 'all') satoshis, at optional {feerate}. Only use outputs that have {minconf} confirmations. The thing ...


0

An HTLC always "freezes" funds. It is a smart contract that says "here is the balance and a hash. If you give me the preimage of that hash within time T, the balance is yours. Otherwise I can take it back.". You can then use this functionality to achieve an atomic swap by going through a service node that is active in both networks and offers to swap ...


2

You will find the answer to your question in BOLT 02 in the section about the update_fulfill_htlc message from there I quote: If the payment_preimage value in update_fulfill_htlc doesn't SHA256 hash to the corresponding HTLC payment_hash [the receiving node] MUST fail the channel. This goes for every local HTLC so if Charlie sends the wrong ...


3

I guess this has historical reasons. The short channel ids where there first in the onion format. C Lightning even today does not support multiple channels between 2 nodes. Lnd on the other hand does. That is why lnd developers started to switch the channel if a second channel with enough balance between the nodes existed. Later on it was agreed to add the ...


2

I am gonna need to use prude mod and began the download of the chain starting from march 2018 as recquired by lnd, my question is which bitcoin client is able to do that and how to configure it for this procedure ? I don’t believe any client can do this: how will your node know if a UTXO from before March 2018 was valid if it hast verified the full ...


0

The keyword you are probably looking for is neutrino as explained in the article by lightning labs. From the conclusion of the article I quote: We’re excited to have released the first implementation of BIP 157/158-compliant Neutrino clients in lnd 0.5 and in the Lightning App alpha. While these initial releases are for testnet, mainnet Neutrino is in ...


0

Lightning Labs manages the lnd node(s) running on the private (closed source) server you are correct. Your node receiving Loop payments on LN will need a route to their node, however part of the service Loop is providing (and charges for) requires them to keep channels balanced to pay your invoices or accept payments on demand. The closed source ...


0

Can my LN channel for some amount "X" receive a LN payement larger than "X" No, you can only receive payments until the entire channel capacity ("X") has been pushed to you side of the channel. At that point, you will no longer have incoming capacity. ..or receive multiple small payments that exceed "X"? You could receive multiple payments that exceed "...


0

I wasn't aware until now that their server is closed source. But it appears to be like that indeed. Interesting and understandable choice, I guess they do want to earn money after all. Let's hope it'll be open sourced/reconstructed eventually. With regards to your more technical questions, I don't know what nodes their servers run on, but the idea of the ...


4

Currently it cost $0.000116736 USD (1 satoshi) fee to make a transaction on lightning. This is incorrect; there is no set price for sending a LN transaction. Each node can define its own policy for forwarding a payment through the network (base fee rate, plus a small percentage of the amount forwarded), so the fee paid will depend on the payment route ...


0

Without detailed log files I can only guess the exact reason why you see this behavior. Two likely things come to my mind: 1.) Your node might have routed smaller payments. So in case you have outgoing capacity on one channel and incoming on another one someone might have used that to rout a payment. which would move some satoshi from one channel to the ...


2

Listen: This specifies the interfaces to listen to for incoming connections to your node. This will allow other nodes to establish inbound connections to your lnd node. If you want to listen to all ipv4 connections on port 9735, you can use listen = 0.0.0.0:9735 External IP: Adding an external IP advertises your node to the network. If you'd like to signal ...


1

Lnd itself does as far as I remember not provide an api for rebalancing channels. However there is the lndmanage repository that uses the lnd api to provide a pretty strong rebalancing tool https://github.com/bitromortac/lndmanage Such rebalancing will cost you routing fees as they are regular (circular) payments. That being said it is not clear why you ...


2

So in Bitcoind you can define authentication via an rpc interface (remote procedure call). In the config file of Bitcoind which is usually located in ~/.bitcoin/bitcoin.conf you can set the values for rpcuser=bitcoind_rpc_user_string rpcpass=bitcoind_rpc_password_string Obviously you should select other values than the ones in this answer / question. You ...


0

rpc_pb2_grpc is an official lnd API. This is a low-level interface that supports essentially all the same calls you can make through lncli. If you decide to use this one - I can suggest you start with this official tutorial. lnd_grpc is a third-party wrapper on top of rpc_pb2_grpc, which introducing additional level of abstraction and hides some things from ...


1

lncli listchannels will tell you the local balance and remote balance of each channel (in satoshis). You could simply sum up the the balances of all your channels to find the total outgoing capacity (local balance) and incoming capacity (remote balance) you have. Here is a one-liner that reports the sum of your inbound capacity (requires jq): lncli ...


Top 50 recent answers are included