You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
85 lines
3.1 KiB
85 lines
3.1 KiB
manifestVersion: 1
|
|
id: lightning-terminal
|
|
category: bitcoin
|
|
name: Lightning Terminal
|
|
version: "0.11.0-alpha"
|
|
tagline: The easiest way to manage channel liquidity
|
|
description: >-
|
|
Lightning Terminal is the easiest way to manage inbound and
|
|
outbound liquidity on the Lightning Network. Keep your channels open and the
|
|
funds flowing. It provides a visual interface for interacting with your
|
|
channels and balances using Loop.
|
|
|
|
|
|
New: Introducing Lightning Pool, a marketplace for Lightning channels. You can now earn sats by opening new channels to those looking to receive funds on Lightning for a set period of time, or rent a channel to start accepting payments instantly. Join the marketplace and start putting your Bitcoin to work.
|
|
|
|
|
|
Why use Pool?
|
|
|
|
- Earn a return on Lightning capital
|
|
|
|
- Rent a channel and start accepting payments instantly
|
|
|
|
- Open channels for less with transaction batching
|
|
|
|
|
|
Why use Loop?
|
|
|
|
- Add "inbound liquidity" to receive payments
|
|
|
|
- Reduce transaction fees by recycling and reusing Lightning channels
|
|
|
|
- Send funds to and from users or services that aren't yet Lightning enabled
|
|
|
|
- Configurable wait times and "batching" allow for further fee savings
|
|
|
|
- Refill and offload funds from any number of Lightning channels in a single on-chain transaction
|
|
developer: Lightning Labs
|
|
website: https://lightning.engineering
|
|
dependencies:
|
|
- lightning
|
|
repo: https://github.com/lightninglabs/lightning-terminal
|
|
support: https://github.com/lightninglabs/lightning-terminal/issues/new
|
|
port: 3004
|
|
gallery:
|
|
- 1.jpg
|
|
- 2.jpg
|
|
- 3.jpg
|
|
- 4.jpg
|
|
path: ""
|
|
defaultUsername: ""
|
|
deterministicPassword: true
|
|
releaseNotes: >-
|
|
This release of Lightning Terminal (LiT) updates the integrated LND daemon
|
|
version to the latest v0.17.0-beta release, as well as updates the
|
|
integrated Loop daemon to the latest patch release.
|
|
|
|
|
|
In this release of LiT, a new Status server was added, which enables users
|
|
to disable the different integrated sub-servers and the integrated accounts
|
|
sub-system in LiT through configuration. LiT will now also successfully
|
|
start even if any of the sub-servers or sub-systems fails to start.
|
|
|
|
|
|
This release of LiT also enables the ability to link a new Autopilot
|
|
session with an old session, as well as enabling the ability to specify
|
|
feature configurations for an Autopilot session.
|
|
|
|
|
|
One important change to note for users running LiT through docker, is that
|
|
due to the new status server feature, the startup process of LiT will not
|
|
error and end if a sub-server or sub-system fails to start. So any
|
|
platforms that rely on docker to automatically restart the LiT container
|
|
if the startup process ends due to the sub-servers or sub-system not having
|
|
started yet, will now not restart the container as the start process won't
|
|
exit.
|
|
|
|
|
|
We'll be continuously working to improve the user experience based on
|
|
feedback from the community.
|
|
|
|
|
|
This release packages LND v0.17.0-beta, Taproot Assets Daemon v0.2.3-alpha,
|
|
Loop v0.26.3-beta, Pool v0.6.4-beta and Faraday v0.2.11-alpha.
|
|
submitter: Umbrel
|
|
submission: https://github.com/getumbrel/umbrel/pull/348
|