Background

When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.

In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the

Would be useful to have deleteinvoice RPC method (opposite to createinvoice) to be able to cleanup expired invoices

• I'm submitting a ...

  • bug report
  • feature request
  • [x ] support request

• What is the current behavior?

Traceback (most recent call last):
File "run.py", line 22, in
sys.exit(app.start())
File "/home/Martin/node-launcher/node_launcher/gui/application.py", line 32, in start
self.node_set.start()
File "/home/Martin/node-launcher/node_

Description of the Issue

When an invoice has expired, Joule should not allow the 'Confirm' payment button to be clicked. It should be disabled, gray, and/or show 'Expired'.

Additionally, the Reject button is no longer appropriate after expiry. It should simply be replaced with a 'Close' button.

Steps to Reproduce

Create an invoice that expires, and then leave the payment dialog

This is useful for claiming pegins with elements

gettxoutproof ["txid",...] ( "blockhash" )

Returns a hex-encoded proof that "txid" was included in a block.

NOTE: By default this function only works sometimes. This is when there is an
unspent output in the utxo for this transaction. To make it always work,
you need to maintain a transaction index, using the -txindex command line option

Some candidates for removal that could easily be re-implemented inside Spark:

• superagent (only used for a simple HTTP GET request, can be replaced with the built-in http module)

• helmet (sets security headers)

• js-yaml (only used to format objects in a human-readable manner, we don't really need yaml)

• nanoid (secure random string generator)

• is-ip (few-liner depende

This was optimized already in #1431 to reduce the number of times we throw when transaction parsing -- now it should never happen on a live network. There is still a problem when we have a unsigned base transaction with 0 inputs and 1 output, which gives us the same bytes as the marker + flag byte (0x0001). This is really a base transaction, but we will think it is a WitnessTransaction and

This might be a good idea and sufficiently easy to implement.
Just leaving the suggestion here for the future.

Where suggested by brian-brazil in prometheus/docs#1737:

Some suggestions to improve your exporter:
_total is a suffix for counters, it shouldn't be used with gauges. Some metrics like lightning_channel_in_msatoshi_offered also sound like they might be counters rather than gauges.
Units are inconsistent, sometimes missing and conflicting with the help text. You s

The "server address" and "macaroon/cert locations" are currently hardcoded into the script at lnd.py in a way that assumes that the script will be run in the same environment as the lnd node. Specifically for running the scripts remotely, it would be useful if there was some way to allow the user to define:

1. a common folder location where credentials (admin.macaroon & tls.cert) are stor

I would appreciate support for my local currency, ILS (Israel Shekels).