onchain is not for payments. Is only for final settlement.
Those who still do not want to comprehend this, will pay a huge price later.

That's why I prefer on-chain Bitcoin, and Satoshi designed.

nym2024

Not really that the number of zaps could get stuck. All depends of the routes is taking those zaps.

Some routing nodes are already using LN firewalls to filter all these useless small zaps.

The whole idea with using hold invoices is kinda of crazy, especially in this scenario with many small zaps, from many users.

SN's wallet plans

k00b

> More zaps only means more stuck HTLC.

Not really that the number of zaps could get stuck. All depends of the routes is taking those zaps.
Some routing nodes are already using LN firewalls to filter all these useless small zaps.
Stuck HTLC could happen mainly because:
- the sender close / go offline his wallet BEFORE the HTLC get "delivered". It could happen even with "stationary" nodes, bad internet, bad syncing, bad fees, bad channels, bad hardware. Are so many causes here.
- on the route the HTLC encounter a bad node or even a LN firewall bad configured.
- bugs in LN implementations that make them incompatible to deliver HTLC in some conditions.

The whole idea with using hold invoices is kinda of crazy, especially in this scenario with many small zaps, from many users.