BTCPayServer.Lightning.LNDhub 1.0.19

.NET 6.0 .NET Standard 2.0
dotnet add package BTCPayServer.Lightning.LNDhub --version 1.0.19
NuGet\Install-Package BTCPayServer.Lightning.LNDhub -Version 1.0.19
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="BTCPayServer.Lightning.LNDhub" Version="1.0.19" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add BTCPayServer.Lightning.LNDhub --version 1.0.19
#r "nuget: BTCPayServer.Lightning.LNDhub, 1.0.19"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install BTCPayServer.Lightning.LNDhub as a Cake Addin
#addin nuget:?package=BTCPayServer.Lightning.LNDhub&version=1.0.19

// Install BTCPayServer.Lightning.LNDhub as a Cake Tool
#tool nuget:?package=BTCPayServer.Lightning.LNDhub&version=1.0.19


A C# library for Lightning Network clients


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:

  • BTCPayServer.Lightning.Common contains the common abstractions shared between those implementation.
  • BTCPayServer.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:

  • BTCPayServer.Lightning.All super package which reference all the others NuGet
  • BTCPayServer.Lightning.Common exposes common classes and ILightningClient NuGet
  • BTCPayServer.Lightning.LND exposes easy to use LND clients NuGet
  • BTCPayServer.Lightning.CLightning exposes easy to use clightning clients NuGet
  • BTCPayServer.Lightning.Charge exposes easy to use Charge clients NuGet
  • BTCPayServer.Lightning.Eclair exposes easy to use Eclair clients NuGet
  • BTCPayServer.Lightning.LNbank exposes easy to use LNbank clients NuGet
  • BTCPayServer.Lightning.LNDhub exposes easy to use LNDhub clients NuGet

If you develop an app, we advise you to reference BTCPayServer.Lightning.All NuGet.

If you develop a library, we advise you to reference BTCPayServer.Lightning.Common NuGet.

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 BTCPayServer.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.

string connectionString = "...";
ILightningClientFactory factory = new LightningClientFactory(Network.Main);
ILightningClient client = factory.Create(connectionString);
LightningInvoice invoice = await client.CreateInvoice(10000, "CanCreateInvoice", TimeSpan.FromMinutes(5));

ILightningClient is an interface which abstract the underlying implementation with a common interface.

The connectionString encapsulates the necessary information BTCPay needs to connect to your Lightning node, we currently support:

  • clightning via TCP or unix domain socket connection
  • lightning charge via HTTPS
  • LND via the REST proxy
  • Eclair via their new REST API
  • LNbank via REST API
  • LNDhub via their REST API
  • type=clightning;server=unix://root/.lightning/lightning-rpc
  • type=clightning;server=tcp://
  • type=lnd-rest;server=http://mylnd:8080/;macaroonfilepath=/root/.lnd/admin.macaroon;allowinsecure=true
  • type=lnd-rest;server=https://mylnd:8080/;macaroon=abef263adfe...
  • type=lnd-rest;server=https://mylnd:8080/;macaroon=abef263adfe...;certthumbprint=abef263adfe...
  • type=lnd-rest;server=https://mylnd:8080/;macaroonfilepath=/root/.lnd/admin.macaroon;certfilepath=/var/lib/lnd/tls.cert
  • type=charge;server=https://charge:8080/;api-token=myapitoken...
  • type=charge;server=https://charge:8080/;cookiefilepath=/path/to/cookie...
  • type=eclair;server=;password=eclairpass
  • type=eclair;server=;password=eclairpass;;bitcoin-auth=btcpass
  • type=lnbank;server=http://lnbank:5000;api-token=myapitoken;allowinsecure=true
  • type=lnbank;server=;api-token=myapitoken
  • type=lndhub;server=
Eclair notes

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:

openssl x509 -noout -fingerprint -sha256 -in /root/.lnd/tls.cert | sed -e 's/.*=//;s/://g'

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.

If you want to use command line:

cd tests
dotnet test



Product Versions
.NET net5.0 net5.0-windows net6.0 net6.0-android net6.0-ios net6.0-maccatalyst net6.0-macos net6.0-tvos net6.0-windows net7.0 net7.0-android net7.0-ios net7.0-maccatalyst net7.0-macos net7.0-tvos net7.0-windows
.NET Core netcoreapp2.0 netcoreapp2.1 netcoreapp2.2 netcoreapp3.0 netcoreapp3.1
.NET Standard netstandard2.0 netstandard2.1
.NET Framework net461 net462 net463 net47 net471 net472 net48 net481
MonoAndroid monoandroid
MonoMac monomac
MonoTouch monotouch
Tizen tizen40 tizen60
Xamarin.iOS xamarinios
Xamarin.Mac xamarinmac
Xamarin.TVOS xamarintvos
Xamarin.WatchOS xamarinwatchos
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on BTCPayServer.Lightning.LNDhub:

Package Downloads

Client library for lightning network implementations to build Lightning Network Apps in C#.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.0.19 2,015 2/21/2023
1.0.18 921 2/8/2023
1.0.17 339 2/2/2023
1.0.16 1,378 1/10/2023
1.0.15 426 1/6/2023
1.0.14 668 12/23/2022
1.0.13 310 12/22/2022
1.0.12 625 12/7/2022
1.0.11 781 12/5/2022
1.0.10 2,032 10/31/2022
1.0.9 537 10/26/2022
1.0.8 626 10/17/2022
1.0.7 1,238 9/26/2022
1.0.6 1,108 9/9/2022
1.0.5 467 9/9/2022
1.0.4 369 8/23/2022
1.0.3 1,329 8/9/2022
1.0.2 3,110 7/8/2022
1.0.1 1,227 6/21/2022
1.0.0 4,942 6/8/2022