This library is meant to facilitate the development of Lightning Network based apps written in C#.
Its main goal isn't to perfectly implement client API of all lightning node implementation, but to provide a common abstraction that can be used to support many implementations at once.
The most important packages are:
PCOINPayServer.Lightning.Common contains the common abstractions shared between those implementation.
PCOINPayServer.Lightning.All contains LightningClientFactory which can convert a connection string to an instance of ILightningClient.
If your app depends on ILightningClient directly, you will be able to support those different lightning implementations out of the box.
Here is a description of all packages:
PCOINPayServer.Lightning.All super package which reference all the others
PCOINPayServer.Lightning.Common exposes common classes and ILightningClient
PCOINPayServer.Lightning.LND exposes easy to use LND clients
PCOINPayServer.Lightning.CLightning exposes easy to use clightning clients
PCOINPayServer.Lightning.Charge exposes easy to use Charge clients
PCOINPayServer.Lightning.Eclair exposes easy to use Eclair clients
PCOINPayServer.Lightning.LNbank exposes easy to use LNbank clients
PCOINPayServer.Lightning.LNDhub exposes easy to use LNDhub clients
If you develop an app, we advise you to reference PCOINPayServer.Lightning.All.
If you develop a library, we advise you to reference PCOINPayServer.Lightning.Common.
You can also use our BOLT11PaymentRequest to parse BOLT11 invoices. (See example).
How to use
Click on the nuget button of the package interesting you, and follow the instruction to add it to your project.
For .NET Core Apps, you need to enter this in your project's folder:
dotnet add package PCOINPayServer.Lightning.All
You have two ways to use this library:
Either you want your code to works with all lightning implementation (right now LND, Charge, CLightning)
Or you want your code to work on a particular lightning implementation
Using the generic interface
This is done by using LightningClientFactory and the common interface ILightningClient.
Note that bitcoin-host and bitcoin-auth are optional, only useful if you want to call ILightningClient.GetDepositAddress on Eclair.
We expect this won't be needed in the future.
LND notes
Unless the LND certificate is trusted by your machine you need to set the server authentication scheme for LND by specifying one of: certthumbprint, certfilepath, allowinsecure=true.
certfilepath and certthumbprint are equivalent in terms of security but differ in their practical usage.
certfilepath reads a file on your file system so unless you set up some kind of file syncing you can not use it for remote connections.
The advantage is that if the certificate is updated (and synced in case of a remote machine) no more reconfiguration is required for RPC connections to continue to work.
It is therefore the recommended option if you can use it.
The certthumbprint to connect to your LND node can be obtained through this command line:
allowinsecure=true just blindly accepts any server connection and is therefore not secure unless used in tightly controlled environments.
E.g. host is the same machine or is accessed over an encrypted tunnel, assuming no untrusted entities can bind the specified port.
LNDhub notes
You can also use the lndhub:// URL, which can be retrieved e.g. from the BlueWallet Export/Backup screen.
The library turns it into the expected type=lndhub connection string format.
Using implementation specific class
If you want to leverage specific lightning network implementation, either instanciate directly ChargeClient, LndClient or CLightningClient, or cast the ILightningClient object returned by LightningClientFactory.
How to test
You first need to run all the dependencies with docker-compose:
cd tests
docker-compose up
Then you can run and debug the tests with Visual Studio or Visual Studio Code.
