lightning-network

In the output of list channels the private/public status of the channel is returned, but in the output of pending channels the status is not revealed. To allow for recognizing a pending open channel as a private requires waiting for the channel to confirm.

Ideally the PendingChannelsResponse would include the channel flags or the private/public status of the channel to know which type of chan

When we return a bitcoin amount, our JSON responses currently specify the unit (btc, sat, msat) in the parameter name, but it's a bit ugly and is missing in some places.

Maybe it would be better to include the unit explicitly in the response. I see two different options:

• Instead of returning a numeric value, return a string including the unit (e.g. "2500 msat", "0.45 btc", "1.5 mbtc"). The

The rpcuser value is sensitive information and should not be displayed in the UI (/rtl/config/lnconfig).
We can take the following approaches to display the hidden information:
Password protect the config page and ask the user to enter password to display the page.

The expected behavior would be:

• User clicks on the LND Config tab
• The application prompts the user for entering the pas

I am unable to resize text in the xterm.js instance

I would like to be able to press ctrl+ to increase text size and ctrl- to decrease text size.

There are plenty of if not something then panic code, refactor them with general functions, but try to avoid reflect.

payment_request is returned so you can parse that to display the memo

• 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 Feature or Idea

Ratelimit the speed at which sites can create getInfo()/sendInvoice()/makeInvoice() requests if they require opening a window (for example, getInfo(), if pre-approved, should not be ratelimited). In testing, a buggy/malicious site can easily open tens or hundreds of windows.

Existing Example(s) of Feature

Here is an example piece of code to tri

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

Useful endpoints for the front end. It allows us to display to users if we are doing IBD or rescanning the wallet. This should add rescan and sync endpoints to indicate that the wallet is doing intiial block download (sync) or rescan which indicates the wallet is being rescanned.

{
  "wallet": {
    "keymanager": {
      "rootXpub": "zpub6jftahH18ngZyaghYHAYjB4MDxtYH4VZpLhkbeQot

when an API user is creating an invoice, there is a way to pass a memo field. This memo is aimed to be included in the boltt11 invoice, and display to both the sender (because it's part of the invoice) and the recipient.

we should add another field called metadata that allow an API user to add more data related to a payment, without the API user to himself have to have an external database

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