Re: [Lightning-dev] Comments on BOLT#11

HTLC.me is run by Alex Bosworth; I'll ping him. On Fri, Dec 15, 2017 at 6:44 PM, Jonathan Underwood < junderw...@bitcoinbank.co.jp> wrote: > iirc they are using the description as a way to join the user data and the > payment hash on their end. > > htlc me is one node but separates its balance

Re: [Lightning-dev] Comments on BOLT#11

iirc they are using the description as a way to join the user data and the payment hash on their end. htlc me is one node but separates its balance into user accounts that exist outside lightning. I think the identifier is used so when their backend checks the payment request status, the user

Re: [Lightning-dev] Comments on BOLT#11

Jonathan Underwood writes: > Additional comment: we should make a requirement to hide text in the > description under certain conditions. > > ie. "A reader MUST hide information surrounded by curly brackets {} > including > the brackets themselves from the UI, and

Re: [Lightning-dev] Every node must be aware of all other nodes - scalability problem?

Welcome to the mailing list Oliver :-) > It seems to me by reading BOLT #7 that every node in the lightning network > must be aware of every other. That is necessary to choose a complete route > to send a transaction for example. Yes, Bolt 7 is a purposefully simplistic gossiping protocol that

Re: [Lightning-dev] Peer Selection

Hi Cristian, If there is such a great company, BlockStream. and Blockstream runs a fantastic high quality node, then as a user why should I connect to any node other than Blockstream? In this case I dont need to be online all the time and dont need to monitor the blockchain for anything. I will

Re: [Lightning-dev] Peer Selection

Let me add some more color to the discussion. If you do not announce the existence of the channel to the wider network you can still receive incoming payments, by simply telling the payment sender about the channel. This is what is being done in the payment request by adding the `r` parameter to