Ride The Lightning - A full function web browser app for LND, C-Lightning and Eclair
Ride The Lightning - A full function web browser app for LND, C-Lightning and Eclair
Intro -- Application Features -- Road Map -- Application Configurations -- Core Lightning -- Eclair -- Contribution -- Release Notes
RTL is a full function, device agnostic, web user interface to help manage lightning node operations. RTL is available on LND, CoreLightning and Eclair implementations.
Pre-requisite for running RTL is a functioning and synced LND node. If you are a Raspberry Pi or a Linux user, you can follow the famous Stadicus's guide to setup a Bitcoin + Lighting node.
RTL is available on the below platforms/services:
Docker Image: https://hub.docker.com/r/shahanafarooqui/rtl
To download a specific RTL version follow the instructions on the release page
To download from master (not recommended):
$ git clone https://github.com/Ride-The-Lightning/RTL.git
$ cd RTL
$ npm ci --omit=dev --legacy-peer-deps
$ cd RTL
$ git reset --hard HEAD
$ git clean -f -d
$ git pull
$ npm ci --omit=dev --legacy-peer-deps
RTL requires its own config file RTL-Config.json, to start the server and provide user authentication on the app.
Advanced users can refer to this page, for config settings required to manage multiple nodes
Sample-RTL-Config.json to RTL-Config.json located at./RTL.RTL-Config.json file per the example file belowExample RTL-Config.json:
…
For details on all the configuration options refer to this page.
RTL requires the user to be authenticated by the application first, before allowing access to LND functions.
Specific password must be provided in RTL-Config.json (in plain text) for authentication. Password should be set with multiPass: in the Authentication section of RTL-Config.json. Default initial password is password.
For hosted solutions such as BTCPayServer, we implemented an "SSO" setup using a one-time-use cookie. For other vendors which have their own authentication service, we introduced a "disableAuth" option, which disables authentication at the RTL level. When using this option, the authentication security is the responsibility of the Vendor. This option is NOT recommended for standalone users of RTL.
Run the following command:
$ node rtl
If the server started successfully, you should get the below output on the console:
$ Server is up and running, please open the UI at http://localhost:3000 or your proxy configured url.
In case you are running a headless Rpi or a Linux node, you can configure RTL as a service.
# Raspibolt RTL: systemd unit for RTL
# /etc/systemd/system/RTL.service
[Unit]
Description=RTL daemon
Wants=lnd.service
After=lnd.service
[Service]
ExecStart=/usr/bin/node /rtl
User=
Restart=always
TimeoutSec=120
RestartSec=30
[Install]
WantedBy=multi-user.target
$ sudo systemctl enable RTL
$ sudo systemctl start RTL
$ sudo journalctl -f -u RTL
You can access the application in multiple setups (Please make note of the 4th exception):
Same device as the server: Open your browser at the following address: http://localhost:3000 to access the RTL application.
Remotely from another device on the same local network (home network) as the node(RTL server+LND running on the same device):
Config tweaks for running RTL server and LND on separate devices on the same network can be found here.
Any Other setup: Please be advised, if you are accessing your node remotely via RTL, its critical to encrypt the communication via use of https. You can use solutions like nginx and letsencrypt or TOR to setup secure access for RTL.
RTL holds your node's credentials, so a security flaw in RTL could let an attacker act on your node — including moving funds. Please report security vulnerabilities privately — not in a public issue. See SECURITY.md for the reporting channels (GitHub private vulnerability reporting or email), the PGP key, what is in and out of scope, and what to expect after you report.
In case you are running into issues with the application or if you have feedback, feel free to open issues on our github repo. You can also reach out to us via twitter DM on @Suheb__ or @RTL_App. Thanks for your interest. (For security vulnerabilities, please use the channels in SECURITY.md rather than a DM or a public issue.)
No open issues yet, or sync has not completed.