loop/docs/release-notes/release-notes-next.md
Boris Nagaev 95e184a40f
loopd: account for channel reserves in loop out validation
Use each channel's local balance minus its reserve when simulating Loop
Out payment bandwidth, clamping the result at zero. This prevents swaps
from starting when the gross balance covers the amount and routing fee
but the spendable balance does not.

Add one-sat boundary tests and a bug-fix release note. Leave a TODO for
server-fee and prepay capacity because enforcing their maximum fee caps
could reject viable swaps whose actual routing fees are lower.
2026-08-10 18:48:56 -05:00

24 lines
786 B
Markdown

# Loop Client Release Notes
#### New Features
#### Breaking Changes
#### Bug Fixes
* Loop Out requests now account for channel reserves when checking outbound
capacity, preventing swaps from starting when their off-chain payment cannot
be funded.
* Taproot Asset Loop Out handling now validates RFQ timeouts and asset rates,
keeps cached asset-name lookups responsive during slow `tapd` queries, and
closes `tapd` connections cleanly during shutdown and startup failures.
[PR #1189](https://github.com/lightninglabs/loop/pull/1189)
#### Maintenance
* Added a CI gate and repository agent guidance requiring every pull request to
include a non-empty entry in the next release notes unless it carries the
`no-changelog` label.
#### Contributors (Alphabetical Order)