{"type":"rich","version":"1.0","title":"DarthCoin ₿⚡️ wrote","author_name":"DarthCoin ₿⚡️ (npub1lx…m5xlc)","author_url":"https://yabu.me/npub1lxktpvp5cnq3wl5ctu2x88e30mc0ahh8v47qvzc5dmneqqjrzlkqpm5xlc","provider_name":"njump","provider_url":"https://yabu.me","html":"keysend is not too much about wallet support, but the type of LN node behind it.\nIf your node is a mostly a private node (unannounced channels) it will be almost impossible to be reached by a keysend payment.\nWhy?\nBecause even that you keep it online for a certain time when is about to receive the payment, the other nodes still do not have a 100% updated LN graph to \"know\" in real time about your private node that is online. You will depend of a LSP / public node with which you have a channel, to be connected to the rest of the graph.\n\nBlixt wallet (private node mobile wallet) for example, tried to deal with this issue and was adding the route hints payments into a special QR code for the node. But that QR code can be read only by other Blixt user (for now) and yes you can send keysend payments between 2 private nodes perfectly fine, even that they do not use the same LSP.\n\nZeus also have the option to receive keysend, but still have some issues with the routing hints.\n\nSo the conclusion is that if you want to receive properly keysend, you must have at least 2-3 public channels and always online node. You do not need any other wallet app, simply your LN node is enough."}