You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the latest splice transaction doesn't confirm, we allow exchanging
`tx_init_rbf` and `tx_ack_rbf` to create another splice transaction to
replace it. We use the same funding contribution as the previous splice.
We disallow creating another splice transaction using `splice_init` if
we have several RBF attempts for the latest splice: we cannot know which
one of them will confirm and should be spent by the new splice.
Disallow chains of unconfirmed splice transactions
When 0-conf isn't used, we reject `splice_init` while the previous
splice transaction hasn't confirmed. Our peer should either use RBF
instead of creating a new splice, or they should wait for our node
to receive the block that confirmed the previous transaction. This
protects against chains of unconfirmed transactions.
Copy file name to clipboardExpand all lines: docs/release-notes/eclair-vnext.md
+34Lines changed: 34 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,39 @@ Every node advertizes the rates at which they sell their liquidity, and buyers c
13
13
The liquidity ads specification is still under review and will likely change.
14
14
This feature isn't meant to be used on mainnet yet and is thus disabled by default.
15
15
16
+
### Channel Splicing
17
+
18
+
With this release, we add support for the final version of [splicing](https://github.com/lightning/bolts/pull/1160) that was recently added to the BOLTs.
19
+
Splicing allows node operators to change the size of their existing channels, which makes it easier and more efficient to allocate liquidity where it is most needed.
20
+
Most node operators can now have a single channel with each of their peer, which costs less on-chain fees and resources, and makes path-finding easier.
21
+
22
+
The size of an existing channel can be increased with the `splicein` API:
If the node operator wants to reduce the size of a channel, or send some of the channel funds to an on-chain address, they can use the `spliceout` API:
That operation can also be RBF-ed with the `rbfsplice` API to speed up confirmation if necessary.
42
+
43
+
Note that when 0-conf is used for the channel, it is not possible to RBF splice transactions.
44
+
Node operators should instead create a new splice transaction (with `splicein` or `spliceout`) to CPFP the previous transaction.
45
+
46
+
Note that eclair had already introduced support for a splicing prototype in v0.9.0, which helped improve the BOLT proposal.
47
+
We're removing support for the previous splicing prototype feature: users that depended on this protocol must upgrade to create official splice transactions.
48
+
16
49
### Update minimal version of Bitcoin Core
17
50
18
51
With this release, eclair requires using Bitcoin Core 27.1.
@@ -38,6 +71,7 @@ Eclair will not allow remote peers to open new obsolete channels that do not sup
38
71
-`channelstats` now takes optional parameters `--count` and `--skip` to control pagination. By default, it will return first 10 entries. (#2890)
39
72
-`createinvoice` now takes an optional `--privateChannelIds` parameter that can be used to add routing hints through private channels. (#2909)
40
73
-`nodes` allows filtering nodes that offer liquidity ads (#2848)
74
+
-`rbfsplice` lets any channel participant RBF the current unconfirmed splice transaction (#2887)
0 commit comments