Good morning Greg,
> > I do not know if existing splice implementations actually perform such a
> > check.
> Unless all splice implementations do this, then any kind of batched splicing
> is risky.
> As long as the implementation decides to splice again at some point when a
> prior
> splice
> I do not know if existing splice implementations actually perform such a
check.
Unless all splice implementations do this, then any kind of batched
splicing is risky.
As long as the implementation decides to splice again at some point when a
prior
splice isn't confirming, it will self-resolve on
Good morning Bastien,
I have not gotten around to posting it yet, but I have a write-up in my
computer with the title:
> Batched Splicing Considered Risky
The core of the risk is that if:
* I have no funds right now in a channel (e.g. the LSP allowed me to have 0
reserve, or this is a newly-s
Good morning list,
I've been trying to design a protocol to let users withdraw funds from
exchanges directly into their lightning wallet in an efficient way
(with the smallest on-chain footprint possible).
I've come to the conclusion that this is only possible with some form of
covenants (e.g. `S
