tonyaldon

lightning

![img-1000.png](https://m.stacker.news/24807)

Would you like to attach a socket REPL to your Core Lightning plugin?

I just made clnrpc-clj public: A Core Lightning JSON-RPC client for Clojure devs

🪄Can we modify a @Core_LN plugin while it's running?  Answer in the video

Printing json objects in Core Lightning log

In BOLT 11 invoices, why payment hash and secret are 52 5-bit bytes long?

I had a question from a friend this morning about Core Lightning RPC interface and I thought my answer may be helpful for other.  So here we are in Stacker News.

> What is your take on RPC?  my understanding is that you cannot add rune permissions to it and that it gives you admin access (god mode) on your node.

-   A unix socket RPC client is something that runs on the same machine as your node and connects to it via the socket file `lightning-rpc`.  It is something inherently local.  So if you run something in you node machine, anyway you already have access to the node, so there is no need for restriction like rune.  If you have access to the node, you are already god ;)
-   For instance `lightning-cli` is a RPC client.  You use it in the same machine as the node, and each time you run a command it connect to your node via the socket file `lightning-rpc`.  So if there is no unix socket RPC client, you couldn't talk to your node.
-   clnrest and cln-grpc are both plugins that expose CLN commands via some (communication) protocols: HTTP/HTTPS for clnrest and Grpc for cln-grpc.  Both plugins are running locally in the node's machine, and both use a unix socket client to talk to the node.  clnrest uses the Python library `pyln-client` as RPC client and `cln-grpc` uses the Rust library `cln-rpc`.  So when you ask one of those plugins to do something on your node, they will issue a RPC request to your node.  What is interesting is that `clnrest` asks you for a `rune` because it will check with `checkrune` if you are allowed to run the command you want to run and then run it locally.  Something that `cln-grpc` doesn't do (as far as I understand).
-   `lnsocket` is really something different.  This is a library (C, go) that connects to your node using the LN protocol (BOLT #8 and BOLT \#1) and send `commando` messages.  And your node that runs the builtin plugin `commando` knows how to handle those specific messages.  And `commando` requires a `rune` to run the command you ask him to run.  Under the hood it will also check the run with `checkrune` command.  If you are interested you can watch those lives:
    -   https://lnroom.live/2023-07-20-live-0009-introduction-to-commando-and-commando-rune/
    -   https://lnroom.live/2023-08-03-live-0010-simple-cln-bookkeeper-web-app-powered-by-lnsocket-and-golang-part-1/

I hope this is useful!
Have a nice day

[how to] Core Lightning unix socket RPC clients, clnrest, cln-grpc and commando

Working on lightningd and need to log some information?

devs

writing C code with the Emacs user experience

> I just got sick of having to configure it

I can feel what your saying.  It happens to me also from time to time! 

Take a look at Core Lightning checkrune command

We talk about signatures in BOLT 11 invoices today in 2h?

This is how I try things out in a repository I'm not familiar with

It is never too late to learn how BOLT 11 invoices work!

(102 >> i) & 1 --- Shifting bits is funny and sometime necessary?

underrated programming tool: failing tests

bitcoin

Pieter Wuille: New Address Type for SegWit Addresses (2017)

How to get the last bit of a number in C?

Learn how to add ccan libraries into your C project

Core Lightning implementation of BOLT #11 invoices - part 5 | live #21

You don't need to be a C programmer to start learning about CLN implementation!