Yup. To add to what @DarthCoin said, here's the basic rule around how changes are merged into the common Lightning spec:
Spelling, typo and formatting changes are accepted once two contributors ack and there are no nacks. All other changes get approved and minuted at the spec meeting. Protocol changes require two independent implementations which successfully inter-operate; be patient as spec changes are hard to fix later, so agreement can take some time.[1]
The splicing spec was merged now that discussions are over and there's interrop between Eclair and LDK[2] (and I think also Core Lightning[3]) it has been merged with 2+ ACKs into the main spec.
Just? It’s two years old
Yes, specification work takes time between drafting and reaching interoperability. Merged this morning.
So other implementations now have to adopt this?
I thought eclair already had splicing?
And did you opened a channel with a LND node towards Acinq or any other node with eclair and could make a splicing? No.
Now this spec will make possible the interoperability between LN implementations, is a common language. Next step is LND and others to implement it.
I thought shocknet was against splicing for some reason?
Maybe 'against' is a bit strong!
👀 https://stacker.news/search?q=%40justin_shocknet+%22splicing%22
cc@justin_shocknetcomes up empty for me
That's weird, search for
@justin_shocknet "splicing"That about covers it, over-hyped
Yup. To add to what @DarthCoin said, here's the basic rule around how changes are merged into the common Lightning spec:
The splicing spec was merged now that discussions are over and there's interrop between Eclair and LDK[2] (and I think also Core Lightning[3]) it has been merged with 2+ ACKs into the main spec.
lightning/bolts/CONTRIBUTING.MD ↩
https://github.com/lightning/bolts/pull/1160#issuecomment-4097238314 ↩
https://github.com/lightning/bolts/pull/1160#issuecomment-3769003543 ↩
finally!
LFG