Lightning Interoperability

​

Receiving a Lightning Payment

This provides Alice with true offline receive - she doesn’t need to be online in order to receive the full Lightning payment. Additionally, Alice does not need to run a Lightning node and does not need to open any channels or perform any force closures. All operations here are atomic under the same 1/n or minority/n trust assumptions, as the operators must work together to recreate the preimage.

​

Sending a Lightning Payment

1. Alice receives a Lightning invoice from Bob.
2. Alice makes an API call to the SSP, agreeing to conditionally transfer leaves upon payment completion.
3. SE locks transfers on Alice’s specified leaves until a specified time.
4. SSP makes a Lightning payment to pay Bob’s invoice.
5. SSP provides proof of Lightning payment to the SE.
6. SE finalizes the transfer of Alice’s leaves to the SSP atomically.

Note: If the specified time expires, the SE unlocks usage of Alice’s leaves and control returns to her.