Releases: lightninglabs/loop
Releases · lightninglabs/loop
v0.32.1-beta
v0.32.1-beta release
v0.32.0-beta
Highlights
Static Address Open Channel — This release introduces the ability to open Lightning channels directly from static address deposits. Instead of performing a loop-in to get funds into your Lightning node and then opening a channel as separate steps, you can now combine both into a single operation using the new loop openchannel command.
Use Cases
- Consolidate deposits into channels: If you have one or more static address deposits sitting on-chain, you can open a channel to any peer using those funds directly, skipping the
loop-in swap and its associated fees. - Flexible funding: Use the --utxo flag to select specific deposit outpoints, or use --fundmax to sweep all selected UTXOs into a single channel.
- Full channel configuration: The command supports the same options as lncli openchannel — channel type (tweakless, anchors, taproot), private channels, push amounts, fee rates,
zero-conf, and more.
Example
loop openchannel --node_key <peer_pubkey> --local_amt 1000000
loop openchannel --node_key <peer_pubkey> --utxo txid:0 --fundmax
v0.31.8-beta
v0.31.8-beta release
v0.31.7-beta
v0.31.7-beta release
v0.31.5-beta
v0.31.5-beta release
v0.31.4-beta
v0.31.4-beta release
v0.31.2-beta
Breaking Changes
- The content of the
commit_hashfield of theGetInforesponse has been updated so that it contains the Git commit
hash the Loop binary build was based on. If the build had uncommited changes, this field will contain the most recent
commit hash, suffixed by "-dirty". - The
Commitpart of the--versioncommand output has been updated to contain the most recent git commit tag.Add comment
v0.31.1-beta
Breaking Changes
- Autoloop now defaults to a slow publication deadline (30 minutes after
initiation) to reduce fees. To revert to the previous behavior, users can run
loop setparams --fast, which causes swap HTLCs to be published immediately
after initiation.
v0.31.0-beta
New Features
- Enhance the
loop listswapscommand by improving the ability to filter the
response. Use--start_timestamp_nsto return only swaps after
that timestamp. Use--max_swapsto limit total swap outputs.
Paging is enabled using thenext_start_timefield in the response.
v0.30.0-beta
v0.30.0-beta release