Skip to content

Releases: benharold/voltage

Initial Release

23 Aug 23:53
Compare
Choose a tag to compare
Initial Release Pre-release
Pre-release

Voltage 0.1.0

Disclaimer

This is alpha quality software and should be treated as such. I have personally only used this with a testnet node. Use at your own risk.

That being said, this software does not touch any sensitive information on your computer. It's simply a GUI that communicates with c-lightning via RPC-JSON, in a similar manner to how lightning-cli communicates with c-lightning.

General Information

This is the first alpha release of Voltage, a macOS GUI for c-lightning written in Swift.

In order to use Voltage you must have a c-lightning node running either locally, or on a remote machine which is accessible via public-key authentication over SSH.

I've personally only used Voltage to connect to a remote c-lightning node running on a Gentoo box, so I'd be happy to hear of your experience using it under any other configuration.

Setup

Local

The first time you run Voltage, it will attempt to connect to your local c-lightning node. If an RPC connection to a local node cannot be established, you will be prompted with the Preferences window to setup your connection.

For a local connection, just type the path to your c-lightning RPC socket in the "Socket path" field of the Voltage preferences, then hit the "Test Connection" button. You will be alerted as to whether or not the connection was successful.

Remote

In order to use Voltage to control your remote c-lightning node, the machine on which your node resides must be accessible via SSH and you must have public-key authentication enabled.

When you first open Voltage, if you don't have a local c-lightning node, you will be promted with the Preferences window to setup your connection.

Click on the "Remote" radio button to bring up the remote connection parameters. All of the parameters you enter are for the remote machine, including the socket path. You must use the IP address (not a domain name) of the remote machine and the port over which SSH is enabled. This is typically 22, but some folks map it to 2222 or something even sillier, as if nmap didn't exist.

Troubleshooting

If you are having trouble connecting, you may be able to glean some useful information from the Debug window (⌘D). If you're still having trouble, I'd be happy to help. Just open an issue in the GitHub repo and describe what's going on, including the output of the Debug window if it seems relevant.