c-lightning

It would be nice if we could rename each individual node. Sometimes, Alice, Bob and Carol... are too vague for practical usage.

Ie. https://btcpay.kukks.org/rates?storeid=GPpuLBt2VaQEFySV4qjXM2xNCMo5iQDoKuqiRP6DA37T&currencyPairs=BTC_USD,BTC_EUR

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

Just blacklist some nodes by node id. I have an implementation already but if a new contributor wants to jump on it before i get to pr it i can review :). Hint: use the peer_connected hook.

Repro

"Receive payments" tab: generate an invoice with a description but no label. The plugin will crash.

Possible solution

Generate a random label, or forbid to set a description without a label.

This extension layout and classes was done in 5 minutes by a pragmatic programmer using only Tachyons classes.

If anyone out there knows how to build a simple and yet beautiful interface using the fewer elements possible that help would be very welcomed.

Marginal improvements would be great. For example, just modifying the layout a little or changing the default colors

We definitely need to add a test suite, people are using this and I still shamefully test new updates by-hand with a regtest and the plugins in test/.

The following call require the hash map implementation CLightningRPC.getInstance().runRegisterCommand(CLightningCommand.DIAGNOSTIC, payload); but we can use only the map interface