# CLN Team Meeting ## 2023/02/15 - cln: Discussing forwards and backwards compatibility for `cln-rpc` and `cln-grpc` ([#5988][5988]) - gl: Node export for user offboarding implemented - Nodes get disabled - DB backup and signer state are bundled and then encrypted - Uploaded to an HTTP host from where they can be downloaded - 🚧 Still writing documentation - gl: Currently enabling CLN v22.11 on GL: - VLS changed considerably and we need to track compatible CLN ↔ VLS pairs - Changes to `gossipd` and `gossip_store` need to be implemented, and hopefully we find a compatible subset so we don't need to create multiple versions - `Scheduler.schedule` calls are now authenticated (test framework was causing trouble) - gl: Node now tracks peers and reconnect on startup - gl: Backfilled a number of legacy APIs that had incomplete mappings - gl: Peter is working on pairing process and runes for constraints [5988]: https://github.com/ElementsProject/lightning/issues/5988
Last changed by  
 
Christian Decker
104

Read more

Connecting to CLN

If you want to use the grpc: start the grpc-plugin and generate the bindings from the proto file for your language. If you’re writing in Rust, decide which interface you want to use, then either use cln-rpc if you’re on the same machine (FS access to the socket) or use tonic-build to generate the bindings and connect over grpc (remote, no FS access). If you want to write a plugin in Rust, use cln-plugin If you want to write a plugin in Python, decide on whether to use grpc or JSON-RPC, then either generate the grpc bindings or use pyln-client which includes the JSON-RPC client flowchart LR grpc-client -->|grpc+https| grpc-plugin grpc-plugin -->|jsonrpc+uds| CLN cln-rpc -->|jsonrpc+uds| CLN pyln-client -->|jsonrpc+uds| CLN

2/7/2023
Read more from Christian Decker
Published on HackMD