Skip to content

Commit

Permalink
add section about trampoline payments
Browse files Browse the repository at this point in the history
  • Loading branch information
JssDWt committed Nov 15, 2024
1 parent 205c1a2 commit b18432e
Show file tree
Hide file tree
Showing 2 changed files with 22 additions and 0 deletions.
6 changes: 6 additions & 0 deletions src/guide/lnurl_pay.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,12 @@
</section>
</custom-tabs>

## Trampoline payments

In the above example, the `use_trampoline` flag can be set to `true` to enable
trampoline payments. See
[Trampoline payments](send_payment.md#trampoline-payments) for more details.

## Supported Specs
- [LUD-01](https://github.com/lnurl/luds/blob/luds/01.md) LNURL bech32 encoding
- [LUD-06](https://github.com/lnurl/luds/blob/luds/06.md) `payRequest` spec
Expand Down
16 changes: 16 additions & 0 deletions src/guide/send_payment.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,3 +67,19 @@ Once you have outbound liquidity you can start sending payments too.
```
</section>
</custom-tabs>

## Trampoline payments

In the above example, the `use_trampoline` flag can be set to `true` to enable
trampoline payments. With trampoline, pathfinding through the lightning network
is outsourced to the LSP.

This has several benefits:
- The payment is more reliable and faster as the LSP has a better view of the
network topology and can find good routes faster.
- There is less interaction between the user's app and the user's node in the
cloud, improving payment speed.

The trade-offs are:
- The payment can be more expensive as the LSP will take a fee for its services.
- The payment is less private as the LSP will learn the payment destination.

0 comments on commit b18432e

Please sign in to comment.