> For the complete documentation index, see [llms.txt](https://chaincode.gitbook.io/seminars/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chaincode.gitbook.io/seminars/lightning-protocol-development/future-of-lightning.md).

# The Future of Lightning

## Reading

| Content                                                                                                                                                   | Time (min) |
| --------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
| [Breaking Down the Bitcoin Lightning Network: eltoo](https://medium.com/@brandonarvanaghi/breaking-down-the-bitcoin-lightning-network-eltoo-c48554f5ae02) | 15         |
| [Eltoo by fiatjaf](https://fiatjaf.com/ffdfe772.html)                                                                                                     | 15         |
| (*optional*) [Eltoo and the Far Future](https://btctranscripts.com/chaincode-residency/2019-06-25-christian-decker-eltoo/)                                | 40         |
| (*optional*) [Eltoo whitepaper](https://blockstream.com/eltoo.pdf)                                                                                        | 60         |
| (*optional*) [Onion Messages](https://github.com/lightning/bolts/pull/759)                                                                                | X          |
| [AMP/Offers/LNURL](https://vimeo.com/703262308)                                                                                                           | 30         |
| [Submarine Swaps](https://blog.muun.com/a-closer-look-at-submarine-swaps-in-the-lightning-network/)                                                       | 15         |
| [Splicing](https://btctranscripts.com/chaincode-residency/2019-06-26-rene-pickhardt-splicing/)                                                            | 30         |
| [Splices and Liquidity in the Lightning Network](https://blog.muun.com/splices-and-liquidity-in-the-lightning-network/)                                   | 15         |
| [Dual funded channels](https://btctranscripts.com/c-lightning/dual-funded-channels/) (until min 26)                                                       | 26         |
| [Liquidity Advertisements](https://medium.com/blockstream/lightnings-missing-piece-a-decentralized-liquidity-market-a0bb47534a4f)                         | 15         |
| [Multi-party channels/Channel factories](https://btctranscripts.com/chaincode-residency/2019-06-28-christian-decker-multiparty-channels/)                 | 20         |
| [Payment Points: Replacing HTLCs](https://suredbits.com/payment-points-part-1/)                                                                           | 15         |
| [Payment Points: "Stuckless" Payments](https://suredbits.com/payment-points-part-2-stuckless-payments/)                                                   | 15         |
| [Peer Backups](https://medium.com/@ACINQ/phoenix-wallet-part-3-backup-f63a9470d4e7)                                                                       | 10         |
| [Asynchronous payments](https://gist.github.com/remyers/e0d2bedb7bc87371d1bdbbb6fff2edd1)                                                                 | 10         |
| (optional) [LSPs](https://github.com/BitcoinAndLightningLayerSpecs/lsp)                                                                                   | 10         |
| (optional) [Gossip v2](https://lists.linuxfoundation.org/pipermail/lightning-dev/2022-February/003470.html)                                               | 15         |

## Discussion Questions

### Breaking Down the Bitcoin Lightning Network: eltoo

1. Why do we need SIGHASH\_ANYPREVOUT for eltoo?
2. What do HTLCs look like for an Eltoo channel?

### Eltoo and the Far Future

1. How does a cooperative close work with Eltoo?
2. Can channels using Eltoo or PTLC be mixed with standard channels in a multi-hop payment?
3. Since all update transactions have the same shape, what's stopping earlier update txs from binding to later txs resetting to an old state?
4. Why do settlement txs also need SIGHASH\_ANYPREVOUT?
5. Would there ever be a reason to prefer LN-penalty when creating a channel between two Eltoo-capable nodes?

### Submarine swaps

1. Can an adversary make a swap and then wait until a moment before the lock expiry to reveal the secret on one chain while using the signature on the other? If the blocks are fast, could an attacker be able to steal the money from both chains?

### Splicing

1. Is it easier to splice on an Eltoo channel?

### Multi-party channels/Channel factories

1. What are the advantages and disadvantages of multiparty channels?

### Dual funded channels

1. How do you split the fees in dual-funded channels?

### Payment Points: Replacing HTLCs

1. How does a wormhole attack work?
2. Can sender or receiver notice a wormhole attack?


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://chaincode.gitbook.io/seminars/lightning-protocol-development/future-of-lightning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.