> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spark.money/llms.txt
> Use this file to discover all available pages before exploring further.

# Lightning Interoperability

<img src="https://mintcdn.com/lightspark/qIS7zQJqaXfAMCl9/images/technical/technical-8.png?fit=max&auto=format&n=qIS7zQJqaXfAMCl9&q=85&s=a285e6e7bc02262843cfb9ff941efad1" alt="Lightning Payment" width="3596" height="3216" data-path="images/technical/technical-8.png" />

<div>
  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.
</div>

### Sending a Lightning Payment

<div>
  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.
</div>

***

### Routing Nodes

If you're a Lightning node operator or LSP looking to establish channels with Spark, connect to our routing nodes:

```
02a98e8c590a1b5602049d6b21d8f4c8861970aa310762f42eae1b2be88372e924@172.30.102.161:9735
039174f846626c6053ba80f5443d0db33da384f1dde135bf7080ba1eec465019c3@172.30.202.34:9735
```

Opening channels to these nodes improves routing reliability for Lightning payments to and from Spark wallets.