|
|
|
# Loop Client Release Notes
|
|
|
|
This file tracks release notes for the loop client.
|
|
|
|
|
|
|
|
### Developers:
|
|
|
|
* When new features are added to the repo, a short description of the feature should be added under the "Next Release" heading.
|
|
|
|
* This should be done in the same PR as the change so that our release notes stay in sync!
|
|
|
|
|
|
|
|
### Release Manager:
|
|
|
|
* All of the items under the "Next Release" heading should be included in the release notes.
|
|
|
|
* As part of the PR that bumps the client version, cut everything below the 'Next Release' heading.
|
|
|
|
* These notes can either be pasted in a temporary doc, or you can get them from the PR diff once it is merged.
|
|
|
|
* The notes are just a guideline as to the changes that have been made since the last release, they can be updated.
|
|
|
|
* Once the version bump PR is merged and tagged, add the release notes to the tag on GitHub.
|
|
|
|
|
|
|
|
## Next release
|
|
|
|
|
|
|
|
#### New Features
|
|
|
|
|
|
|
|
* Sweep Batcher: A new sub-system was added that handles all the loopout
|
|
|
|
sweeps. Successful loopout HTLCs will no longer be swept back to the wallet via
|
|
|
|
individual transactions but will instead form a single transaction that holds
|
|
|
|
multiple inputs and pays to a single output. This will significantly reduce
|
|
|
|
chain fee costs as it's using less block space by directly consolidating all the
|
|
|
|
htlcs to a single address. Loopouts that pay to non-wallet addresses will still
|
|
|
|
use individual transactions as their output cannot be mutated.
|
|
|
|
|
|
|
|
|
|
|
|
#### Breaking Changes
|
|
|
|
|
|
|
|
#### Bug Fixes
|
|
|
|
|
|
|
|
#### Maintenance
|