4

The Current Problem The major challenge in the current routing mechanism is finding channels with sufficient balance on one side of a node to forward an incoming payment. To be more descriptive, the channel_announcement or the channel_update messages that are broadcasted contains the short_channel_id through which lightning nodes can look up the transaction ...


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


1

The 4000000 Weight Units limitation is the maximum Bitcoin block size limit (link to the BIP). The 400000 Weight Units limitation is the limit for a transaction to be standard (hence relayed). The penalty transaction is crucial to the security of Lightning Network channels, so you need a transaction which can be relayed, hence a transaction which size is ...


1

First of all I think there seems to be a small confusion about the notation. One does not spend a transaction but transaction outputs. In the case of offered htlcs the output is only one (of potentially many others) output. Also I understand the timelock slightly different. If you publish the commitment transaction it can be mined and verified directly. It ...


1

Why is the description field limited to 639 bytes? Every field in lightning invoice is of the form: type (5 bits) data_length (10 bits, big-endian) data (data_length x 5 bits) The data_length indicates the size of the data that is to be followed. Since data_length itself has a size of 10 bits, it can represent a number up to 1023 (210 -1). Thus the size ...


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