Joseph Hoane [ARCHIVE] on Nostr: đź“… Original date posted:2018-06-20 đź“ť Original message: I root for the Lightening ...
đź“… Original date posted:2018-06-20
đź“ť Original message:
I root for the Lightening Network’s success, but it seems to have an inherent weakness. Since routing tables are not part of the architecture how can the sender chose the next recipient so as to effect an efficient path to the ultimate receiver? With no routing table available the next receiver's connection to the remote ultimate receiver or to the ultimate receiver’s proximate connections is unknown. Even a powerful bridge node will not know an efficient subsequent path and could send the message on in exactly the most inefficient direction. How does choosing an efficient next intermediate receiver not remain a guess, a shot in the dark?Â
I don’t think any solution to the mesh network routing problem has been found. What am I missing here? Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180620/3d0d68dd/attachment.html>;
đź“ť Original message:
I root for the Lightening Network’s success, but it seems to have an inherent weakness. Since routing tables are not part of the architecture how can the sender chose the next recipient so as to effect an efficient path to the ultimate receiver? With no routing table available the next receiver's connection to the remote ultimate receiver or to the ultimate receiver’s proximate connections is unknown. Even a powerful bridge node will not know an efficient subsequent path and could send the message on in exactly the most inefficient direction. How does choosing an efficient next intermediate receiver not remain a guess, a shot in the dark?Â
I don’t think any solution to the mesh network routing problem has been found. What am I missing here? Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180620/3d0d68dd/attachment.html>;