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:
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:
LND Config tab
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.
payment_request is returned so you can parse that to display the memo
There are plenty of if not something then panic code, refactor them with general functions, but try to avoid reflect.
I'm submitting a ...
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_
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.
Here is an example piece of code to tri
It would be very useful to know if we're running regtest, testnet or mainnet in the Bitcoin Core Node section of the Welcome app.
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
Hi,
On send window the text (Paste payment request) should show if what is copied is a lightning invoice. But if what is copied is a bitcoin address, the text should be changed to (Paste bitcoin address).
Add a description, image, and links to the lightning-network topic page so that developers can more easily learn about it.
To associate your repository with the lightning-network topic, visit your repo's landing page and select "manage topics."
Background
Inspired by C-Otto/rebalance-lnd#241.
As part of pathfinding, lnd might encounter edges that have a policy specifying a zero CLTV delta (possibly because of no/outdated gossip?). Every time an edge like this is used in the pathfinding code, a warning is logged: https://github.com/lightningnetwork/lnd/blob/290b78e700021e238f7e6bdce6acc80de8d0a64f/routi