Run your own Lightning node
Self-hosted node for bitcoin-blake2b, controlled from the app
Before downloading: get the installer only from this page (domain btcblake2b.org) or from the official GitHub repository.
Release v0.1.0 — package tlw-node-installer-0.1.0.tar.gz, with SHA256SUMS covering the package and the bridge binary.
Verify the checksum (SHA-256)
The file tlw-node-installer-0.1.0.tar.gz must have this hash:
SHA256(tlw-node-installer-0.1.0.tar.gz) = 3040a213d2e16afc5ec2bb78e3f998cd7b8adb8816be86edb77f8d4c731130f6
Verify on Linux
sha256sum tlw-node-installer-0.1.0.tar.gz
Verify on Windows (PowerShell)
Get-FileHash .\tlw-node-installer-0.1.0.tar.gz -Algorithm SHA256
Install (3 commands)
tar -xzf tlw-node-installer-0.1.0.tar.gz
cd tlw-node-installer-0.1.0
./install.sh --bitcoind-rpc rpcuser:[email protected]:8332
Run it as your regular user: sudo is never required.
At the end the installer prints an NWC/NCC URI: paste it in the app (Lightning → Connect) to control the node. The URI contains a secret — never share it: each device is individually authorized and can be revoked.
Requirements
- Ubuntu 22.04 / 24.04 / 26.04 (x86_64)
- A reachable bitcoind blake2b via RPC (the full node is not included)
curlandpython3(standard on Ubuntu)
What the installer does
- installs Core Lightning (blake2b fork) and the NWC/NCC bridge, each with a pinned SHA-256: any mismatch stops the installation (fail-closed);
- creates a dedicated rune on the node and an authorization URI per device;
- everything is user-level (
~/cln-blake2b,~/bridge,~/.lightning): no system changes, no root; --uninstallremoves binaries and configuration but never touches the wallet datadir (funds, channels, keys stay).
Security & trust
- self-hosted by design: the node runs on your server; nobody else can operate it;
- the bridge accepts requests only from devices you authorized;
- step-by-step guide, FAQ and threat model: installer documentation.
⚠️ Important notice — This is an experimental network. The node software is provided without warranty under the MIT license: use it only after understanding the risks and verifying the integrity of the package.