> Each RBF attempt renegotiates a potential liquidity purchase,
independently of what the previous attempts contained.
You're right, I'm missing the RBF spec! Thanks for the reminder.
I think having the lease renegotiated makes sense, it gives
maximum flexibility and allows the API for an
Hi Andy,
> Also, we might want to make it explicit in the spec that you can't
> have duplicate records? Many DNS records allow multiple for
> redundancy. Is that desired here?
Agreed, this should be made explicit in the bLIP. I don't see a reason
to allow duplicate records, so we should require
Hey Lisa,
Thanks for the update! I believe that moving to CLTV instead of CSV is
definitely the right move here.
Regarding the newly added 2nd-stage lease locked transactions, I don't
think that works. The issue is that you don't have an opportunity to
receive signatures for those transactions
Hi Johan,
Few comments.
## Transaction recycling
The transaction recycling attack is made possible by the change made
to HTLC second level transactions for the anchor channel type[8];
making it possible to add fees to the transaction by adding inputs
without violating the signature. For the
