Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
7

I agree with Alex Bosworth and I have pointed this out about one year ago when I have filed an issue about the strategy used by the LND autopilot which basically looks for nodes with a high channel count. This is one of the reasons why I have created a standalone autopilot and provided an integration for c-lightning. There are several kind of information we ...


4

Yes, a channel opening involves creating and signing 3 transactions, and broadcasting just one. The transaction to be broadcast funds the channel, and spends to a multisig output. It is signed by whomever chooses to fund the channel. When this funding tx receives sufficient confirmation, the channel is considered open. This multisig output is spent by two ...


3

First of all we should understand the difference between capacity of a channel and its balance. The capacity is the amount of Bitcoin provided to that channel. The balance encodes the amount of bitcoin which each channel partner owns in the channel. so the sum of the balances will always be the total capacity of the channel. Second we currently do not ...


3

In your scenario you would like to create a payment channel with user 1 and 2 contributing (on-chain) and receiving (off-chain, in the payment channel) the following amounts: User 1: 2 btc User 2: 1 btc To open and fund the channel accordingly, you therefore create the following funding transaction: Input 0: 2 btc from user 1 Input 1: 1 btc from user 2 ...


3

Stuff like this can usually be found in the lightning-rfc aka BOLT (basics of lightning technologies) which is the formal protocol specification. Currently channel capacity can't succeed 1/6 of a Bitcoin. However for BOLT1.1 (the next version of the protocol) it was agreed that this limit should be dropped (if both nodes of a channel agree to do so). Single ...


3

A lightning funding transaction is a P2WSH transaction, which appears on chain as paying to some random-looking script hash, but the redeemScript which can unlock and spend the money is not revealed on chain until the transaction gets spent (which is when the channel gets closed in Lightning's case). You can recreate the redeemScript if you know the funding ...


2

They can only be detected when force closed and there are still pending htlcs otherwise they look like a spend from a 2-2 multisig wallet. I've been told some people try to do chain analysis and machine learning to predict private channels. I highly doubt that this is reasonably possible. Although there is one thing to consider. If a node has public and ...


2

A funding transaction is one where some money is paid into a P2WSH transaction output, where the redeeemScript is a 2-of-2 multisig between the two participants. No other information is provided. Technically, even the redeemScript for the funding is not revealed until the funding transaction output is spent (channel closed), which makes it less obvious that ...


1

Channel funding (and the distribution of funds) is determined at the time of channel opening. Once opened, a party cannot ‘add funds’ to the channel, this would require opening a new channel. If you opened the channel and did not specify that some number of sats should be pushed to the remote node at the time of opening, then the channel will open with the ...


1

lncli pendingchannels gives a pendingChannelRespnse which might have the pending_open_channels parameter. This contains an array of PendingOpenChannel objects. According to the documentation they should have a parameter confirmation_height which is the height of the blockchain at which the funding TX has enough confirmations (the max of your and your ...


1

Not all implementations support multiple channels between two nodes. That is why I would advise against that practice. Also I do not really see an advantage of having two channels. We don't have Atomic multipath routing yet so in general it makes more sense to have larger channels. Only counter argument I see is that one channel can only have 483 htlcs ...


1

Here there are some properties: Node reliability: On-line connected 24/7. History: when the node came online for first time. Routing: How many channels has the node. Capacity: How much capacity can the handle through channels


1

I will only give the answer for a mutual close. The situation for unilateral (forced) channel close should be similar only that you have too look in the commitment transactions and that you have to look for local_delayedpubkey instead of localpubkey. You can look at BOLT 03: Transactions where it is specified. In particular the section closing transaction. ...


1

What is happening when a channel is pending when opened? How long does it usually take? A node establishes a channel by sending an open_channel message to its desired peer. This message specifies the parameters under which the channel will operate (e.g. the number of bitcoin the channel will be funded with and the cost to route payments through the channel)....


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