Dunder LSP and Lightning Box Provider
Dunder LSP and Lightning Box Provider
This mini guide is dedicated to all those node runners that want to give more purpose to their LN node and provide more services for mobile users
🇪🇸 Español
I really hope that all those Plebnet node runners are reading this mini guide and give more use to their LN nodes. This liquidity is what is needed right now for regular mobile users.
I would like to explain some simple steps about how you can offer LN liquidity services for mobile node users. This could be also that "uncle Jim" scenario, where you are offering LN services for your family and friends, that do not / can't run their own node and just want a way to use LN in a safe and private way, self-custodial.
REMINDER:
This guide is not for noobs! Please, if you do not have a good base knowledge about running public routing nodes, this is NOT for you.
LSP do not hold user funds! It just provide liquidity. This is NOT custody of users funds, is just a way to provide, fast opening channels and good routes for users payments. Read more here what is a LSP (Liquidity Service Provider).
LSPs are very important for mobile private nodes users, to be able to open good channels that offer good liquidity. Not all LN node in the network are willing to offer this kind of services, because a private node is not always online and is not doing any routing, so those funds are exclusively for their own payments, so the LSP cannot use them for routing. So in some way they depend on users traffic. If the user is not using these funds to do payments, the LSP is not earning any fees. Or even worse, if is opening an inbound channel for the user, the LSP is literally putting money from his pocket into a channel that never move.
Is important that these channels services are for users that have most of the time traffic in and out.
Some requirements are to mention first:
A. You have a good LN public node
Running a good routing node is a serious task, you must have a good node with history, with good channels, good liquidity, good maintenance. It is not for any shity new node in the network.
You will have a great responsibility to route well all the payments, not only for your private peers but also for the public ones.
I wrote several guides about this aspect, please take your time and read them:
B. You run a LND node.
This scenario, unfortunately is only for LND node. No CLN, Eclair, LDK for the moment. We encourage anybody that is good with writing code to take it and fork it for other LN implementations. The software is FOSS.
I hope some day, we will have a standard code for all type of LSP and LN implementations, but until then we have to use what we have, to try to move forward.
C. Your node have good liquidity
You must know very well how to maintain your liquidity in such way that could offer smooth and fast payments.
The health of the network depend enormously of good public nodes. If you node is not well maintained, doesn’t have very good liquidity, is only Tor, then you are doing more damage to the whole network then doing good.
D. Routing fees you apply
Fees are up to you, but I suggest to not let the greed controls you. We are not in the phase when we will fuck each others. First we need to fuck the banks and governments, pushing forward the Bitcoin adoption and more use of it.
So proceed with caution, have a long time preference, having a smooth income flow with happy clients of your liquidity.
E. Technical skills
You must be very familiar with Linux and CLI, installing software. NO NEED for noobs that knows only how to use Umbrel and Windows.
Debugging and maintaining a serious system is not for apprentices. Shit can happen all the time and you must act fast and with knowledge. Many people will depend on your skills to fix problems in time.
F. Service longevity
Willing to maintain the service for your users as long as you could. Be fair and help them as much as you can. We’ve seen many quitters, so analyze your options, your future gains, your strategy for long term and start this only if you know you could keep the promise.
SOLUTION PROPOSAL
There are two parts of the proposal:
Dunder LSP - liquidity services for mobile nodes
Lightning Box - LN Address services for private domains, family and friends
A - Dunder LSP
This solution is based on Dunder LSP specs, that are fully open source, made by Hampus , developer of Blixt Wallet. All contributions to improve the code are welcome!
This Dunder LSP is offering right now easy onboarding for new Blixt wallet users, a full LND node on your mobile (I wrote a full step-by-step guide here).
The idea is that you, as a public routing node runner, will provide 2 things:
private channels to mobile node users, even with 0-conf channels
access to public liquidity through those private channels, better payment routes
In this way, the mobile users will have a fast and smooth experience using LN in a self-custodial method, without the complicity of running public routing nodes. Some users simply can’t do all those things, they just want to use LN for own payments.
I wrote all the documentation for Blixt wallet, explaining each app feature, with multiple guides and FAQ. Please read them all, are very interesting use cases.
And here is one that specifically talk about how to use Dunder LSP in your Blixt wallet.
The Dunder process flow is described in this simple scheme:
So what steps you should do as a LND node runner?
Install Dunder LSP software on your own node machine
Set your own Dunder rules for fees, size of the channels etc
Make some tests with your own Blixt wallet, opening an on-demand channel with 0-conf, instant
Make some more tests with your family/friends Blixt users, to be sure your node is responding well and can route well all the payments.
List your Dunder LSP services on the Blixt community peers - soon maybe this list will be integrated directly into Blixt UI so new users can pick easily their peers. Right now is just list where Blixt users are posting their preferred peers to use with Blixt, like a vouched list of peers.
Give feedback to Hampus, post issues on Dunder Github, if you have, participate with PRs for the code. Being open source also can be extended to be a LSP standard for other LN implementations and LN mobile nodes (Zeus, Mutiny, Electrum, Breez, Phoenix).
The network topology will be the following:
B - Lightning Box
This is a new feature for Blixt Wallet, starting with v0.6.9-420 and is based on a software package named Lightning Box, also created by Hampus.
Lightning Box is a Lightning Address provider for mobile nodes like Blixt Wallet, letting you receive Lightning Address payments directly to your phone.
This works in conjunction with the Persistent Mode released in v0.6.9, which allows Blixt Wallet to stay active in the background in order to receive payments.
You can also use this for nostr tipping.
For the moment the default Lightning Box is run on the Blixt Node server and offer a @ blixtwallet.com LN Address. But ANYBODY with a LND public node can run the Lightning Box server and offer LN Address for its own domain, self-custody.
Right now, the Blixt server is only forwarding the payments to Blixt users. Users must put their Blixt node wallet in "persistent mode" in order to receive these payments to their @ blixtwallet.com LN addresses.
So there is NO custody of the funds, or hold invoices, the LN box act as a forwarder.
It can be even used as a chat over LN, instant and fun, also supporting LUD-18 (adding an alias name to a payment). You can add in the contact list, all your regular LN addresses you are using frequently and have it at hand for chatting or sending funds easily. Now Blixt can be considered a full LN chat app 😂😂.
As you can see in this demo image, on the main screen of Blixt appear all the “chats” over LN using LN Box and LUD-18.
As you can see in the screenshot above, sending from SN account, is displayed nicely the logo + LN address + message. Same works for sending from Blixt, you can attach your Blixt LN Address or simply add the alias name (previously set in Blixt settings), or both.
This option from LUD-18 could be useful also for subscription services, where user can send a specific alias (is NOT your node alias or your real name!) and based on that you could be registered or receive back a specific message or whatever else.
Attaching an alias name (LUD-18)+ comment (LUD-12) to a LN payment can have multiple use cases!
See here a video demonstration about how to setup your LN Address in Blixt.
Here is the code for Lightning Box if you run it for yourself, for your family and friends, on your own node, with your own domain.
Happy Lightning with Blixt Node Wallet!
Only by collaborating, testing, using and improving we can go forward !
DISCLAIMER
I am not paid by Blixt or any other team/company. I just support for free their open-source solutions with guides. We MUST help each others if we want to go forward with Bitcoin adoption. They write code, I write guides.
I am writing guides and documentations, translations for many other Bitcoin solutions, for free. My life is dedicated to Bitcoin as a whole, as a way forward for a better world.
Don’t ask what Bitcoin did for you, ask what YOU did for Bitcoin!
MAY THE ₿ITCOIN BE WITH YOU!
If you appreciate DarthCoin work, you can send some satoshis to darthcoin@getalby.com or darthcoin@stacker.news or darthcoin.blink.sv
or using Cashu Address darthcoin@minibits.cash
If you do not want to subscribe on substack, all DarthCoin Bitcoin guides are also announced on this dedicated Telegram Channel, for easy search and keep track.
To subscribe on substack, click here: