📅 Original date posted:2015-12-08
📝 Original message:
On Tue, Dec 8, 2015 at 11:13 AM, Mats Jerratsch wrote:
> However, we have to decide whether we want this whole onion-routing to
> be one-time and one-directional or not.
I have sort of lost track of preferences regarding what is to be sent
through onion routing versus what's not...
Originally I had assumed that some out-of-band messaging would be
taking place (like an equivalent to a BIP70-style payment protocol).
Rather than a single QR code, I was expecting an interactive
wallet-to-wallet protocol while both sides are busy communicating with
the onion routing network for the actual payment route negotiation
stuff. When they ultimately find that no sufficiently cheap route
exists, then the wallets would opt to create a new payment channel in
some circumstances.
Once a path is found, the recipient would then communicate over the
wallet-to-wallet channel to pass over the fully-constructed onion
routing information. Sending that data back over the onion routing
network may not be necessary. Unfortunately this increases the
complexity of the payment side (wallet-to-wallet), but meanwhile makes
for less message passing in onion land, which could make the problem
easier to think about?
- Bryan
http://heybryan.org/
1 512 203 0507