<p>This was answered during a c-lightning developer call on January 10th 2022. The <a href="https://github.com/bitcointranscripts/bitcointranscripts/blob/master/c-lightning/2022-01-10-developer-call.md" rel="nofollow noreferrer">transcript</a> is anonymized by default.</p>
<blockquote>
<p>There we are talking about different bindings. These are the bindings that we use for our RPC interface. I think when rust-lightning is talking about bindings they are talking much more about having a C API that they can compile into their own apps. Whereas this is inter daemon communication or daemon with plugin or daemon with front end. The C API that rust-lightning is building is most likely to be consumed by a binary directly. For example if you are building a Java application or an Android application you will most likely be using GNI to talk to rust-lightning instead of some other Java code. I think they are referring to that. Whereas this is mostly inter daemon and inter process communication. We have a connection or a file descriptor where we write stuff out.</p>
</blockquote>

CC BY-SA 4.0
2022-02-05T11:49:38.937Z
2022-02-05T11:49:38.937Z
Michael Folkson
<p>I know <a href="https://github.com/lightningdevkit/ldk-c-bindings" rel="nofollow noreferrer">LDK</a> (rust-lightning) has been doing a lot of language bindings work to support various languages (C, Go, Java, Swift etc).</p>
<p>c-lightning is now <a href="https://github.com/ElementsProject/lightning/pull/5010" rel="nofollow noreferrer">working</a> on language bindings itself so you can build say c-lightning plugins in Rust.</p>
<p>How does this language bindings work compare to the approach LDK has been taking?</p>

<lightning-network><core-lightning><lightning-development-kit>
c-lightning is working on Rust language bindings. How does this compare to the language bindings work LDK has been doing?
Michael Folkson
# c-lightning is working on Rust language bindings. How does this compare to the language bindings work LDK has been doing?

(Asked by: username_0 on 2022-02-05)

I know [LDK](https://github.com/lightningdevkit/ldk-c-bindings) (rust-lightning) has been doing a lot of language bindings work to support various languages (C, Go, Java, Swift etc).

c-lightning is now [working](https://github.com/ElementsProject/lightning/pull/5010) on language bindings itself so you can build say c-lightning plugins in Rust.

How does this language bindings work compare to the approach LDK has been taking?

**Tags:** lightning-network, core-lightning, lightning-development-kit


---

## 1 answers

### Answer by username_0 on 2022-02-05. Score: 4 | Accepted answer

This was answered during a c-lightning developer call on January 10th 2022. The [transcript](https://github.com/bitcointranscripts/bitcointranscripts/blob/master/c-lightning/2022-01-10-developer-call.md) is anonymized by default.

> There we are talking about different bindings. These are the bindings that we use for our RPC interface. I think when rust-lightning is talking about bindings they are talking much more about having a C API that they can compile into their own apps. Whereas this is inter daemon communication or daemon with plugin or daemon with front end. The C API that rust-lightning is building is most likely to be consumed by a binary directly. For example if you are building a Java application or an Android application you will most likely be using GNI to talk to rust-lightning instead of some other Java code. I think they are referring to that. Whereas this is mostly inter daemon and inter process communication. We have a connection or a file descriptor where we write stuff out.


---

