pull down to refresh

The only thing AMP solves is the atomicity of spontaneous payments. Otherwise it's almost exactly like keysend. As another poster mentions, you're incorrect that they can't get stuck.
You're also confusing security with privacy re pubkeys. These resources explain in depth the lack of receiver privacy and what is and can be revealed.
you all are missing out on half of the utility of LN. Streaming payments.
Have you heard of v4v? You don't need AMP for it and it's quite popular.
There is inherently no privacy for a Lightning node and their HTLCs, and all public nodes learn these things in the network gossip, and the protocol requires it. There can be privacy for nodes on either end running private channels - sending side can have privacy initiating over private channels and receiving side can have privacy if - and only if - they isolate their LN node from the place from where the users receive the invoices (this is why many nodes are using Tor I believe). The path hints are only in the deepest layers of the onion and are not visible to the sender, who only sees the first hop out from their position.
In my project, the state of channels will be largely automated, and it must be possible for the sender to initiate payments, and these payments are going to be quite small most of the time so stuck payments will resolve in most cases soon enough to not be a problem.
It is not necessary for these automatically created channels to charge fees, because the payment itself includes a margin on top to compensate the relay operators. Our gateway/seed nodes will charge routing fees as our mechanism for getting a small share of the fees that will go into development/maintenance costs.
I am unfamiliar with v4v, I see many words bandied around on the interwebs and the more I see them and the less clear their meaning the more I am suspicious. I am also sus on nostr, and just this evening learned about the identity of current and past funders of the LND project, which gives me definite pause for thought.
reply
AMP does enable payments where a single path would not be able to carry the payments though. Seems to me like this would go some way to increasing the maximum size of payments that can be carried on the network.
reply
That's true, forgot that keysend doesn't do multiple paths.
reply