You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at ILQP and Interledger addresses and ChipNet, it might be a desirable feature to be able to find another node from e.g. a QR code. But in LedgerLoops we would just become neighbours and then let DLD do the work. Also note that the goal is not to find one loop path, but multiple ones can also have the desired effect:
Say Alice buys something in Bob's shop, and scans a QR code to become neighbours using some LedgerLoops-compatible smartphone app. There may be a 5-hop path between Alice and Bob that can be used for the "payment", forming a 6-hop loop for payment + handover. But maybe there is a triangle Alice - Janice - Charlie, another triangle Janice-Charlie-Greg, and another one Greg-John-Bob, and all of these triangles are already known. The composed loops Alice - Janice - Greg - Bob - Alice, Alice - Charlie - Greg - Bob - Alice, Alice - Janice - Greg - John - Bob - Alice, and Alice - Charlie - Greg - John - Bob - Alice can now be composed out of these smaller triangles, and even work together to help Alice pay for the item. Greg will be a bottleneck, but for instance getting money from Alice to Greg, or getting it from Greg to Bob, can happen in two ways.
The text was updated successfully, but these errors were encountered:
Looking at ILQP and Interledger addresses and ChipNet, it might be a desirable feature to be able to find another node from e.g. a QR code. But in LedgerLoops we would just become neighbours and then let DLD do the work. Also note that the goal is not to find one loop path, but multiple ones can also have the desired effect:
Say Alice buys something in Bob's shop, and scans a QR code to become neighbours using some LedgerLoops-compatible smartphone app. There may be a 5-hop path between Alice and Bob that can be used for the "payment", forming a 6-hop loop for payment + handover. But maybe there is a triangle Alice - Janice - Charlie, another triangle Janice-Charlie-Greg, and another one Greg-John-Bob, and all of these triangles are already known. The composed loops Alice - Janice - Greg - Bob - Alice, Alice - Charlie - Greg - Bob - Alice, Alice - Janice - Greg - John - Bob - Alice, and Alice - Charlie - Greg - John - Bob - Alice can now be composed out of these smaller triangles, and even work together to help Alice pay for the item. Greg will be a bottleneck, but for instance getting money from Alice to Greg, or getting it from Greg to Bob, can happen in two ways.
The text was updated successfully, but these errors were encountered: