Skip to main content

Open a trusted funding channel to the embedded node


One potential setup you can have with your in-app, embedded node in ZEUS v0.8: connect to your routing node at home (or in the cloud) with a private 0-conf channel.

There are a lot of perks to this set up. You skip on-chain fees, save on routing fees, segregate your main LN funds from your phone, and potentially skip the need to backup your mobile wallet.

WARNING: this is an ADVANCED procedure. You should be comfortable with compiling LND from source, modifying your LND configuration, and running software with NodeJS. Please read the full document before proceeding.


1 On the remote node, enable zero-conf channels

In your lnd.conf add the following lines:


2. From the embedded node, connect to your remote node as a peer

Go to the Open Channel view in ZEUS. You can get there by going to the channels pane in the bottom right corner of the main view. Once you're on the Channels pane, press the plus icon (+) in the top right corner to get to the Open Channel view.

From the Open Channel view, you can press on the header to switch to Connect Peer mode. The header and the fields will change to reflect the mode.

From the Connect Peer mode, enter in the remote node's pubkey and host, and then press the Connect Peer button. If successful, ZEUS should return a message saying that you've successfully connected to your peer.


3. Add your remote node as a zero conf peer

Navigate to Settings > Embedded Node > Peers > Zero conf Peers, and add your remote node's public key to the Zero conf peers list.


4. From the remote node, open up a trusted funding channel using Balance of Satoshis (BOS)

Now that you've established a peer connection from the embedded node to the remote node, you can now open up a channel from the remote node to the embedded node.

To open up the trusted funding channel, you must be using an LND node with the BOS command line tool

On the remote node run:

bos open <embedded-node-public-key> --type private-trusted --avoid-broadcast --amount <amount-in-sats>

The --avoid-broadcast flag will ensure that sure you never broadcast the transaction. This channel will never be reflected on-chain.

5. Be prepared to close channels out with abandonchannel

In our experience, we've had some of these trusted channels get out of wack and go into 'borked' states on LND. To close them out we've had to use the lncli abandonchannel command which requires building LND with the devrpc flag enabled.

Note that this is a dangerous command. You should not use it without understanding the consequences of it. You should ensure that the channel opening and closing were never broadcasted before using it.