Repository of lnd rpc protocol files and utilities for working with them
npm install @ln-juggernaut/lnd-grpc
> Easy to use gRPC wrapper for lnd. ⚡️
This package provides and easy to use gRPC wrapper for lnd.
- Supports all lnd versions
- Supports all lnd gRPC sub services
- Automatic async/promise support
- Automatic lnd version detection
- lndconnect support
- Install
- Usage
- Maintainers
- Contribute
- License
Install via npm:
``
npm install lnd-grpc --save
Then import in your code:
`js`
import LndGrpc from 'lnd-grpc'
Create a new instance of the service using the LndGrpc constructor:
`js
import LndGrpc from 'lnd-grpc'
const grpc = new LndGrpc(options)
`
The constructor accepts the following options:
- lndconnectUri {[string]}:
An lndconnect uri that encodes the lnd connection details (host, cert, and macaroon). If lndconnectUri is set it will override the host, cert, and macaroon properties (below)
- host {[string]}:
Hostname and port of lnd gRPC. (extracted from lndconnectUri if provided)
- cert {[string]}:
TLS certificate of the lnd node. This can be a path to the TLS cert or PEM ended cert data. (extracted from lndconnectUri if provided)
- macaroon {[string]}:
Macaroon for the lnd node. This can be a path to the macaroon file or hex encoded macaroon data. (extracted from lndconnectUri if provided)
- waitForCert {[boolean|number]}:
Time (ms) to wait for TLS certificate before aborting connection attempt.
This is useful in the case where you can not guarantee that the TLS certificate exists at the time when you attempt to establish the connection.
Set to true to use the default of 10 seconds.
- waitForMacaroon {[boolean|number]}:
Time (ms) to wait for macaroon before aborting connection attempt.
This is useful in the case where you are connecting to a local node where a wallet does not already exist. After calling lnd's initWallet method to create a new wallet, it can take some time for lnd to initialize and create the wallet's macaroons.
Set to true to use the default of 10 seconds.
- version {[string]}:
If you know which version of lnd you are connecting to in advance you can specify that here.
By default, we use the latest proto files available when connecting to lnd. As soon as the wallet is unlocked, we call lnd's getInfo method in order to determine which version of lnd is running. If needed, we will reconnect using a more appropriate proto version.
- protoDir {[string]}:
Custom path to rpc proto files. advanced
- grpcOptions {[Object]}:
Custom gRPC options. advanced
Minimal example:
`js`
new LndGrpc({
host: 'localhost:10009',
cert: '~/.lnd/tls.cert',
macaroon: '~/.lnd/data/chain/bitcoin/mainnet/admin.macaroon',
})
Complete example:
`js`
new LndGrpc({
host: 'localhost:10009',
cert: '~/.lnd/tls.cert',
macaroon: '~/.lnd/data/chain/bitcoin/mainnet/admin.macaroon',
version: '0.6.0-beta',
waitForMacaroon: 30 * 1000, // 30 seconds
waitForCert: true,
protoDir: '~/path/to/proto/files', // useful when running in electron environment, for example
})
After initializing a new LndGrpc instance, call its connect method to establish a connection to lnd.
`js
const grpc = new LndGrpc({ host, cert, macaroon })
await grpc.connect()
console.log(grpc.state) // active|locked
`
After establishing a connection you can access all available lnd gRPC interfaces under the services property.
If the wallet state was determined to be locked when the connection was established you must first unlock the wallet and then activate the Lightning service in order to access methods on the Lightnig service or any other grpc subservice that requires the node to be unlocked.
`js
const { WalletUnlocker } = grpc.services
if (grpc.state === 'locked') {
await WalletUnlocker.unlockWallet({ wallet_password: Buffer.from('your wallet password') })
await grpc.activateLightning()
console.log(grpc.state) // active
}
`
Disconnect from all gRPC services. It's important to disconnect from the lnd node once you have finished using it. This will free up any open handles that could prevent your application from properly closing.
`js`
await grpc.disconnect()
`js
import LndGrpc from 'lnd-grpc'
const grpc = new LndGrpc({
host: 'localhost:10009',
cert: '~/.lnd/tls.cert',
macaroon: '~/.lnd/data/chain/bitcoin/mainnet/admin.macaroon',
waitForCert: true,
waitForMacaroon: true,
})
// Establish a connection.
await grpc.connect()
// Do something cool if we detect that the wallet is locked.
grpc.on(locked, () => console.log('wallet locked!'))
// Do something cool when the wallet gets unlocked.
grpc.on(active, () => console.log('wallet unlocked!'))
// Do something cool when the connection gets disconnected.
grpc.on(disconnected, () => console.log('disconnected from lnd!'))
// Check if the wallet is locked and unlock if needed.
if (grpc.state === 'locked') {
const { WalletUnlocker } = grpc.services
await WalletUnlocker.unlockWallet({
wallet_password: Buffer.from('mypassword'),
})
// After unlocking the wallet, activate the Lightning service and all of it's subservices.
await WalletUnlocker.activateLightning()
}
// Make some api calls...
const { Lightning, Autopilot, Invoices } = grpc.services
// Fetch current balance.
const balance = await Lightning.walletBalance()
// Enable autopilot.
const modifyStatusRes = await Autopilot.modifyStatus({ enable: true })
// Cancel an invoice.
const cancelInvoiceRes = await Invoices.cancelInvoice({
payment_hash: '3bba3a6cdbd601dbf096784115f45d314c0f51ffb69ae6d338e229cb825afbe1',
})
// Disconnect from all services.
await grpc.disconnect()
`
The grpc service will be in one of the following states at all times.
ready
The ready state is the initial state of all new lnd-grpc service instances and indicates that a connection has not yet been established.
locked
The locked state indicates that a connection has been established and the node was last known to be in a locked state.
active
The active state indicates that a connection has been established and the node was last known to be in an active (unlocked) state.
locked
The locked event is emitted when it has been determined that the wallet is locked and the WalletUnlocker interface is active.
active
The active event is emitted when it has been determined that the wallet is unlocked and the Lightning interface is active.
disconnected
The disconnected event is emitted after calling disconnect, once the connection has been fully closed.
is
Checks wether the service is in a given state.
Example:
`js`
assert(grpc.is('active')) // test wether the service state is active.
can
Checks wether the service can carry out a given state transition.
Example:
`js`
assert(grpc.can('activateLightning')) // test wether the service can activate the lightning service
waitForState
Wait for the service to enter a particular state.
Example:
`js`
await grpc.waitForState('active')
console.log(grpc.state) // active
gRPC Options
x
Under the hood we use the grpc-js library for the gRPC handling. By default we use the following options to control its behaviour.
`js`
{
keepCase: true,
longs: Number,
enums: String,
defaults: true,
oneofs: true,
}
These settings can be overridden by passing grpcOptions to the constructor. Custom settings will be merged in with the above defaults.
`js`
new LndGrpc({
host: 'localhost:10009',
grpcOptions: {
keepCase: false,
},
})
gRPC Proto Files
This repository hosts a copy of the lnd gRPC proto files for all official lnd releases. We attempt to select the most appropriate version of these files when connecting by calling lnd's getInfo method and parsing the version string.
In some situations you may want to load these files from an alternate location - such as in an Electron environment where you may need to bundle up the proto files as additional package resources for distribution. You can tell us to read the proto files from an alternate location by passing the protoDir option to the constructor.
Run the tests suite:
`bash`
npm test
Run with debugging output on:
`bash``
DEBUG=lnrpc* npm test
Feel free to dive in! Open an issue or submit PRs.
lnd-grpc follows the Contributor Covenant Code of Conduct.
MIT © Tom Kirkpatrick