I responded to a few things in-line before realizing I think we're out of sync
on what this alternative proposal actually implies. In my understanding is it,
it does *not* imply that you are guaranteed the ability to RBF as fees change.
The previous problem is still there - your counterparty can
Matt Corallo writes:
> Ultimately, defining a "near the top of the mempool" criteria is fraught
> with issues. While it's probably OK for the original problem (large
> batched transactions where you don't want a single counterparty to
> prevent confirmation), lightning's requirements are very d
