pull down to refresh
26 sats \ 3 replies \ @bellabaxter 29 Apr \ parent \ on: SN's wallet plans meta
Lightning is super cool but very technical and if nobody can/wants to be custodian anymore it gets very difficult, especially for less committed users.
-
For micro-transactions fees can be proportionally high. I'd say up to 10% when sending 10 sats. Never saw more than that though.
-
To prevent this there could be a pooling system, maybe the custodial balance could be maintained to at least 10k sats in order to avoid creating too many transactions and to allow offline nodes to come back online.
-
What a nightmare! This could happen any moment when using lightning, correct? More zaps only means more stuck HTLC.
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.