Johan,
The issues with mempool limits for OP_SECURETHEBAG are related, but have
distinct solutions.
There are two main categories of mempool issues at stake. One is relay
cost, the other is mempool walking.
In terms of relay cost, if an ancestor can be replaced, it will invalidate
all it's child
On Thu, Oct 24, 2019 at 03:49:09PM +0200, Johan Torås Halseth wrote:
> [...] what about letting the rule be
>
> The last transaction which is added to a package of dependent
> transactions in the mempool must:
> * Have no more than one unconfirmed parent.
> [... subsequent email ...]
> I realize
Hi,
Design reason of trampoline routing was to avoid lite nodes having
to store the whole network graph and compute long-hop route. Trick
lays in getting away from source-base routing, which has the nice
property to hide hop position along the payment route (if we forget
payment hash correleation)
Good morning list,
Of note, is that long ago Rusty proposed already a "local" channel
announcement:
https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-November/001486.html
Briefly, the above proposal goes this way:
> BigBrother: Hi LittleNode!
>
> LittleNode: Hi BigBrother!
>
> Big
