New answers tagged

0

I think the reason is that the authors had watchtower services in mind. Which I guess people agree are needed in the poon dryja channel construction. When you use the same keys for commitment transaction watchtower services can basically learn which payments in which amounts go through the channels. And start an attack on the privacy of people making and ...


1

Click the three dots in the top right corner, tap "Network Info". Your NodeId is visible on this screen Now, go to the URL ip.tyk.nu to find your IP address. Now, in a Linux prompt (or WSL), install the PyPI qrcode package. On Ubuntu, it is available in the python3-qrcode package. Now, execute this command (substitute the values you just learnt): echo -...


1

Check the Script wiki would be helpful. I once did this by hand, here's the process. First, put the unlocking script on top of the locking script, <remotehtlcsig> <payment_preimage> # To remote node with revocation key OP_DUP OP_HASH160 <RIPEMD160(SHA256(revocationpubkey))> OP_EQUAL OP_IF OP_CHECKSIG OP_ELSE <remote_htlcpubkey&...


2

There are three ways in which that offered HTLC output can be redeemed: Revocation using the revocation public key (the example you mentioned), redeemed using a valid payment preimage or back to the local node after the timeout. Redeemed using a valid pre-image by remote node: The stack starts at <remotehtlcsig> <payment_preimage> Since the ...


1

I think you have answered your question yourself in the last question that you raised. The problem with not publishing Tu0 is that the funder of the channel could double spend the input of Tu0 and in that case "steal" all the money from the channel. so with eltoo we still need the bitcoin network / blockchain give proof of the existence of funds in the 2-2 ...


5

The onion routing in Lightning is based on the Sphinx Mix Format described in this paper. The situation is different from Tor We don't have entry and exit nodes in Lightning as all nodes are inside the Network. In Tor a new connection along the path is as easy as creating a TCP socket between the tor routing nodes. In Lightning a payment channel with ...


2

The nodes are listed in lexicographical order after compressed DER encoding. It is not possible to tell from the public information about a channel who requested to open it. The ordering is required so that signature verification of a channel_announcement message always passes. If intermediate nodes were able to rearrange the order of information within the ...


4

Yes. Unfortunately this is true. Using push-amt means that you send over an amount to the other side wich they own. While it takes place offhand it is final in a similar way as sending Bitcoin to an address. The only way I see to get your funds back is if you talk to the owners of the nodes you opened channels with explain them the situation and ask to get ...


0

I found the problem, in the bip143 tx digest preimage, the scriptCode needs to be preceded by the length of the scriptCode. In this case 0x47


0

With c-lightning there are no restrictions to use as many as you want LN nodes with single bitcoind (i am hosting LN nodes as a service, and by default these use one single bitcoind, just with different RPC credentials). I would like to point to these instructions: https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md#using-bitcoind-or-...


1

Just use lightning-cli close id the implementation will first try to do a mutual close. Both lightning nodes will use the fee estimator from Bitcoind to suggest fees. If they don't agree there is a communication protocol defined in the BOLTs that they will eventually find a local agreement between themselves. This protocol is described under the section ...


1

I just tried to chase that edge case down in the BOLTs. We find at https://github.com/lightningnetwork/lightning-rfc/blob/master/02-peer-protocol.md#cltv_expiry_delta-selection if an HTLC it has fulfilled is in either node's current commitment transaction, AND is past this fulfillment deadline: MUST fail the channel. While the htlc below the dust limit ...


1

If it's a mutual close, the HTLC will be resolved prior to closing of the channel. If the close is unilateral, then yes the HTLC which is below the dust_limit_satoshi cannot be resolved. When you are adding HTLC below the dust_limit_satoshi there is some trust element involved and hence we deduct the HTLC amount from our "balance" as a fee in the commitment ...


1

This is a tricky question as it tackles the difference between what the protocol supports and what implementations provider as an API. On a protocol level channels are enabled / disabled via an update message on the gossip Protocol. Nodes SHOULD set the disabled flag and send such a message if they are shutting down or turning (shortly) off for maintenance....


2

You can do sudo apt-get install -y software-properties-common sudo add-apt-repository -u ppa:bitcoin/bitcoin sudo add-apt-repository -u ppa:lightningnetwork/ppa sudo apt-get install bitcoind lightningd If you don't want to add external repositories you can flollow the clightning docs from https://github.com/ElementsProject/lightning/blob/master/doc/INSTALL....


2

There seems to be a mix in notation. Payment channels on lightning are bidirectional by design. However that does not mean that funds can always flow on both directions. Currently channels are funded by one party an as such can not receive funds after opening. As was mentioned in the comment what you mean is called a dual funded channel. As soon as you use ...


1

To answer your question two things have to be known: Routing fees are always charged from the recipient to the sender as the fee rate of later packages impacts earlier routing decisions. Nodes get paid a routing fee to forward a package on an outgoing channel. The first remark is not of importance for your case as the path only includes 1 routing node. ...


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 ...


3

as explained here I showed that the betweeness centrality of a node on the fee graph is proportional to the expected routing fees which again is proportional to the throughput of your node. So taking your throughput and dividing it by your betweeness centrality score should give you a rough estimate of how much throughput is handled by the network. That ...


0

Nodes can choose to publish their throughput, but they can also stay private and go very anonymous by using the tor network for their node, this website aggregate most of the public node data https://1ml.com/statistics as they said: The statistics are aggregated and calculated from multiple nodes within the Lightning Network. Due to the decentralized ...


3

If you look at git blame of BOLT 03 you can track the sentence regarding the locktime down to this commit: https://github.com/lightningnetwork/lightning-rfc/commit/f1eaa2544665c9b85a2fd95be9c83dad45888982 luckily the author gave a good explanation in the commitment message in git of why the 0x20 was introduced for the upper 8 bits in the locktime field (I ...


0

It's a case when a local node closes the channel unilaterally with broadcasting its local commitment transaction that contains to_local output below. This output is spent by a transaction with nSequence field set to to_self_delay (which can only be valid after that duration has passed.) OP_IF # Penalty transaction <revocationpubkey> OP_ELSE ...


1

If you look at https://blockstream.info/address/bc1qdv0fk4c73fem89s708pzdny8q25d7k5nrckckp87c8alwaw803fq3mqrpz you will see that there are two transactions. The first one https://blockstream.info/tx/943f18e17aa2ba716f2d13785268a1bd6b25c39d2718f3b4785559a5eeaba883 is the funding TX to open the payment channel included in block 587093 (at least according to ...


Top 50 recent answers are included