Re: [Lightning-dev] General questions about channels

Andy Schroder writes: > I understand that you have to be in agreement with your direct peers. So > you don't really care about what agreements others in your route may > have in place? I would think that you would choose not to route through > hops that violate your

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

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

Re: [Lightning-dev] General question on routing difficulties

Thanks Pedro for the paper, I'll read through it as soon as possible and add more feedback :-) I just have some minor points to add regarding your last mail. > The onion-like packets used for *payments* in the current LN > implementations inevitably assume that the sender knows the complete >

Re: [Lightning-dev] General question on routing difficulties

f interest to lightning. It is hard to > imagine it would be a new idea, although I have not yet found the precedent: > http://ben.mord.io/p/delayed-chained-key-revelation-dckr.html > > Thanks, > Ben > > > On Nov 17, 2017 8:04 AM, "Christian Decker&quo

[Lightning-dev] Integration testing between implementations

I think it's safe to say that the protocol is now in feature freeze for version v1.0 and we are limiting changes to bug fixes and clarifications. In order to locate things that we might have interpreted differently and show how far we are when it comes to interoperability I've been testing the

<    1   2