Ereignishorizont
blitz⚡bank

blitz⚡bank

The Self-Managed Blitz⚡Bank

The biggest hurdle for users of Bitcoin⚡Lightning is often managing their funds sovereignly. Custodial services like Wallet of Satoshi are ideal for getting started, but they are not self-custodial solutions – we have to trust the provider. Running and maintaining your own Lightning node is not an option for most people. But what if a service provider could run and maintain the node while we still keep full control of our funds? That is exactly what the Phoenix Wallet from ACINQ offers today. And what if we could also set up a wallet and account system to give family and friends a wallet as well? That is what LNbits offers. LNbits thus becomes your very own Blitz⚡Bank. But that’s not all – LNbits can do much more.

1. Introduction

Even though Bitcoin Lightning will probably never be a technology that the majority of people manage directly and sovereignly, it will still play a central role in the development, distribution and adoption of Bitcoin. Lightning is expected to serve as a settlement layer for various custodial services, sidechains and further layers on top of Bitcoin. There will probably also be combinations in which Lightning is the link operated by specialists – if only because of rising on-chain fees and the increasing price of Bitcoin.

The fees for opening and closing Lightning channels are still affordable. The technology is now quite mature, and payments over Lightning work surprisingly well. A few years ago, running a Lightning node was reserved for real nerds. Today, well-developed software takes over many background tasks, so 1-click nodes already exist. Nevertheless, you will still occasionally have to dig deeper when problems occur and take care of backups yourself.

Development doesn’t stand still, and so the company ACINQ released the Phoenix Wallet. ACINQ uses the Lightning implementation “eclair”, which, next to LND and Core Lightning, is the third most widely used Lightning implementation. ACINQ manages the Lightning node for you and takes care of all background tasks. The big advantage, however, is that the wallet remains in the user’s self-custody. You get a 12-word seed and your own channel, in which the outbound liquidity always belongs to you. So the funds are in self-custody while ACINQ manages the technology in the background. For this service they charge fees, of course, but these are transparent and, in my opinion, fair: fee overview.

We can now run a quasi “own” Lightning node with little effort. The node has a channel to the ACINQ servers, which act as your Lightning Service Provider (LSP). You don’t need anything more. ACINQ is well connected, and with splicing you can now also increase or decrease the size of Lightning channels. For the fee, ACINQ also directly provides you with a channel of 2 million satoshis, so the channel can go a while without any adjustments. ACINQ manages the node and the channel, but you own the key to the wallet and thus control the funds in the Lightning channel.

For a long time the Phoenix Wallet was only available as an app for Android and iOS, but it is now also available as a server service for Linux systems. This opens up new possibilities. Since interaction with the “Phoenixd” daemon only happens via the command line (CLI) or an API (Application Programming Interface), direct use is rather impractical for the average user. In combination with LNbits, however, they make a strong team. LNbits is a wallet and account system with a graphical user interface that makes usage considerably easier. LNbits essentially consists of a database and numerous extensions that offer an astonishing number of features. However, LNbits needs a funding source, and this is where the Phoenix Wallet comes into play.

Both applications together on a Virtual Private Server (VPS) hosted in the cloud with direct internet access, combined with a domain pointing to the server, give you your very own Blitz⚡Bank. This enables you to independently manage a complete Lightning wallet and account system – for yourself, your family or your friends. The costs are manageable: about 5 euros per month for the VPS and setup fees of about 30,000 satoshis. If you already own a domain, you can usually create a subdomain for free. Otherwise, a domain costs an additional 5 to 15 euros per year, or you can use a free subdomain from e.g. duckdns.org.

Thanks to the sophisticated Phoenix Wallet and the excellent user interface of LNbits, installing and setting up a Blitz⚡Bank is no longer rocket science. Watch my video and judge for yourself. A little technical background is required, but the installation is mostly done by copy and paste, and the setup is done through the LNbits user interface. Just give it a try – it’s definitely worth it!

2. Requirements

You need two things: a domain or subdomain and a Virtual Private Server (VPS). If you already have a domain, you can easily create a new DNS entry for the subdomain on your hosting provider’s website under DNS/nameserver, pointing to the IP address of the Virtual Private Server. If you don’t have a domain yet, you can either buy one from any hosting provider or use a free subdomain, for example from duckdns.org. The domain and VPS providers don’t have to be the same; many web hosting providers also offer Virtual Private Servers. As an example, I explained the setup of a VPS at Digital Ocean, but you can use any provider. The server doesn’t need much: the minimum requirements are 1 CPU, 1 GB RAM, 25 GB SSD and 1 GB transfer. As the operating system, I recommend Ubuntu 24.04 LTS, which is the version I tested this with.

3. Set Up and Harden the Server

Recommendation: To keep an overview and always have all your data at hand, create a text file and store it, ideally in a protected area, since it will contain sensitive data. Here is a possible template:

Your Domain:             subdomain.yourdomain.com
VPS IP address:          yourIPaddress
Login "root" user:       ssh root@yourIPaddress / password: your1strongpassword
Login "blitzbank" user:  ssh blitzbank@yourIPaddress / password: your2strongpassword
Phoenix Wallet Seed:     the twelve words ..
Super User Name:         SuperUser / password: your3strongpassword
Super User Account:      https://subdomain.yourdomain.com/wallet?usr=33bfc..
Start User Account:      https://subdomain.yourdomain.com/wallet?usr=d486f..

On your PC or laptop, open the terminal window for the command line or command prompt. On Windows, type ‘cmd’ into the Start menu; on Linux systems press ‘Ctrl-Alt-T’; on macOS search for ‘Terminal’. Then follow the instructions. You only have to enter your individual data, such as the IP address or domain, in a few places, and check the version once during the Phoenix installation and adjust it if necessary. You can take everything else as it is.

ssh root@yourIPaddress

Perform the Ubuntu OS Update / Upgrade

apt update && apt dist-upgrade -y

-> You may have to press Enter.

Automatic Security Updates (unattended-upgrades)

So that your server doesn’t stay on an outdated state permanently, we let Ubuntu install the security updates on its own. Only the official security updates from Ubuntu are installed, no regular feature updates and no third-party programs such as Phoenixd or LNbits.

apt install unattended-upgrades -y
dpkg-reconfigure -plow unattended-upgrades

-> At the question “Automatically download and install stable updates?” use the arrow keys to select <Yes> and confirm with Enter. On many VPS the package is already preinstalled. In that case you only see the message “is already the newest version”, and the question follows anyway.

Some updates, especially kernel updates, only take effect after a reboot. We let this happen automatically at night, but only if an update actually requires it. Thanks to the autostart services (see below), Phoenixd and LNbits start again by themselves afterwards, so you don’t have to do anything. Open the configuration file:

nano /etc/apt/apt.conf.d/50unattended-upgrades

Navigate to the end of the file with CTRL+END and append the following lines there:

Unattended-Upgrade::Automatic-Reboot "true";
Unattended-Upgrade::Automatic-Reboot-Time "04:00";

-> CTRL+X -> Y -> Enter

Test the configuration (dry run, nothing is installed):

unattended-upgrade --dry-run --debug

-> At the end you should see either a list of pending packages or “No packages found that can be upgraded unattended”. Both are fine. You can view the log of the real runs later with sudo cat /var/log/unattended-upgrades/unattended-upgrades.log (without sudo you get “Permission denied”).

Note: Phoenixd, LNbits and the LNbits extensions are not updated by this. You should continue to update these yourself and deliberately, ideally after a snapshot, since this is your money system. You update LNbits like this:

sudo systemctl stop lnbits
cd ~/lnbits
git pull --rebase
uv sync --all-extras
sudo systemctl start lnbits

-> Afterwards, update the extensions in the Super User account under Extensions with Update All. For Phoenixd, download the new version as described in the section “Install Phoenix” and restart the service with sudo systemctl restart phoenixd.

ufw (Firewall)

apt install ufw
ufw default deny incoming
ufw default allow outgoing
ufw allow 22 comment 'OpenSSH'
ufw allow 80 comment 'Standard Webserver'
ufw allow 443 comment 'SSL Webserver'
ufw enable
ufw status 

-> Press y once and then Enter to activate the firewall.

fail2ban (Protection Against Brute Force Attacks)

apt install fail2ban -y
systemctl enable fail2ban
systemctl start fail2ban
systemctl status fail2ban

-> Confirm twice with Enter.

swapfile (Virtual RAM, for Memory Overflow)

fallocate -l 2G /swapfile
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfile
swapon -s
sudo nano /etc/fstab

To start the swapfile automatically, you have to append the following at the end:

/swapfile swap swap defaults 0 0

-> Save and close with CTRL+X -> Y -> Enter.

Check the swapfile installation:

htop

-> Top left: Swp[ 0K/2.00G]
-> Quit with F10

Create a Dedicated User

For more security, we create a new user that we will use to log in from now on. It also gets “root” privileges, but has to identify itself with its password again and again. This offers more security, better traceability and protects against human error.

adduser blitzbank

-> Set a password; entering the additional data is optional.

usermod -aG sudo blitzbank 

-> Give the user root privileges.

Edit the configuration file of the OpenSSH server.

sudo nano /etc/ssh/sshd_config  

Add:

AllowUsers blitzbank

-> CTRL+X -> Y -> Enter

Note: With this, SSH login is only allowed for the new user. If you try to log in as the “root” user, you will see the error message “Permission denied, please try again.” This is intentional, because an attacker always knows the user name “root”. If you still want to reach the VPS as the “root” user, add an additional line AllowUsers root. After five failed attempts, access is blocked completely for 10 minutes, because Fail2ban blocks all connections.

Now shut down the VPS to make a backup and to restart everything once:

systemctl poweroff

-> To create a backup of your Virtual Private Server as a snapshot, you will surely find a corresponding function on the website of your VPS hosting provider. It creates a complete image of your disk or VPS. You can restore it at any time to bring the server back to an earlier state. Then restart the server via the website and, from now on, always log in with the new user.

ssh blitzbank@yourIPaddress

Secure SSH Access with a Key

Passwords can be guessed, an SSH key cannot. That’s why we set up login with a key pair and then disable password login. Follow this exact order and keep the existing connection to the server open until the test was successful, otherwise you will lock yourself out.

On your PC or laptop (not on the server), generate the key pair. Confirm the question about the storage location with Enter; a passphrase is recommended:

ssh-keygen -t ed25519

Copy the public key to the server. On Windows (cmd):

type %USERPROFILE%\.ssh\id_ed25519.pub | ssh blitzbank@yourIPaddress "mkdir -p ~/.ssh && chmod 700 ~/.ssh && cat >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys"

On Linux and macOS this is enough:

ssh-copy-id blitzbank@yourIPaddress

-> Now test in a new terminal window whether the login with ssh blitzbank@yourIPaddress works without being asked for the server password (possibly you will be asked for the passphrase of your key). Only when this works, continue on the server:

sudo nano /etc/ssh/sshd_config.d/00-hardening.conf
PasswordAuthentication no
PermitRootLogin no

-> CTRL+X -> Y -> Enter. We deliberately use a separate file with the name 00-..., because settings in /etc/ssh/sshd_config.d/ take precedence over the main file, and some hosters re-enable password logins there.

sudo sshd -t && sudo systemctl restart ssh

-> sshd -t checks the configuration; no output should appear. Afterwards, open another new terminal window and check that login with the key still works. Back up your private key (the file id_ed25519 without .pub), because without it you can no longer get onto the server. If you do lock yourself out, the console in the web interface of your VPS provider will help.

4. The Phoenix Wallet

Install Phoenix

Note: First check whether your VPS already has the program unzip installed. Use this command:

which unzip

-> As the answer, you get the path /usr/bin/unzip if unzip is already installed. If not, install it first with sudo apt install unzip.

Version check: Check the latest version and adjust it below if necessary: https://github.com/ACINQ/phoenixd/releases

mkdir phoenixd
cd phoenixd
wget https://github.com/ACINQ/phoenixd/releases/download/v0.9.3/phoenixd-0.9.3-linux-x64.zip
unzip -j phoenixd-0.9.3-linux-x64.zip
./phoenixd

First you will be asked whether you understand that you are responsible for the wallet yourself and that you have to back up the 12 seed words safely. Confirm with: I understand.

Next you will be asked whether you understand the automatic liquidity management. You can find more information on this topic here. Roughly speaking, Phoenix takes over the entire management for you. You can receive your first satoshis right away. However, a certain threshold has to be exceeded before a channel with 2 million satoshis is opened for you. This threshold is about 30,000 satoshis, which covers the on-chain and setup fees. More on that later. Confirm again with: I understand.

Finally, press the Enter key once more so that the Phoenix server starts. You will then already see the first information, such as your nodeid. Stop the process for now with CTRL+C.

Phoenix Wallet 12-Word Seed

cat ~/.phoenix/seed.dat ; echo

Important: Back up the 12 words safely! This is your insurance, with which you can always restore the wallet. You don’t need a backup of the Lightning channel, because Phoenix and the ACINQ server take care of that for you.

Phoenix Autostart Service

Open the phoenixd.service file:

sudo nano /etc/systemd/system/phoenixd.service

Fill the file with:

[Unit]
Description=phoenixd
After=network.target
[Service]
ExecStart=/home/blitzbank/phoenixd/phoenixd
WorkingDirectory=/home/blitzbank/phoenixd
User=blitzbank
Restart=always
TimeoutSec=120
RestartSec=30
[Install]
WantedBy=multi-user.target

-> CTRL+X -> Y -> Enter

sudo systemctl enable phoenixd
sudo systemctl start phoenixd
sudo systemctl status phoenixd

The Phoenix Wallet now runs in the background and is always started automatically. 🐦‍🔥

View the running logs of the last two hours:

sudo journalctl -u phoenixd -f --since "2 hour ago"

5. The LNbits Server

Prepare the Prerequisites

sudo apt install git curl -y
python3 --version
curl -LsSf https://astral.sh/uv/install.sh | sh
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

Install LNbits

cd ~
git clone https://github.com/lnbits/lnbits.git
cd lnbits
git checkout main
uv sync --all-extras
cp .env.example .env
uv run lnbits

The server should now have started successfully:
..
-> SUCCESS | ✔️ Backend VoidWallet connected and with a balance of 0 msat.
..

The VoidWallet is an empty or virtual wallet that LNbits sets up automatically as soon as no valid funding source is available. You can still use the LNbits server, but the wallet cannot be used. Transactions are not possible because there is no Lightning wallet behind it. We will configure the Phoenix Wallet in a moment, but first press CTRL+C to stop the process.

LNbits Autostart Service

Open the lnbits.service file:

sudo nano /etc/systemd/system/lnbits.service

Fill the file with:

[Unit]
Description=LNbits
Wants=phoenixd.service
[Service]
ExecStartPre=/bin/sleep 2
WorkingDirectory=/home/blitzbank/lnbits
ExecStart=/home/blitzbank/.local/bin/uv run lnbits --port 5000
User=blitzbank
Restart=always
TimeoutSec=120
RestartSec=30
Environment=PYTHONUNBUFFERED=1
[Install]
WantedBy=multi-user.target

-> CTRL+X -> Y -> Enter

sudo systemctl enable lnbits
sudo systemctl start lnbits
sudo systemctl status lnbits

-> Leave the status display with q.

From now on, LNbits starts automatically with every server start and runs in the background. ⚙️

Check the LNbits log:

sudo journalctl -u lnbits -f --since "2 hour ago"

6. The Caddy Web Server

Important: Make sure that, at your domain provider, the DNS records (A and AAAA) of your subdomain/domain point to the IP address of your Virtual Private Server, so that requests via the domain are forwarded to the VPS. If you don’t have a domain yet, you can get a free subdomain from duckdns.org. I wrote something about it under point 7.11.

Install Caddy

sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo apt update
sudo apt install caddy

-> Test the web server in your internet browser with: http://yourIPaddress. Note: This doesn’t work with every browser.

Configure the Caddyfile

sudo nano /etc/caddy/Caddyfile

Attention: Replace yourdomain.com with your domain in three places.

yourdomain.com {
  handle /api/v1/payments/sse* {
    reverse_proxy 127.0.0.1:5000 {
      header_up X-Forwarded-Host yourdomain.com
      transport http {
         keepalive off
         compression off
      }
    }
  }
  reverse_proxy 127.0.0.1:5000 {
    header_up X-Forwarded-Host yourdomain.com
  }
}

-> CTRL+X -> Y -> Enter

sudo systemctl reload caddy

After a short delay, Caddy should have obtained all the necessary certificates, and you can check the web server with your internet browser. Simply enter yourdomain.com, and your LNbits server should be displayed. 🎉 You now have a public HTTPS website encrypted with TLS. Caddy takes care of renewing the certificate for you. You can test the certificate itself, e.g. with ssllabs.com. Simply enter your domain and click Submit.

Here are two more useful commands to check the status and the logs of the Caddy server:

sudo systemctl status caddy
sudo journalctl -u caddy -f --since "2 hour ago"

7. Setting Up the Bank

Activate the LNbits Admin User Interface (UI) / Super User Account

sudo nano ~/lnbits/.env 

Change the following line (about line 12) from false to true:

LNBITS_ADMIN_UI=true

-> CTRL+X -> Y -> Enter

sudo systemctl restart lnbits

Now open your LNbits server again. You should see the page yourdomain.com/first_install. There you have to assign a Username and a Password to the super user.

Then click “LNbits Wallet” at the top left and then “Export to Phone with QR Code” on the right. Below the QR code you will see the button COPY WALLET URL. Copy the URL and store it safely, because it is your access to the Super User Account, which has all administrator rights.

Note: If you accidentally skip the first_install page during setup or otherwise get no access, you can also get the wallet ID for the super user with a command:

cat ~/lnbits/data/.super_user ; echo

You will now see the wallet or account ID as a string, e.g.: 01544859c4644397b826e4106ef20ccb. With it you can now log in under Login with user ID.

You can see at the top left that this is the Super User Account. For better identification, rename the wallet accordingly. Simply click the wallet on the left, then you will see the option Rename Wallet on the right. There you can rename the wallet to SuperUser.

Recommendation: Now log out at the top right under My Account and use the Super User Account from now on only in the incognito window of your browser. This gives you a little more security, and you can have two accounts open at the same time, since all other users use the normal browser window. It is best to use the wallet and the extensions of the Super User Account only for administrative management. For all other purposes you can create normal user accounts.

Marrying Phoenix and LNbits

Your LNbits is already running, but it still has the VoidWallet configured, i.e. a dummy wallet. Now you have to store the access data of the Phoenix Wallet in LNbits so that LNbits gets access to the wallet.

Show the Phoenix Wallet API
cat ~/.phoenix/phoenix.conf ; echo

The string after http-password= is your API key, which you will need in a moment.

Store the Phoenix API Key in LNbits

Open the super user account and go to Server / Funding Source. Click Void Wallet and set it to Phoenixd. Replace PHOENIX_KEY with the Phoenix API key. The endpoint can stay as it is. Then click SAVE and afterwards RESTART SERVER. If you don’t get an error message, you have now stored the Phoenix Wallet as the funding source on the LNbits server. 🏆

Feel free to check this again with the LNbits log files:

sudo journalctl -u lnbits -f --since "2 hour ago"

-> SUCCESS | ✔️ Backend PhoenixdWallet connected and with a balance of 0 msat. 🔥

-> CTRL+C

Restart the Entire VPS Once
sudo systemctl reboot

-> Wait a moment and then log in again: ssh blitzbank@yourIPaddress

Fund the Bank

Now you have to initiate the opening of a Lightning channel with an initial payment. To do so, open an incognito browser and log in with the SuperUser. Copy the string you saved earlier into the address bar of the browser and press ENTER. Your Super User Account should then appear. Here you can fund the Phoenix Wallet so that ACINQ (Phoenix) opens a Lightning channel for you. Click CREATE INVOICE. Enter “100,000 satoshis” under Amount and “funding” under Memo, then confirm with CREATE INVOICE. The Lightning invoice is displayed to you as a QR code. Scan it with your Lightning wallet and pay the invoice. That’s it! Now you have a “self-managed Blitz⚡Bank”

Phoenix takes care of everything else for you in the background and opens a 2,000,000-satoshi Lightning channel that is “dual funded”. The channel has both inbound and outbound liquidity. This means you can use it to send payments (outbound) and also to receive them (inbound). Of the 100,000 satoshis you paid, Phoenix uses about 30,000 satoshis for the channel opening fees (on-chain fees) as well as the setup fees for the service and the provision of the inbound liquidity. Phoenix commits funds in the channel for you, so that you have inbound liquidity without having to adjust the channel yourself.

The wallet of the SuperUser now shows a balance of 100,000 satoshis. That is only half the truth, however: LNbits credits this amount in the database, which means that 100,000 satoshis are also booked in the Lightning channel of the funding wallet. However, 30,000 satoshis of fees have already been deducted there. You can also check the actual balance of the funding source in the SuperUser account. Under Server / Funding / Wallets Management you will find information about your funding source. The LNbits balance should be 100,000 satoshis, while your node balance is 70,000 satoshis – that is your real liquidity. The difference of 30,000 satoshis corresponds to the fees.

Now you can create a new user in parallel to the SuperUser. To do so, open your Blitz⚡Bank in the normal browser and use Create New Wallet to create a new wallet named “Start”. On the right you will find the option Export to Phone with QR Code and below the QR code the button COPY WALLET URL. You should store this URL safely. For a better overview in the database, click My Account at the top right and give the account a user name. An account/user can contain several wallets. You get access to your account via the URL link or the user ID, which you will find directly above it. You get back to the overview by clicking the wallet “Start” on the left.

Do you want to check the status of the Lightning channel?
~/phoenixd/phoenix-cli listchannels | grep "txId"

-> Copy the txId and have it displayed on mempool.space.

More Info About Your Channel Balance
~/phoenixd/phoenix-cli getinfo

-> balanceSat, inboundLiquiditySat and capacitySat

Info: The balanceSat should be identical to the display of the Node Balance, which you can find in the super user account under Server / Funding.

Backups

You have backed up the Phoenix seed, so you can restore the wallet at any time. What the seed does not contain, however, is the LNbits database with all accounts, wallets, balances and extensions, as well as the .env file with your settings. Without a backup, your users’ balances cannot be reconstructed after a server failure. By default, the database is located in ~/lnbits/data/database.sqlite3.

That is why you should back up in three stages: First, use the automatic backups or snapshots of your VPS provider, if it offers them. This usually costs a few euros per month and backs up the complete system. Second, pull a copy of the database to your PC every now and then; the .env file also contains credentials and should be backed up as well. Third, set up a cron job that regularly creates a backup and transfers it to a second server. A backup on the same server does not protect against losing the server.

-> You will find step-by-step instructions for the manual backup, the restore and the cron job on the page Blitz⚡Bank – Extras in chapters 3.3 and 3.4.

Note: Only restore an old database backup if it is necessary. The LNbits balances and the Phoenix wallet have to match. An old database state may have forgotten payments that Phoenix has already booked.

8. Done

Congratulations, you now have your own Bitcoin Lightning⚡Bank in self-custody! You have a full-fledged wallet and an account system with many expansion options in the frontend, as well as a self-custodial funding source in the backend. With LNbits you also have a powerful tool to really exploit the potential of Lightning. LNbits offers a large number of extensions with which you can, for example, create static pay links, Lightning addresses, vouchers, paywalls, split payments, point of sale terminals (PoS), the BitcoinSwitch and much more. You now have the power; you are sovereign in terms of Lightning and can offer friends and family a trustworthy environment.

There is still a lot to tell about the Phoenix Wallet and LNbits. But I would like to end the tutorial here for now. The basics are laid, the Blitz⚡Bank is fully functional and you can test it extensively. You can find my demo server for this tutorial at blitzbank.ereignishorizont.xyz. It is equipped with a small selection of extensions. The wallet size is limited to a maximum of 10,000 satoshis, since it is only a demonstration.

If you are looking for more information, take a look at the appendix. There you will also find a link to another page with tips, tricks and further information about the Blitz⚡Bank.

Thank you very much for your attention.

Stay Humble & Stack Sats

Axel

9. Appendix

Acknowledgements and References 🧡

Thanks to Yvette and Daniel for their work, which I was able to build on.
Yvette on GitHub: github.com/arbadacarbaYK
Daniel’s blog: danielpcostas.dev

Further Sources 📚

Phoenix Server: https://phoenix.acinq.co/server
LNbits Server: ereignishorizont.xyz/lnbits-server
LNbits docs: docs.lnbits.org

Tips, Tricks and Other Things About the Blitz⚡Bank

See page: Blitz⚡Bank – Extras


Made with love 🧡 Since 866520 / 973870