One of the fundamental limitations of the Lightning protocol is how payment routing is handled and accomplished. It is entirely source routed, meaning that the sender of a payment is the one who constructs the entire route from themselves to the receiver in order to facilitate the payment. This presents an issue when it comes to the changing balances of channels over time as they are routing payments between numerous different users across the network, once a sender „locks in” and decides on a specific route, that route cannot be changed until a failure message makes it way back to the sender, allowing them to construct an entirely new route going around the point where the initial attempt failed.
This necessitates either dealing with a cumbersome and annoying UX, or the use of payment probing, intentionally crafting payments you will fail on purpose just to see if the route you want to use will work before attempting again with the actual payment. The former is just a bad user experi
We współpracy z: https://bitcoinmagazine.com/technical/payment-splitting-and-switching-improving-privacy-and-payment-success-simultaneously
