[c-lightning] [Lightning-dev] Lightning RPC

William Casarin jb55 at jb55.com
Tue Jan 25 02:33:32 AEDT 2022

On Mon, Jan 24, 2022 at 01:54:49PM +1030, Rusty Russell wrote:
>Christian Decker <decker.christian at gmail.com> writes:
>>William Casarin <jb55 at jb55.com> writes:
>>> I think the end goal of an RPC bolt [blip] would be super powerful,
>>> so that lnsocket could talk to any lightning node, but that could be
>>> further down the line. Choosing the right data format seemed like an
>>> important step in that direction. Would love to hear your thoughts
>>> on this!
>> I agree. Exchanging the transport layer underneath grpc doesn't change
>> semantics, but does unlock a number of potential use-cases. I think
>> either the JSON-RPC or grpc can serve as a basis for a common RPC
>> definition that can have any number of bindings, since we generate
>> conversion code to/from JSON-RPC and grpc we can transparently map them
>> back and forth.
>Yeah, I don't think we'll end up with a control standard.  But I've been
>pleasantly surprised before: certainly a common subset would be nice!

I ended up just using json+commando for my prototype[1]. I'm not going
to overengineer anything yet. If there's a way write plugins for the
other implementations I could start hacking away at a common control
subset, since I do eventually want an iOS app that controls all node
implementations. I will try to get something working across multiple
implementations before writing up a spec.


[1] http://git.jb55.com/lnsocket/file/rpc.c.html

More information about the c-lightning mailing list