Christian Decker writes:
> Rusty Russell writes:
>
>> I like it! The lack of "reply" function eliminates all storage
>> requirements for the intermediaries. Unfortunately it's not currently
>> possible to fit the reply onion inside the existing onion, but I know
>> Christian has a rabbit in his
Good morning Christian, and Rusty,
> > > Would it not be better to create a circular path? By this I mean,
> > > Alice constructs an onion that overall creates a path from herself to
> > > Bob and back, ensuring different nodes on the forward and return
> > > directions. The onion hop at Bob revea
Rusty Russell writes:
>> Would it not be better to create a circular path? By this I mean,
>> Alice constructs an onion that overall creates a path from herself to
>> Bob and back, ensuring different nodes on the forward and return
>> directions. The onion hop at Bob reveals that Bob is the cho
Good morning Rusty,
> > Would it not be better to create a circular path?
> > By this I mean, Alice constructs an onion that overall creates a path from
> > herself to Bob and back, ensuring different nodes on the forward and return
> > directions.
> > The onion hop at Bob reveals that Bob is th
René Pickhardt writes:
> Hey Rusty,
>
> I was very delighted to read your proposal. But I don't see how you prevent
> message spam. If I understand you correctly you suggest that I can
> communicate to any node along a path of peer connections (not necessarily
> backed by payment channels but kind
ZmnSCPxj writes:
> Good morning Rusty,
>
> A concern I have brought up in the past is that if this is more than just a
> single request-response, i.e. if this is a conversation where Alice sends to
> Bob, Bob sends back to Alice, Alice sends back to Bob, and so on, then if the
> same path is us
Good morning Rusty,
A concern I have brought up in the past is that if this is more than just a
single request-response, i.e. if this is a conversation where Alice sends to
Bob, Bob sends back to Alice, Alice sends back to Bob, and so on, then if the
same path is used each time Alice sends to B
Hey Rusty,
I was very delighted to read your proposal. But I don't see how you prevent
message spam. If I understand you correctly you suggest that I can
communicate to any node along a path of peer connections (not necessarily
backed by payment channels but kind of only known through channel
anno
Hi all!
It seems that messaging over lightning is A Thing, and I want to
use it for the offers protocol anyway. So I've come up with the
simplest proposal I can, and even implemented it.
Importantly, it's unreliable. Our implementation doesn't
remember across restarts, limits us
