v0.11.2-beta

Autoloop Swap Size

• Autoloop can now be configured with custom swap size limits. Previously,
  autoloop would use the minimum/maximum swap amount set by the server (exposed
  by the loop terms command) to decide on swap size.
• Setting a custom minimum swap amount is particularly useful for clients that
  would like to perform fewer, larger swaps to save on fees. The trade-off when
  setting a large minimum amount is that autoloop will wait until your channel is
  at least the minimum amount below its incoming threshold amount before executing
  a swap, which may result in channels staying under the threshold for longer.
• These values can be set using the following command: loop setparams --minamt={minimum in sats} --maxamt={maximum in sats}.
• The values set must fall within the limits set by the loop server.

v0.11.1-beta

NewFeatures

• When requesting a swap, a new initiator field can be set on the gRPC/REST
  interface that is appended to the user agent string that is sent to the server
  to give information about Loop usage. The initiator field is meant for user
  interfaces to add their name to give the full picture of the binary used
  (loopd, LiT) and the method/interface used for triggering the swap (loop
  CLI, autolooper, LiT UI, other 3rd party UI).

v0.11.0-beta

New Features

• The loop client now labels all its on-chain transactions to make them easily
  identifiable in lnd's listchaintxns output.

Introducing Autoloop

• This release includes support for opt-in automatic dispatch of loop out swaps,
  based on the output of the Suggestions endpoint.
• To enable the autolooper, the following command can be used:
  loop setparams --autoout=true --autobudget={budget in sats} --budgetstart={start time for budget}
• Automatically dispatched swaps are identified in the output of the
  ListSwaps with the label [reserved]: autoloop-out.
• If autoloop is not enabled, the client will log the actions that the
  autolooper would have taken if it was enabled, and the Suggestions endpoint
  can be used to view the exact set of swaps that the autolooper would make if
  enabled.

v0.10.0-beta

Version 0.10.0-beta

New Features

• Multi-path payment has been enabled for Loop In. This means that it is now possible
  to replenish multiple channels via a single Loop In request and a single on-chain htlc.
  This has to potential to greatly reduce chain fee costs. Note that it is not yet possible
  to select specific peers to loop in through.
• The daemon now sends a user agent string with each swap. This allows
  developers to identify their fork or custom implementation of the loop client.

Updated Swap Suggestions

• The swap suggestions endpoint has been updated to be fee-aware. Swaps that
  exceed the fee limits set by the liquidity manager will no longer be
  suggested (see getparams for the current limits, and use setparams to
  update these values).
• Swap suggestions are now aware of ongoing and previously failed swaps. They
  will not suggest swaps for channels that are currently being utilized for
  swaps, and will not suggest any swaps if a swap that is not limited to a
  specific peer or channel is ongoing. If a channel was part of a failed swap
  within the last 24H, it will be excluded from our swap suggestions (this
  value is configurable).
• The debug logging level is recommended if using this feature.

Breaking Changes

• Macaroon authentication has been enabled for the loopd gRPC and REST
  connections. This makes it possible for the loop API to be exposed safely over
  the internet as unauthorized access is now prevented.

  The daemon will write a default loop.macaroon in its main directory. For
  mainnet this file will be picked up automatically by the loop CLI tool. For
  testnet you need to specify the --network=testnet flag.
  More information about TLS and macaroons.

• The setparm loopcli endpoint is renamed to setrule because this endpoint
  is only used for setting liqudity rules (parameters can be set using the new
  setparams endpoint).

v0.9.0-beta

In this patch release:

Potentially Breaking Changes

• TLS encryption is introduced and is now required to communicate with the Loop daemon API
• Support is discontinued in binary releases for Darwin 386 (32 bit Mac)

New Features

• A liquidity management system is introduced to drive automated Loop actions based on desired liquidity
  • Fully automated Loop actions are not yet included, this release introduces suggested actions that can be executed using the API, or in the future can be directed to be executed automatically.
• A rewrite of the on-chain script is introduced that is a bit cheaper on-chain in the successful case

Fixes

• The Docker image Go version is increased to Go 1.13

v0.8.1-beta

In this patch release:

• The Loop Out pathfinding timeout is increased to help discover lower fee routes for larger amounts
• The Loop Out default sweep confirmation target is extended to help lower on-chain fees for Loop Outs
• Preparatory support is included for an upcoming update to the on-chain script
• Support is added to choose your own directory for Loop's database and log files

v0.8.0-beta

In this minor release:

• More details into swap failure causes are surfaced to help better understand how to fix issues encountered with swap execution
• The new LND 0.11.0 chain transaction labeling feature is used to record in the LND db which txs are Loop-related
• You can now specify the number of confirmations to wait before considering the swap service's on-chain send to you to be confirmed

v0.7.0-beta

In this minor release:

• Loop Out confirmation targets can now be much longer, resulting in potentially much cheaper Loop Out on-chain costs
• The Loop server has been upgraded to supply a state subscription service to supply indications of server-side swap status

v0.6.5-beta

In this patch release:

• Added support for a human-readable message from the server. The message is received after initiation of a swap and printed to the log. It is also exposed as a field on the client RPC interface.

• Several bugs fixes and security improvements.

v0.6.4-beta

In this patch release:

• A loopd error will now terminate with exit code 1 instead of exit code 0 to assist auto-restarting
• Loop Out will now increase inbound liquidity more quickly in situations where low chain fees were specified

If you have time to wait for the funds to return to you on-chain, consider increasing --conf_target from the default of 6 when running the loop out command to achieve fee savings at the cost of slower swap finality.