Releases: itsneski/lightning-jet
v1.6.0-db-cleanup
jet 1.6.0
This release automates the removal of old db records (#99). Jet will automatically purge old records, keeping the database size manageable.
In addition, this release introduces logging improvements (#102). All logging will now be done using a central facility, with a standardized log format. By default, jet will limit the amount of logging to info, error, and warning messages, with an option to set the logging level to debug
.
Other changes:
jet probes --peers
- new option to return stats on the current peersjet list-channels
- now shows channels in pending open state
How to upgrade:
git pull
npm install
jet restart all
v1.5.5-exclude
jet 1.5.5
This release adds telegram notifications in case of issues with the rebalancer exclude
setting. Jet will notify if the exclude
is malformed or if the nodes are no longer present in the peer list.
Other changes:
- fixed #97: jet no longer rebalances from/to an [excluded] peer in follow-up to a forward
- fixed #98: excessive number of SQLITE_CONSTRAINT errors in jet-worker.log
How to upgrade:
git pull
jet restart all
v1.5.4-probes
jet 1.5.4
This release introduces a new tool, jet probes
, that displays nodes (discovered during probes) that have signaled a commitment to liquidity. This tool can be used to identify prospects for new channels.
In addition, this release upgrades sqlite library to version 5.1.2. This upgrade adds further stability to jet when working with increased database sizes.
Other changes:
- added support for jet on Ubuntu vm
jet info
now accepts node or channel id as an argument- fixed occasional 'SQLITE_BUSY: database is locked' exceptions that cause telegram daemon to exit
How to upgrade:
git pull
npm install
jet restart all
v1.5.3-liquidity
jet 1.5.3
This release optimizes liquidity allocation for low-volume peers. Jet attempts to revive low-volume peers by moving small amounts of liquidity to the local side. This release caps the liquidity proportionally to the total channel capacity.
In addition, this release eliminates occasional rebalances that happen in the absence of forwards. Jet now factors pending htlcs (on forwards) into the rebalancing algo.
Other changes:
jet info
is a new tool that shows basic node stats like bitcoin balance, number of channels, etcjet stats
now shows a breakdown of forwarded sats into inbound and outbound- fixed occasional 'SQLITE_BUSY: database is locked' exceptions that cause daddy to exit
- updated dependencies, make sure to run
npm install
How to upgrade:
git pull
npm install
jet restart all
v1.5.2-reliability
jet 1.5.2
This release introduces several reliability enhancements. Jet segments execution of daemons and individual rebalances into separate processes for added reliability. Sometimes rebalance processes get stuck; this happens rarely but it was observed. Stuck processes may consume extra resources (CPU & mem), preventing jet from launching new rebalances (max rebalance instance count). To prevent this from happening, jet now tracks how long processes have been running and terminates processes that ran over the max.
Logger daemon now has its own lnd [is alive] check. This eliminates redundant telegram start/stop notifications when lnd is shutdown or restarted.
Worker daemon now records heartbeat in the local database. This lets daddy [watchdog] daemon know that the service is alive and does not need to be restarted.
Other changes:
Channel database size notification thresholds increased from 2 to 4gb for a warning, for 5 to 8gb for a serious warning, and from 8 to 16gb for an urgent warning.
How to upgrade:
git pull
jet restart all
v1.5.1-metrics
jet 1.5.1
This release introduces profitability metrics via jet stats
. Node operators can now see how many sats they earned or lost over a particular time period. They can also compare metrics from different time periods, including routing volume metrics, per-channel and cumulative metrics.
In addition, this release introduces a new daemon, worker, that is responsible for a variety of management tasks, such as reconnecting inactive peers, populating database tables, detecting inactive peers, etc.
The log file names have been standardized and aligned with the service names. The following table reflects the changes:
daemon | log name | old name |
---|---|---|
daddy |
jet-daddy.log | launcher.log |
worker |
jet-worker.log | |
logger |
jet-logger.log | htlc-logger.log |
telegram |
jet-telegram.log | telegram.log |
rebalancer |
jet-rebalancer.log | rebalancer.log |
Other changes:
- fixed #89: lnd connect error for nodes in voltage.cloud
How to upgrade:
git pull
jet restart all
v1.5.0-lnd15
jet 1.5.0
This release enables compatibility with lnd15. The underlying bos
and grpc
libraries have been updated to the latest version. Library packages have been audited and dependencies fixed.
Important:
- run
npm install
aftergit pull
- change
readonly.macaroon
toadmin.macaroon
inapi/config.json
Other changes:
- fixed #88: Logger stop/start messages repeat forever in Jet Bot if LND is remote
- fixed #86: Rebalancer Not Working (ERR in lnd.log: permission denied)
- fixed #85: Running "jet monitor" against voltage.cloud returns async hook corruption Error
- fixed #84: jet analyze-fees crashed on a channel with incomplete data
How to upgrade:
Change readonly.macaroon
to admin.macaroon
in api/config.json
git pull
npm install
jet restart all
v1.4.4-embassy
jet 1.4.4
This release introduces support for EmbassyOS. Jet can now rebalance channels on Start9 products that run EmbassyOS. In addition this release introduces important stability fixes.
Other changes:
- jet now shows hours and minutes in telegram notifications about inactive peers
jet monitor --current
now displays rebalances in-flight (a subset of what's displayed injet monitor
)jet htlc-history
has a new margin column that shows rebalance margin for peers- jet has a new
disable
flag under the rebalancer config section that disables auto-rebalancer - fixed #55: rebalance instances over-limit
- fixed #81: jet errors out on an unknown/non-existing peer
How to upgrade:
git pull
jet restart all
v1.4.3-voltage
jet 1.4.3
This release introduces support for rebalancing nodes in Voltage Cloud. Jet can now rebalance your node in Voltage Cloud by connecting to it remotely via a secure grpc connection.
Other changes:
- fixed #74: jet shows occasional 'started logger' telegram notifications
How to upgrade:
git pull
jet restart all
v1.4.2-inactive-channels
jet 1.4.2
This release enhances the monitoring of inactive channels and provides a deeper insight into rebalance history via jet rebalance-history
.
Jet introduces jet channel-events
, a new tool that shows the history of channel events, e.g. channels becoming inactive/active. Jet now shows a list of inactive channels and how long channels have been inactive in jet channel-events
and jet list-channels
. In addition, Jet notifies via telegram when channels have been inactive for too long.
jet rebalance-history
now shows when rebalances started, how long they ran, and the type of rebalance (regular, low volume, missed, forward). This allows node operators get a deeper insight into Jet's behavior for launching rebalances.
Other changes:
jet update-channel
can now be called on a partial peer alias or a pub id.- jet now ensures that rebalance sats on forwards are above threshold.
- jet now logs extra information on unrecognized/unknown rebalance errors.
- jet now better handles exceptions when reconnecting peers.
- fixed #66: jet list-channels fails with a null error.
- fixed #71: File search code appears to truncate path.
How to upgrade:
git pull
jet restart all