pull down to refresh

0 sats \ 3 replies \ @openyoureyes 17h \ on: Blinded Paths is a game changer! 🤯 lightning
1)Adoption: not all wallets support it. 2)payment failures: even if your wallet supports it, you have to add route hints in blinded paths that lead to longer pathfinding and more failures. 3)weak privacy: a payment can be unblinded by probing.
write
preview
100 sats \ 2 replies \ @DarthCoin 17h
you have to add route hints in blinded paths
wrong. If you do that, there's no more "blinded" and will always fail. That's why also in Zeus when you activate blinded paths, route hints is automatically switching off. You use one or another.
not all wallets support it.
first is about LN implementations to add it, not wallets. Wallets are just interfaces.
reply
0 sats \ 1 reply \ @Car OP 8h
It works with the people I transact with so idk 🤷‍♂️
Darth do you have a guide on this? Or is it something that is too still early? I didn’t even know it existed before today, kinda shocked Lightning devs are not championing this stuff it’s really freaking cool.
reply
0 sats \ 0 replies \ @DarthCoin 4h
Many LN features are ignored by users. Another example of underrated feature is 0-conf channels (I posted about here) and AMP invouces. Also many still don't know how to use MPP.
What buffels me more is that many still don't know that private channels exist!
I didn't make a guude mentioning blinded paths because is still new and mostly depended on how LN implementations added first to be available in wallets.
I've test it quite a lot, with public and private nodes (I run both), it works nice indeed. The only thing to take in condideration:
  • not all nodes are supporting it, so if you encounter one in the path it could fail.
  • your LN graph must be well synced and updated. So for a private node that is not always online it depends a lot of the graph to find the right path.
  • don't try it with new channels. Use channels that have some history of payments.
reply