Skip to content

Releases: ZmnSCPxj/clboss

Bwahaha's Dominion

24 Jul 20:39
v0.13.2
11a16bb
Compare
Choose a tag to compare

Added

  • Added signet support ([#148]).
  • Updated the seeds list ([#208],
  • Added module diagrams for channel creation, offchain to onchain
    swaps, and channel balancing ([#200], [#203]).

Changed

  • testnet: Reduce the min_nodes_to_process because testnet is shrinking ([#209]).
  • Improve listpeers handling diagnostics ([#214], [#215]).
  • Improve Initialization of OnchainFeeMonitor with Conservative
    Synthetic History ([#210]).

Fixed

  • Converted deprecated listpeer usage to listpeerchannels ([#213], [#198]).
  • Recognize --developer CLI flag and don't exit giving usage ([#185], [#216])).

v0.13.1: E Street Fix

07 May 22:15
v0.13.1
Compare
Choose a tag to compare

Fixes for CLN RPC changes

v0.13: Born to Run

09 Sep 00:35
9dc326a
Compare
Choose a tag to compare
  • Updated to CLN v23.05's JSON-RPC amount convention. Should be able to handle previous convention as well.
  • Continuous Integration restored by @vincenzopalazzo!
  • Various fixes and cleanup

0.13A: Candidate for Weaksauce Weakness

12 May 23:12
Compare
Choose a tag to compare
Pre-release
  • Improved performance for nodes with >100 peers.
  • Disable InitialRebalancer because it just is not economically rational.
  • Allow disabling rebalancer by new clboss-unmanage tag balance.

As is usual, download the official release tarball clboss-0.13A.tar.gz, untar, and ./configure && make and update your lightningd config file.

0.12 Not Completely Useless

30 Apr 06:47
Compare
Choose a tag to compare

This is exactly the same release as 0.12, and only exists for back-compatibility with processes which might be using "v" before the version number when referring to release tags. Future releases will no longer have "v" before the version number in their release tags. CopyPasta below.

Oh no, a new version of some completely useless piece of software!

  • Version compatibility: C-Lightning 0.9.1 to 0.11
    • Most extensively tested with 0.10.2, so older versions might have subtle compatibility bugs.
    • On Core Lightning 0.11, you must set --allow-deprecated-apis to true. This is the default behavior of Core Lightning 0.11.
    • Core Lightning 0.11 supports multiple channels per peer, but this has not been tested at all with CLBOSS. CLBOSS should still adapt to multiple channels in general but this is untested.

Changes:

  • Use dig -v to check for dig installation, to prevent failing to detect if the testing environment has no network.
  • Avoid making channels to multiple nodes in the same IP bin, to make it harder to eclipse our node.
  • We now try to keep down our expenditures when rebalancing: rebalancing less often, and reducing the budget for rebalance attempts.
  • You can now use the clboss-unmanage command to suppress management of some aspect of channels with particular peers.
  • EXPERIMENTAL: CLBOSS now has the ability to monitor peers and planning to close them. CLBOSS will now monitor peers, but if you want CLBOSS to actually close "bad" peers, enable with --clboss-auto-close=true. You can also use the new clboss-unmanage to prevent closure of channels to particular nodes.
  • We are now a little more willing to leave funds onchain if the funds are small relative to the total funds (onchain and offchain) of the node.
  • Reduce the probe lengths of ActiveProber.
  • Change our threshold for "low fees" a little lower. Previously it was 25 +/- 5 percentile of the last two weeks, now it is 20 +/- 3 percentile of the last two weeks.
  • You can now support or oppose #zerobasefee with the new --clboss-zerobasefee=<require|allow|disallow> option.
  • You can now adjust the minimum and maximum channel size with --clboss-min-channel=<sats> and --clboss-max-channel=<sats>.
  • ChannelFinderByPopularity is made a little more aggressive when CLBOSS is first used (on a node that already was manually-managed before) or when the node is suddenly given a large amount of funds.
  • We now also check dowsed amounts during investigation.

Get it!

0.12 Not Completely Useless

30 Apr 06:45
Compare
Choose a tag to compare

Oh no, a new version of some completely useless piece of software!

  • Version compatibility: C-Lightning 0.9.1 to 0.11
    • Most extensively tested with 0.10.2, so older versions might have subtle compatibility bugs.
    • On Core Lightning 0.11, you must set --allow-deprecated-apis to true. This is the default behavior of Core Lightning 0.11.
    • Core Lightning 0.11 supports multiple channels per peer, but this has not been tested at all with CLBOSS. CLBOSS should still adapt to multiple channels in general but this is untested.

Changes:

  • Use dig -v to check for dig installation, to prevent failing to detect if the testing environment has no network.
  • Avoid making channels to multiple nodes in the same IP bin, to make it harder to eclipse our node.
  • We now try to keep down our expenditures when rebalancing: rebalancing less often, and reducing the budget for rebalance attempts.
  • You can now use the clboss-unmanage command to suppress management of some aspect of channels with particular peers.
  • EXPERIMENTAL: CLBOSS now has the ability to monitor peers and planning to close them. CLBOSS will now monitor peers, but if you want CLBOSS to actually close "bad" peers, enable with --clboss-auto-close=true. You can also use the new clboss-unmanage to prevent closure of channels to particular nodes.
  • We are now a little more willing to leave funds onchain if the funds are small relative to the total funds (onchain and offchain) of the node.
  • Reduce the probe lengths of ActiveProber.
  • Change our threshold for "low fees" a little lower. Previously it was 25 +/- 5 percentile of the last two weeks, now it is 20 +/- 3 percentile of the last two weeks.
  • You can now support or oppose #zerobasefee with the new --clboss-zerobasefee=<require|allow|disallow> option.
  • You can now adjust the minimum and maximum channel size with --clboss-min-channel=<sats> and --clboss-max-channel=<sats>.
  • ChannelFinderByPopularity is made a little more aggressive when CLBOSS is first used (on a node that already was manually-managed before) or when the node is suddenly given a large amount of funds.
  • We now also check dowsed amounts during investigation.

Get it!

0.11E

26 Apr 00:01
Compare
Choose a tag to compare
0.11E Pre-release
Pre-release

Someone is apparently compensating for not publishing more often.

  • Fix accidental removal of some options, instead of adding new options.

Please download the clboss-0.11E.tar.gz file, untar, then ./configure && make to compile, then point your plugin= or important-plugin= at the new compiled clboss.

0.11D

25 Apr 02:53
Compare
Choose a tag to compare
0.11D Pre-release
Pre-release

New release, after so long, sorry for the delay.

  • We now records our offchain-to-onchain swaps.
  • Fix incompatibility with recent C-Lightning.
  • Allow #zerobasefee.
  • Finding by popularity becomes aggressive when a sudden jump in funds occurs.
  • Allow minimum and maximum channel size to be set via command line.
  • Check dowsing results during investigation as well.

Download source tarball here, do not get the files auto-generated by github: https://github.com/ZmnSCPxj/clboss/releases/download/0.11D/clboss-0.11D.tar.gz

0.11B Candidate for Not Completely Useless

03 May 04:35
Compare
Choose a tag to compare

A new thing is EXPERIMENTAL auto-closing of "bad" channels. The actual closing is disabled by default, but the monitoring for "bad" peers is always enabled and you can look at the peer_complaints field of the output of clboss-status to see what CLBOSS thinks are bad peers and how bad they are and why they are bad. Make sure to keep 0.11B or later running for a month before enabling auto-close (a complainer holds off for a week to do some active probing before judging peers as bad, so you want this complainer to be doing this assessment for a few weeks before you can judge whether you agree with it or not), and check the peer_complaints field of clboss-status to see if you agree with CLBOSS assessment, before enabling auto-close. To enable auto-close, read the README.md and follow the instructions, and before that, make sure you actually agree that CLBOSS is reasonably sane by checking the peer_complaints field first.

This release does rebalancing a lot less often than previous releases. Previous releases tended to rebalance so often that you would lose significantly more money than what you earned. This release ameliorates that, but channels are now significantly more unbalanced, sadly. Some more work and experimentation on this is needed to maximize earnings.

New in this release is a reproducible binary for Linux x86-64. It is large because I included the debug symbols, I probably should not include those. The link to the reproducible binary is to an OnionShare server, which requires Tor Browser or torsocks wget, and may or may not be online 24/7, because it is 147M. However this binary contains everything CLBOSS needs and you don't have to install anything else (except dnsutils/dig, which I should include in the next release). The binary was built using GNU Guix, see the reproducible/ directory in the source tarball or repo for more info.

  • Official release tarball: clboss-0.11B.tar.gz
  • Linux x86-64 reproducible binary in OnionShare (requires Tor Browser to download, or torsocks wget): clboss-0.11B-guix-7540f69.tar.gz - sha256sum: 6644726d0ab3a46771afdb1c602083e53d0b5fc8ef722c7bf6d57e14ea99b334

0.11A: Candidate for Not Completely Useless

18 Jan 06:17
Compare
Choose a tag to compare