Артём Литвинович [ARCHIVE] on Nostr: 📅 Original date posted:2018-07-29 📝 Original message: Greetings. What was the ...
📅 Original date posted:2018-07-29
📝 Original message:
Greetings.
What was the rationale for not including channel capacity into the
channel_announcement message?
As things stand now, the only way to determine it is to check the
blockchain, which is hard for mobile and/or light wallets.
Even worse, the data is only there in the form of short_channel_id, which
is incompatible with most block explorer APIs.
In other words, having to have access to the blockchain turns a
route-finding tool from a simple program into a thing laden with many
dependencies in order to fetch and parse the transactions.
Not knowing the capacity of the channels drops routing success rates
dramatically, especially for larger payments.
Is there a good reason to force us to do so that i'm missing?
-Artem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180729/dd98d6a7/attachment.html>;
📝 Original message:
Greetings.
What was the rationale for not including channel capacity into the
channel_announcement message?
As things stand now, the only way to determine it is to check the
blockchain, which is hard for mobile and/or light wallets.
Even worse, the data is only there in the form of short_channel_id, which
is incompatible with most block explorer APIs.
In other words, having to have access to the blockchain turns a
route-finding tool from a simple program into a thing laden with many
dependencies in order to fetch and parse the transactions.
Not knowing the capacity of the channels drops routing success rates
dramatically, especially for larger payments.
Is there a good reason to force us to do so that i'm missing?
-Artem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180729/dd98d6a7/attachment.html>;