diff --git a/_compress_images_cache.yml b/_compress_images_cache.yml index 95c3fbee7..a1099166a 100644 --- a/_compress_images_cache.yml +++ b/_compress_images_cache.yml @@ -1405,5 +1405,66 @@ assets/images/projects/projects@2x.jpg: projects@2x.jpg assets/images/search-preview.jpg: search-preview.jpg assets/images/submit-header-design-preview.jpg: submit-header-design-preview.jpg assets/mstile-150x150.png: mstile-150x150.png +assets/images/guide/how-it-works/lightning-services/lightning-services-mobile.jpg: lightning-services-mobile.jpg +assets/images/guide/how-it-works/lightning-services/lightning-services-mobile@2x.jpg: lightning-services-mobile@2x.jpg +assets/images/guide/how-it-works/lightning-services/lightning-services-preview.jpg: lightning-services-preview.jpg +assets/images/guide/how-it-works/lightning-services/lightning-services.jpg: lightning-services.jpg +assets/images/guide/how-it-works/lightning-services/lightning-services@2x.jpg: lightning-services@2x.jpg +assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered-mobile.png: where-is-this-serviced-offered-mobile.png +assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered-mobile@2x.png: where-is-this-serviced-offered-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered.png: where-is-this-serviced-offered.png +assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered@2x.png: where-is-this-serviced-offered@2x.png +assets/images/guide/how-it-works/lightning-services/Collaborative-funding-mobile.png: Collaborative-funding-mobile.png +assets/images/guide/how-it-works/lightning-services/Collaborative-funding-mobile@2x.png: Collaborative-funding-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/Collaborative-funding.png: Collaborative-funding.png +assets/images/guide/how-it-works/lightning-services/Collaborative-funding@2x.png: Collaborative-funding@2x.png +assets/images/guide/how-it-works/lightning-services/How-is-service-offered-mobile.png: How-is-service-offered-mobile.png +assets/images/guide/how-it-works/lightning-services/How-is-service-offered-mobile@2x.png: How-is-service-offered-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/How-is-service-offered.png: How-is-service-offered.png +assets/images/guide/how-it-works/lightning-services/How-is-service-offered@2x.png: How-is-service-offered@2x.png +assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed-mobile.png: Spend-unconfirmed-mobile.png +assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed-mobile@2x.png: Spend-unconfirmed-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed.png: Spend-unconfirmed.png +assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed@2x.png: Spend-unconfirmed@2x.png +assets/images/guide/how-it-works/lightning-services/On-demand-channel-mobile.png: On-demand-channel-mobile.png +assets/images/guide/how-it-works/lightning-services/On-demand-channel-mobile@2x.png: On-demand-channel-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/On-demand-channel.png: On-demand-channel.png +assets/images/guide/how-it-works/lightning-services/On-demand-channel@2x.png: On-demand-channel@2x.png +assets/images/guide/how-it-works/lightning-services/Combining-channel-opens-mobile.png: Combining-channel-opens-mobile.png +assets/images/guide/how-it-works/lightning-services/Combining-channel-opens-mobile@2x.png: Combining-channel-opens-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/Combining-channel-opens.png: Combining-channel-opens.png +assets/images/guide/how-it-works/lightning-services/Combining-channel-opens@2x.png: Combining-channel-opens@2x.png +assets/images/guide/how-it-works/lightning-services/Watchtowers.png: Watchtowers.png +assets/images/guide/how-it-works/lightning-services/Watchtowers@2x.png: Watchtowers@2x.png +assets/images/guide/how-it-works/lightning-services/OnChain-funding-mobile.png: OnChain-funding-mobile.png +assets/images/guide/how-it-works/lightning-services/OnChain-funding-mobile@2x.png: OnChain-funding-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/OnChain-funding.png: OnChain-funding.png +assets/images/guide/how-it-works/lightning-services/OnChain-funding@2x.png: OnChain-funding@2x.png +assets/images/guide/how-it-works/lightning-services/Lightning-address-mobile.png: Lightning-address-mobile.png +assets/images/guide/how-it-works/lightning-services/Lightning-address-mobile@2x.png: Lightning-address-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/Lightning-address.png: Lightning-address.png +assets/images/guide/how-it-works/lightning-services/Lightning-address@2x.png: Lightning-address@2x.png assets/images/guide/daily-spending-wallet/activity/expanded-micropayments.png: expanded-micropayments.png assets/images/guide/daily-spending-wallet/activity/expanded-micropayments@2x.png: expanded-micropayments@2x.png +assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service-mobile.png: Inbound-liquidity-as-a-service-mobile.png +assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service-mobile@2x.png: Inbound-liquidity-as-a-service-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service.png: Inbound-liquidity-as-a-service.png +assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service@2x.png: Inbound-liquidity-as-a-service@2x.png +assets/images/guide/how-it-works/lightning-services/Backups-mobile.png: Backups-mobile.png +assets/images/guide/how-it-works/lightning-services/Backups-mobile@2x.png: Backups-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/Backups.png: Backups.png +assets/images/guide/how-it-works/lightning-services/Backups@2x.png: Backups@2x.png +assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers-mobile.png: what-are-lightning-wallet-servers-mobile.png +assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers-mobile@2x.png: what-are-lightning-wallet-servers-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers.png: what-are-lightning-wallet-servers.png +assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers@2x.png: what-are-lightning-wallet-servers@2x.png +assets/images/guide/how-it-works/lightning-services/Watchtowers-mobile.png: Watchtowers-mobile.png +assets/images/guide/how-it-works/lightning-services/Watchtowers-mobile@2x.png: Watchtowers-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/Submarine-swaps-mobile.png: Submarine-swaps-mobile.png +assets/images/guide/how-it-works/lightning-services/Submarine-swaps-mobile@2x.png: Submarine-swaps-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/Submarine-swaps.png: Submarine-swaps.png +assets/images/guide/how-it-works/lightning-services/Submarine-swaps@2x.png: Submarine-swaps@2x.png +assets/images/guide/how-it-works/lightning-services/Offline-payment-mobile.png: Offline-payment-mobile.png +assets/images/guide/how-it-works/lightning-services/Offline-payment-mobile@2x.png: Offline-payment-mobile@2x.png +assets/images/guide/how-it-works/lightning-services/Offline-payment.png: Offline-payment.png +assets/images/guide/how-it-works/lightning-services/Offline-payment@2x.png: Offline-payment@2x.png diff --git a/assets/images/guide/how-it-works/lightning-service-providers/backups-recovery.jpg b/assets/images/guide/how-it-works/lightning-service-providers/backups-recovery.jpg deleted file mode 100644 index 1a48c815f..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/backups-recovery.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/backups-recovery@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/backups-recovery@2x.jpg deleted file mode 100644 index 83a33f6c4..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/backups-recovery@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/channel-opens.jpg b/assets/images/guide/how-it-works/lightning-service-providers/channel-opens.jpg deleted file mode 100644 index b86eb862f..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/channel-opens.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/channel-opens@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/channel-opens@2x.jpg deleted file mode 100644 index c049f9943..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/channel-opens@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/dual-funding.jpg b/assets/images/guide/how-it-works/lightning-service-providers/dual-funding.jpg deleted file mode 100644 index 5ca5db046..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/dual-funding.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/dual-funding@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/dual-funding@2x.jpg deleted file mode 100644 index a2e1da90c..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/dual-funding@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/inbound-liquidity.jpg b/assets/images/guide/how-it-works/lightning-service-providers/inbound-liquidity.jpg deleted file mode 100644 index ee8be8433..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/inbound-liquidity.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/inbound-liquidity@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/inbound-liquidity@2x.jpg deleted file mode 100644 index 7880cf908..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/inbound-liquidity@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/lightning-address.jpg b/assets/images/guide/how-it-works/lightning-service-providers/lightning-address.jpg deleted file mode 100644 index 51e862068..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/lightning-address.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/lightning-address@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/lightning-address@2x.jpg deleted file mode 100644 index 97b9785ba..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/lightning-address@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-mobile.jpg b/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-mobile.jpg deleted file mode 100644 index 3cec73990..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-mobile.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-mobile@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-mobile@2x.jpg deleted file mode 100644 index 0302d1704..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-mobile@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-preview.jpg b/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-preview.jpg deleted file mode 100644 index 7353fec41..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-preview.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers.jpg b/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers.jpg deleted file mode 100644 index d58b95cf0..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers@2x.jpg deleted file mode 100644 index e56a47c9d..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/payment-forwarding.jpg b/assets/images/guide/how-it-works/lightning-service-providers/payment-forwarding.jpg deleted file mode 100644 index 62ccdfb1d..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/payment-forwarding.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/payment-forwarding@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/payment-forwarding@2x.jpg deleted file mode 100644 index c782921dd..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/payment-forwarding@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/spend-unconfirmed.jpg b/assets/images/guide/how-it-works/lightning-service-providers/spend-unconfirmed.jpg deleted file mode 100644 index c3cd6250d..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/spend-unconfirmed.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/spend-unconfirmed@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/spend-unconfirmed@2x.jpg deleted file mode 100644 index 85523c889..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/spend-unconfirmed@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/swap-in.jpg b/assets/images/guide/how-it-works/lightning-service-providers/swap-in.jpg deleted file mode 100644 index cca6897b9..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/swap-in.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/swap-in@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/swap-in@2x.jpg deleted file mode 100644 index d4419a0ce..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/swap-in@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/swap-out.jpg b/assets/images/guide/how-it-works/lightning-service-providers/swap-out.jpg deleted file mode 100644 index cd3bee2a8..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/swap-out.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/swap-out@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/swap-out@2x.jpg deleted file mode 100644 index d4f0cdbe5..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/swap-out@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/watchtowers.jpg b/assets/images/guide/how-it-works/lightning-service-providers/watchtowers.jpg deleted file mode 100644 index 46480eb93..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/watchtowers.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/watchtowers@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/watchtowers@2x.jpg deleted file mode 100644 index 4b7e9bee9..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/watchtowers@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/zero-reserve.jpg b/assets/images/guide/how-it-works/lightning-service-providers/zero-reserve.jpg deleted file mode 100644 index 9f8aae2e3..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/zero-reserve.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-service-providers/zero-reserve@2x.jpg b/assets/images/guide/how-it-works/lightning-service-providers/zero-reserve@2x.jpg deleted file mode 100644 index dbd264da4..000000000 Binary files a/assets/images/guide/how-it-works/lightning-service-providers/zero-reserve@2x.jpg and /dev/null differ diff --git a/assets/images/guide/how-it-works/lightning-services/Backups-mobile.png b/assets/images/guide/how-it-works/lightning-services/Backups-mobile.png new file mode 100644 index 000000000..3ca46fa35 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Backups-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Backups-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/Backups-mobile@2x.png new file mode 100644 index 000000000..6ff6c8659 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Backups-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Backups.png b/assets/images/guide/how-it-works/lightning-services/Backups.png new file mode 100644 index 000000000..72cfbc4e2 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Backups.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Backups@2x.png b/assets/images/guide/how-it-works/lightning-services/Backups@2x.png new file mode 100644 index 000000000..1d9febcf5 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Backups@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Collaborative-funding-mobile.png b/assets/images/guide/how-it-works/lightning-services/Collaborative-funding-mobile.png new file mode 100644 index 000000000..ce6ef3d29 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Collaborative-funding-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Collaborative-funding-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/Collaborative-funding-mobile@2x.png new file mode 100644 index 000000000..7a14c83a4 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Collaborative-funding-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Collaborative-funding.png b/assets/images/guide/how-it-works/lightning-services/Collaborative-funding.png new file mode 100644 index 000000000..776b173b5 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Collaborative-funding.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Collaborative-funding@2x.png b/assets/images/guide/how-it-works/lightning-services/Collaborative-funding@2x.png new file mode 100644 index 000000000..a1e4cd160 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Collaborative-funding@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens-mobile.png b/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens-mobile.png new file mode 100644 index 000000000..a315494f8 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens-mobile@2x.png new file mode 100644 index 000000000..20161f1f0 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens.png b/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens.png new file mode 100644 index 000000000..20161f1f0 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens@2x.png b/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens@2x.png new file mode 100644 index 000000000..72ede82e5 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/How-is-service-offered-mobile.png b/assets/images/guide/how-it-works/lightning-services/How-is-service-offered-mobile.png new file mode 100644 index 000000000..157ded9d6 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/How-is-service-offered-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/How-is-service-offered-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/How-is-service-offered-mobile@2x.png new file mode 100644 index 000000000..99f1b6c9d Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/How-is-service-offered-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/How-is-service-offered.png b/assets/images/guide/how-it-works/lightning-services/How-is-service-offered.png new file mode 100644 index 000000000..5fad03bea Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/How-is-service-offered.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/How-is-service-offered@2x.png b/assets/images/guide/how-it-works/lightning-services/How-is-service-offered@2x.png new file mode 100644 index 000000000..db0f52465 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/How-is-service-offered@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service-mobile.png b/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service-mobile.png new file mode 100644 index 000000000..fcaa89cc0 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service-mobile@2x.png new file mode 100644 index 000000000..76d215dde Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service.png b/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service.png new file mode 100644 index 000000000..f31ab1dbb Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service@2x.png b/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service@2x.png new file mode 100644 index 000000000..102627b81 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Lightning-address-mobile.png b/assets/images/guide/how-it-works/lightning-services/Lightning-address-mobile.png new file mode 100644 index 000000000..096461e91 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Lightning-address-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Lightning-address-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/Lightning-address-mobile@2x.png new file mode 100644 index 000000000..d66d277cd Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Lightning-address-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Lightning-address.png b/assets/images/guide/how-it-works/lightning-services/Lightning-address.png new file mode 100644 index 000000000..d66d277cd Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Lightning-address.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Lightning-address@2x.png b/assets/images/guide/how-it-works/lightning-services/Lightning-address@2x.png new file mode 100644 index 000000000..6eee4f7d9 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Lightning-address@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Offline-payment-mobile.png b/assets/images/guide/how-it-works/lightning-services/Offline-payment-mobile.png new file mode 100644 index 000000000..792b2eb4b Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Offline-payment-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Offline-payment-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/Offline-payment-mobile@2x.png new file mode 100644 index 000000000..4d276fa40 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Offline-payment-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Offline-payment.png b/assets/images/guide/how-it-works/lightning-services/Offline-payment.png new file mode 100644 index 000000000..f9c6b03ff Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Offline-payment.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Offline-payment@2x.png b/assets/images/guide/how-it-works/lightning-services/Offline-payment@2x.png new file mode 100644 index 000000000..ffc9ee46d Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Offline-payment@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/On-demand-channel-mobile.png b/assets/images/guide/how-it-works/lightning-services/On-demand-channel-mobile.png new file mode 100644 index 000000000..145174bbc Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/On-demand-channel-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/On-demand-channel-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/On-demand-channel-mobile@2x.png new file mode 100644 index 000000000..829fed820 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/On-demand-channel-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/On-demand-channel.png b/assets/images/guide/how-it-works/lightning-services/On-demand-channel.png new file mode 100644 index 000000000..829fed820 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/On-demand-channel.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/On-demand-channel@2x.png b/assets/images/guide/how-it-works/lightning-services/On-demand-channel@2x.png new file mode 100644 index 000000000..a9d8dc1cf Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/On-demand-channel@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/OnChain-funding-mobile.png b/assets/images/guide/how-it-works/lightning-services/OnChain-funding-mobile.png new file mode 100644 index 000000000..df7d161bd Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/OnChain-funding-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/OnChain-funding-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/OnChain-funding-mobile@2x.png new file mode 100644 index 000000000..c131ebc97 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/OnChain-funding-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/OnChain-funding.png b/assets/images/guide/how-it-works/lightning-services/OnChain-funding.png new file mode 100644 index 000000000..c131ebc97 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/OnChain-funding.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/OnChain-funding@2x.png b/assets/images/guide/how-it-works/lightning-services/OnChain-funding@2x.png new file mode 100644 index 000000000..0bdb2805d Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/OnChain-funding@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed-mobile.png b/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed-mobile.png new file mode 100644 index 000000000..b54dcd687 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed-mobile@2x.png new file mode 100644 index 000000000..81b3877dd Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed.png b/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed.png new file mode 100644 index 000000000..df3af4234 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed@2x.png b/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed@2x.png new file mode 100644 index 000000000..9d26d4a5f Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Submarine-swaps-mobile.png b/assets/images/guide/how-it-works/lightning-services/Submarine-swaps-mobile.png new file mode 100644 index 000000000..79eea157c Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Submarine-swaps-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Submarine-swaps-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/Submarine-swaps-mobile@2x.png new file mode 100644 index 000000000..8f650cc30 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Submarine-swaps-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Submarine-swaps.png b/assets/images/guide/how-it-works/lightning-services/Submarine-swaps.png new file mode 100644 index 000000000..6b0e11cdf Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Submarine-swaps.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Submarine-swaps@2x.png b/assets/images/guide/how-it-works/lightning-services/Submarine-swaps@2x.png new file mode 100644 index 000000000..8c7ce46a1 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Submarine-swaps@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Watchtowers-mobile.png b/assets/images/guide/how-it-works/lightning-services/Watchtowers-mobile.png new file mode 100644 index 000000000..f4aad8322 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Watchtowers-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Watchtowers-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/Watchtowers-mobile@2x.png new file mode 100644 index 000000000..c370f7750 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Watchtowers-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Watchtowers.png b/assets/images/guide/how-it-works/lightning-services/Watchtowers.png new file mode 100644 index 000000000..3e11b56b2 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Watchtowers.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/Watchtowers@2x.png b/assets/images/guide/how-it-works/lightning-services/Watchtowers@2x.png new file mode 100644 index 000000000..32989dc63 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/Watchtowers@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/lightning-services-mobile.jpg b/assets/images/guide/how-it-works/lightning-services/lightning-services-mobile.jpg new file mode 100644 index 000000000..52e341c70 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/lightning-services-mobile.jpg differ diff --git a/assets/images/guide/how-it-works/lightning-services/lightning-services-mobile@2x.jpg b/assets/images/guide/how-it-works/lightning-services/lightning-services-mobile@2x.jpg new file mode 100644 index 000000000..d54c86648 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/lightning-services-mobile@2x.jpg differ diff --git a/assets/images/guide/how-it-works/lightning-services/lightning-services-preview.jpg b/assets/images/guide/how-it-works/lightning-services/lightning-services-preview.jpg new file mode 100644 index 000000000..8e4611c61 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/lightning-services-preview.jpg differ diff --git a/assets/images/guide/how-it-works/lightning-services/lightning-services.jpg b/assets/images/guide/how-it-works/lightning-services/lightning-services.jpg new file mode 100644 index 000000000..344b71768 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/lightning-services.jpg differ diff --git a/assets/images/guide/how-it-works/lightning-services/lightning-services@2x.jpg b/assets/images/guide/how-it-works/lightning-services/lightning-services@2x.jpg new file mode 100644 index 000000000..d60311c0f Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/lightning-services@2x.jpg differ diff --git a/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers-mobile.png b/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers-mobile.png new file mode 100644 index 000000000..fa8f4475b Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers-mobile@2x.png new file mode 100644 index 000000000..171f48447 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers.png b/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers.png new file mode 100644 index 000000000..2858ff9e1 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers@2x.png b/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers@2x.png new file mode 100644 index 000000000..417f424ff Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered-mobile.png b/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered-mobile.png new file mode 100644 index 000000000..bb86e4e7c Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered-mobile.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered-mobile@2x.png b/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered-mobile@2x.png new file mode 100644 index 000000000..82cffe67f Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered.png b/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered.png new file mode 100644 index 000000000..eac37d7ad Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered.png differ diff --git a/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered@2x.png b/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered@2x.png new file mode 100644 index 000000000..a15767d72 Binary files /dev/null and b/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered@2x.png differ diff --git a/guide/how-it-works/introduction.md b/guide/how-it-works/introduction.md index 3fe7f14b6..1bb5b6e90 100644 --- a/guide/how-it-works/introduction.md +++ b/guide/how-it-works/introduction.md @@ -38,7 +38,7 @@ A primer on liquidity in the lightning network. --- -### [Lightning service providers]({{ '/guide/how-it-works/lightning-service-providers/' | relative_url }}) +### [Lightning services]({{ '/guide/how-it-works/lightning-services/' | relative_url }}) Common user experience problems of the Lightning network that can be resolved by third-party service providers. diff --git a/guide/how-it-works/lightning-service-providers.md b/guide/how-it-works/lightning-service-providers.md deleted file mode 100644 index a3ddff9c6..000000000 --- a/guide/how-it-works/lightning-service-providers.md +++ /dev/null @@ -1,318 +0,0 @@ ---- -layout: guide -title: Lightning Service Providers -description: Common user experience problems of the lightning network that can be resolved by third-party services. -nav_order: 4 -parent: How it works -permalink: /guide/how-it-works/lightning-service-providers/ -main_classes: -no-top-padding ---- - - - -{% include picture.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers@2x.jpg" - mobile = "/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-mobile.jpg" - mobileRetina = "/assets/images/guide/how-it-works/lightning-service-providers/lightning-service-providers-mobile@2x.jpg" - alt-text = "Lightning service providers header image." - width = 1600 - height = 740 - layout = "full-width" -%} - -# Lightning Service Providers - -The [lightning network]({{ '/guide/getting-started/technology-primer/#the-lightning-payment-network' | relative_url }}) is currently bitcoins best solution at [scaling]({{ '/guide/getting-started/technology-primer/#do-all-transactions-have-to-be-this-secure' | relative_url }}) to billions of people. However, using the lightning network self-custodially brings about many new usability issues, such as channel management, routing, uptime requirements and backups. - -Lightning service providers (LSPs) solve these user friction points by providing services that make it easy to access and use the lightning network. They act as trust-minimized third parties that make it easy to onboard new users into lightning. - -Roy Sheinfeld from [Breez](https://breez.technology/) explains LSPs in more depth in his [introducing lightning service providers](https://medium.com/breez-technology/introducing-lightning-service-providers-fe9fb1665d5f) and [envisioning LSPs in the lightning economy](https://medium.com/breez-technology/envisioning-lsps-in-the-lightning-economy-832b45871992) articles. - -## What is a lightning service? - -Lightning services are trust-minimized offerings by LSPs that solve user pain points when using a non-custodial bitcoin lightning wallet. - -A lightning service should always be non-custodial and opt-out, with trade-offs clearly communicated to users. - -Below are some lightning services, the pain points they solve, their trade-offs, and the applications that use them. - -## Backup & recovery - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/backups-recovery.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/backups-recovery@2x.jpg" - alt-text = "Backups & recovery LSP service image." - width = 400 - height = 300 - layout = "float-right-desktop" -%} - -A Lightning wallet requires both a [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) and up-to-date payment channel states to be recovered. Payment channel states need to be [backed up]({{ '/guide/daily-spending-wallet/backup-and-recovery/landing-page/' | relative_url }}) each time a payment is received or sent. Users can make these backups, though if done incorrectly or stored insecurely, users are at risk of losing their bitcoin. - -A backup & recovery service automatically backs up and stores a user’s channel states with the LSP when a lightning payment is sent or received. These backups are encrypted, usually by the user’s recovery phrase, before being sent to the LSP. - -When a user recovers their wallet, they enter their recovery phrase, the LSP sends them the encrypted channel states, these are decrypted by the user, and the wallet is restored. - -This service requires trust that the LSP accurately and securely stores the users channel state backups. Entrusting backups with a single third-party like this is also a security risk and makes users reliant on the LSP. - -As the users recovery phrase is required to recover the channel states stored by the LSP, this makes the recovery phrase wallet-dependent. Users will be unable to recover their bitcoin in a wallet that was not the one who generated it, making things less [interoperable]({{ '/guide/designing-products/interoperability/' | relative_url }}). - -Users should have the option to backup payment channel states [manually]({{ '/guide/daily-spending-wallet/backup-and-recovery/manual-backup/' | relative_url }}) or [automatically]({{ '/guide/daily-spending-wallet/backup-and-recovery/cloud-backup/' | relative_url }}). - -[ACINQ](https://medium.com/@ACINQ/phoenix-wallet-part-3-backup-f63a9470d4e7) is an example of a LSP using a backup and recovery service for its wallet Phoenix. [Backpack](https://github.com/synonymdev/backpack-client) is an open-source client enabling this service. - -
- -## Channel opens - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/channel-opens.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/channel-opens@2x.jpg" - alt-text = "Image showing lightning channels represented like an abacus.." - width = 400 - height = 300 - layout = "float-right-desktop" -%} - -To use a lightning wallet, users first need a [payment channel]({{ '/guide/getting-started/technology-primer/#what-is-a-payment-channel' | relative_url }}). Manually opening a payment channel involves finding a suitable peer, having on-chain bitcoin in your wallet to put in the channel, and broadcasting a transaction. Once this channel is opened, it needs to be managed. - -All of this can be complex for users to deal with. A channel opening service automatically opens a channel to the LSP for the user when necessary. - -Users should always have the option to manually open channels, as to not completely rely on a LSP. Any trade-offs involved with using a channel open service should be clearly communicated to users in the UI. - -Below, we cover the different ways in which a channel open service can be offered, depending on user needs and the trade-offs they are willing to make. These channel open types can be offered together, and in fact, in some cases work better when offered together. - -
- -### Inbound liquidity - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/inbound-liquidity.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/inbound-liquidity@2x.jpg" - alt-text = "Drop of water representing liquidity." - width = 140 - height = 140 - layout = "float-right" -%} - -Lightning wallets can not receive payments without inbound liquidity in a channel. This is primarily the case with new wallets, but may also occur when channels are imbalanced on funded wallets. - -Offering inbound liquidity with a channel open service addresses this situation. When a user receives a payment without enough inbound liquidity, a new channel is automatically opened containing inbound liquidity. The network fee, and sometimes an additional service fee, for opening the channel is typically deducted from the payment amount. - -A channel open with inbound liquidity allows users to fund their wallets with a lightning payment, or combined with a [swap-in]({{ '/guide/how-it-works/lightning-service-providers/#swap-in' | relative_url }}) or [dual funding]({{ '/guide/how-it-works/lightning-service-providers/#dual-funding' | relative_url }}) service can allow funding with an on-chain payment. - -[Dunder](https://github.com/hsjoberg/dunder-lsp) is an open-source LSP client that helps applications offer inbound liquidity to users. - -[Liquidity ads](https://medium.com/blockstream/setting-up-liquidity-ads-in-c-lightning-54e4c59c091d) are a protocol-level way for anyone to act as an LSP and advertise their willingness to offer inbound liquidity to other users. - -
- -### Dual-funding - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/dual-funding.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/dual-funding@2x.jpg" - alt-text = "Blocks representing unconfirmed spend." - width = 140 - height = 140 - layout = "float-right" -%} - -Using a channel open service requires a LSP to open a channel for the user on their behalf, which requires trust. An LSP could refuse to open a channel for a user, or require invasive privacy practices, leading to application-level censorship. - -A [dual-funding](https://bitcoinops.org/en/topics/dual-funding/) channel open service solves this issue of trust by having users cooperatively open a channel with the LSP. Users get the benefits of having both inbound and outbound liquidity without having to trust the LSP. - -Dual funding is only applicable when funding a wallet with on-chain bitcoin. The issue of trusting the LSP to open the channel for the user still exists when funding with a lightning payment. - -
- -### Spend-unconfirmed - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/spend-unconfirmed.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/spend-unconfirmed@2x.jpg" - alt-text = "Blocks representing unconfirmed spend." - width = 140 - height = 140 - layout = "float-right" -%} - -The bitcoin in a payment channel can not be spent until the on-chain transaction that opened the channel is confirmed. If a [mempool]({{ '/guide/glossary/#mempool' | relative_url }}) is congested, this could take a long time. - -A channel open service using spend-unconfirmed, sometimes called turbo channels or zero-confirmation channels, allows users to spend their bitcoin instantly without having to wait for the channel transaction to confirm. - -A spend-unconfirmed channel is trusted until the transaction is confirmed. Users should have the option to disable these types of channel opens if they are being used. Some LSPs may batch their channel opens, meaning a user's channel will be trusted until that batch process is complete. - -[Breez](https://breez.technology/) is a bitcoin wallet that provides this service. - -
- -### Swap-in - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/swap-in.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/swap-in@2x.jpg" - alt-text = "Swap into lightning." - width = 140 - height = 140 - layout = "float-right" -%} - -Funding a lightning wallet typically consists of two steps. First, the user needs to deposit on-chain funds. Second, a lightning channel needs to be opened. This adds a lot of friction, particularly for new users. - -A swap-in channel open service solves this by allowing users to fund a lightning wallet with an on-chain payment. The user sends their on-chain bitcoin to the LSP who opens a channel for the user. - -Swap-ins should be done in a trust-minimized, non-custodial way using a [submarine swap](https://blog.muun.com/a-closer-look-at-submarine-swaps-in-the-lightning-network/). A [dual-funded]({{ '/guide/how-it-works/lightning-service-providers/#dual-funding' | relative_url }}) channel open requires less trust and equally solves this issue. - -The client [Loop](https://lightning.engineering/loop/) and the non-custodial lightning wallet [Phoenix](https://phoenix.acinq.co/) both offer a swap-in service. - -
- -### Zero-reserve - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/zero-reserve.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/zero-reserve@2x.jpg" - alt-text = "Empty glass representing no channel reserve." - width = 140 - height = 140 - layout = "float-right" -%} - -Payment channels require a channel reserve to be set aside to prevent theft. When a user opens a channel, they will not be able to spend this reserve. This can confuse new users who are likely not familiar with this. - -A zero-reserve channel open service solves this issue by allowing channels opened by the LSP to not have a zero-reserve on the users side. The LSP still has a reserve as it is connected to the wider network. This also prevents them from attempting to steal the user's bitcoin. - -This service has an asymmetric trust model as it is more in favour of the user, who has nothing at stake if attempting to cheat the LSP. This can be useful when combined with other services, as it balances the trust between the user and LSP. - -[Phoenix](https://phoenix.acinq.co/) is a non-custodial lighting wallet offering this service. - -
- -## Lightning address - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/lightning-address.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/lightning-address@2x.jpg" - alt-text = "Lightning address LSP service." - width = 400 - height = 300 - layout = "float-right-desktop" -%} - -Lightning [payment requests]({{ '/guide/payments/request/payment-request-formats/' | relative_url }}) are not very human-readable and are mostly [single-use]({{ '/guide/daily-spending-wallet/requesting/#single-use-payment-requests' | relative_url }}). Sharing an invoice for every payment adds a lot of friction when sending and requesting payments. - -A [Lightning address](https://lightningaddress.com/) service gives users a reusable, human-readable way to receive lightning payments, such as bosch@bitcoin.design. - -Lightning addresses require a non-custodial, trusted third-party server run by a LSP to forward payment requests. This opens up the possibility that the LSP could censor user payments on the application layer by not relaying them between the parties. - -Lightning addresses build on top of the [LNURL](https://github.com/fiatjaf/lnurl-rfc) standard, which is another way to create reusable payment requests. - -
- -## Payment forwarding - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/payment-forwarding.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/payment-forwarding@2x.jpg" - alt-text = "Payment forwarding LSP service image." - width = 400 - height = 300 - layout = "float-right-desktop" -%} - -Lightning payments require a route through the network to be calculated for sending, and a user must be online for receiving. Mobile nodes, especially ones running on lower-end devices, may have difficulties calculating a route, resulting in higher network fees. They are also regularly offline, meaning a user will have to be online to receive a payment. - -A payment forwarding service solves these issues by acting as a non-custodial intermediary for payments. The route calculation for sending bitcoin can be conducted by the LSP on behalf of the user. - -For receiving, if the user is offline, the LSP can hold the payment and forward it once the user comes back online. - -[Trampoline payments](https://bitcoinops.org/en/topics/trampoline-payments/) remove the need for a single third-party node to calculate a payment route for a user. However, these are currently not widely supported. - -[Phoenix](https://phoenix.acinq.co/) is a non-custodial lighting wallet offering this service. - -
- -## Swap-out - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/swap-out.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/swap-out@2x.jpg" - alt-text = "Swapping out of the lightning network." - width = 400 - height = 300 - layout = "float-right-desktop" -%} - -Making a payment directly from lightning to on-chain is not possible. A user may want to move funds from their lightning channel to on-chain for more secure storage. - -A swap-out service allows users to send bitcoin from lightning to on-chain. Users send their lightning bitcoin to the LSP. They then make the on-chain payment on the user's behalf. - -This also has added privacy benefits as the user is receiving one of the LSPs UTXOs and not the ones in their channel. - -Swap-outs should be done in a non-custodial, trust-minimized way using [Submarine swaps](https://blog.muun.com/a-closer-look-at-submarine-swaps-in-the-lightning-network/). - -[Lightning Labs](https://lightning.engineering/loop/) is an example of an LSP using a submarine swap-out service called loop. - -
- -## Watchtowers - -
- -{% include image.html - image = "/assets/images/guide/how-it-works/lightning-service-providers/watchtowers.jpg" - retina = "/assets/images/guide/how-it-works/lightning-service-providers/watchtowers@2x.jpg" - alt-text = "Watchtower LSP service image." - width = 400 - height = 300 - layout = "float-right-desktop" -%} - -Lightning nodes need to stay online in order to monitor for potential cheating attempts from their counterparties. Mobile nodes in particular are regularly offline, meaning their channel counterparties could potentially cheat them and steal their bitcoin. - -A [watchtower](https://bitcoinops.org/en/topics/watchtowers/) service prevents this by monitoring the user's node for cheating attempts. If one is detected, a watchtower broadcasts a justice transaction which gives the cheating parties bitcoin to the honest user. Watchtowers sometimes take a small fee for offering this service. - -When using a watchtower and a LSP for [opening channels]({{ '/guide/how-it-works/lightning-service-providers/#channel-opens' | relative_url }}), it's important a watchtower is not that same LSP. This is because LSP is the users counterparty, so having a watchtower with them would not safeguard their bitcoin. - -The [lightningnetwork+ watchtower](https://lightningnetwork.plus/watchtower) is an example of an LSP offering a watchtower client that users can use. - -
- ---- - -Now, lets learn how [nodes]({{ '/guide/how-it-works/nodes/' | relative_url }}) on bitcoin work. - -{% include next-previous.html - previousUrl = "/guide/how-it-works/liquidity/" - previousName = "Liquidity" - nextUrl = "/guide/how-it-works/nodes/" - nextName = "Nodes" -%} diff --git a/guide/how-it-works/lightning-services.md b/guide/how-it-works/lightning-services.md new file mode 100644 index 000000000..b3ce10819 --- /dev/null +++ b/guide/how-it-works/lightning-services.md @@ -0,0 +1,326 @@ +--- +layout: guide +title: Lightning Services +description: Third party services that solve common user experience problems when connecting to and using the lightning network. +nav_order: 4 +parent: How it works +permalink: /guide/how-it-works/lightning-services/ +redirect_from: + - /guide/payments/send/lightning-service-providers/ +main_classes: -no-top-padding +image: https://bitcoin.design/assets/images/guide/how-it-works/lightning-services/lightning-services-preview.jpg +--- + + + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/lightning-services.jpg" + retina = "/assets/images/guide/how-it-works/lightning-services/lightning-services@2x.jpg" + mobile = "/assets/images/guide/how-it-works/lightning-services/lightning-services-mobile.jpg" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/lightning-services-mobile@2x.jpg" + alt-text = "Lightning service providers header image." + caption = "Image by [Rahul Viswanath](https://unsplash.com/@rahul_viswanath) from Unsplash" + width = 1600 + height = 740 + layout = "full-width" +%} + +# Lightning services + +[Scaling]({{ '/guide/getting-started/technology-primer/#do-all-transactions-have-to-be-this-secure' | relative_url }}) bitcoin to billions of self-custodial users with the lightning network creates many new usability issues. +Some of those issues include: +- liquidity and uptime requirements +- channel management +- routing +- complex backups + +Lightning services offered by third-parties aim to solve these issues. + +This section covers two categories of lightning services: Lightning service providers (LSPs), which focus on onboarding and providing connectivity to lightning users, and [lightning wallet servers]({{ '/guide/how-it-works/lightning-services/#what-are-lightning-wallet-servers' | relative_url }}), which provide additional services not relating to connectivity. + +## What is a Lightning service provider? + +Internet service providers (ISPs) help users connect to the internet. Similarly, Lightning service providers (LSPs) help users connect to the lightning network while maintaining [self-custody]({{ '/guide/getting-started/principles/#self-custody' | relative_url }}). + +They do this by being well connected in the network, opening channels, and offering inbound liquidity to users. They often charge a fee for their services. + +You can learn more about how liquidity works on our [liquidity]({{ '/guide/how-it-works/liquidity/' | relative_url }}) page. + +Some LSPs may also offer channel management, routing, backups, and [other services]({{ '/guide/how-it-works/lightning-services/#what-are-lightning-wallet-servers' | relative_url }}), but these are not limited to being offered by LSPs. + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service.png" + retina = "/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/Inbound-liquidity-as-a-service-mobile@2x.png" + alt-text = "How LSPs offer liquidity as a service" + width = 800 + height = 348 +%} + +## How do LSPs connect users to lightning? + +To use lightning, a self-custodial user needs at least one [payment channel]({{ '/guide/getting-started/technology-primer/#what-is-a-payment-channel' | relative_url }}). To send payments, this channel needs outbound liquidity, which the user usually provides. And to receive payments, this channel needs inbound liquidity, which needs to be provided by someone else. + +Finding someone offering inbound liquidity and opening a channel with them can be difficult, especially for new users. LSPs provide inbound liquidity and open channels for users. + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/How-is-service-offered.png" + retina = "/assets/images/guide/how-it-works/lightning-services/How-is-service-offered@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/How-is-service-offered-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/How-is-service-offered-mobile@2x.png" + alt-text = "How LSPs offer inbound liquidity as a service to users" + width = 800 + height = 348 +%} + +LSPs can alter how they open channels to achieve unique user experiences. These can come with additional trust or privacy trade-offs, so users should be made aware of these and be able to opt out if used. + +Below we dive into the different ways an LSP can open a channel and the unique user experiences they can offer. + +### Collaborative fund + +Channels are usually only funded on one side, meaning that initially, one party won't be able to send, and the other won't be able to receive. + +A [collaborative fund](https://bitcoinops.org/en/topics/dual-funding), previously called dual funding, allows both parties to contribute bitcoin to the channel. This means both parties can send and receive once the channel is open. + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/Collaborative-funding.png" + retina = "/assets/images/guide/how-it-works/lightning-services/Collaborative-funding@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/Collaborative-funding-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/Collaborative-funding-mobile@2x.png" + alt-text = "How a collaborative fund of a lightning payment channel is opened by an LSP" + width = 800 + height = 348 +%} + +### On-demand liquidity + +If a user tries to receive a payment without enough inbound liquidity, the payment will fail. + +In these situations, an LSP can fix this with on-demand liquidity. They open a new channel with the user, giving the user enough inbound liquidity to receive the payment. + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/On-demand-channel.png" + retina = "/assets/images/guide/how-it-works/lightning-services/On-demand-channel@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/On-demand-channel-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/On-demand-channel-mobile@2x.png" + alt-text = "How an LSP opens a channel with inbound liquidity on-demand for users" + width = 800 + height = 348 +%} + +### On-chain funding + +A user may only have on-chain bitcoin to fund their lightning wallet with. An LSP can allow users to open a channel using an on-chain payment with a [swap]({{ '/guide/how-it-works/lightning-services/#swaps' | relative_url }}). + +LSPs will need to provide enough inbound liquidity to forward the payment to the user. They often provide more than the forwarded payment amount so the user can receive additional payments with the channel. + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/OnChain-funding.png" + retina = "/assets/images/guide/how-it-works/lightning-services/OnChain-funding@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/OnChain-funding-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/OnChain-funding-mobile@2x.png" + alt-text = "An LSP conducting a swap that opens a new payment channel to a user" + width = 800 + height = 348 +%} + +### Zero-confirmation + +Opening a payment channel first requires an on-chain transaction to be confirmed, which leaves users having to wait to spend the bitcoin in their channel. + +A zero-confirmation channel allows users to use the channel without it being confirmed on chain. This makes it faster to onboard users, though comes with trust that the LSP will not cancel the transaction after payments are made. + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed.png" + retina = "/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/Spend-unconfirmed-mobile@2x.png" + alt-text = "How a zero-confirmation channel is created with an LSP" + width = 800 + height = 348 +%} + +### Combining techniques + +Channel open techniques can be combined in various ways for even more unique user experiences. + +An example is combining a collaborative fund with a zero-confirmation channel open. This ensures that both users can send and receive instantly rather than wait for the new channel to be confirmed. + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens.png" + retina = "/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/Combining-channel-opens-mobile@2x.png" + alt-text = "Combining a collaborative fund and zero-confirmation channel open technique" + width = 800 + height = 348 +%} + +## Where do LSPs offer this service? + +LSPs makes it easy for users to connect to and use lightning by offering inbound liquidity . There are various ways LSPs offer this service which range in complexity. + +- Built-in to wallets like [Breez](https://breez.technology/) +- Web portals like [Blocktank](https://synonym.to/blocktank/) +- P2P marketplaces like [Magma](https://amboss.space/magma) +- Protocol level methods like [liquidity advertisements](https://bitcoinops.org/en/topics/liquidity-advertisements/) + +{% include tip/open.html color="blue" icon="info" label="Avoid LSP lock-in" %} + +If your application uses an LSP, ensure users can switch, opt-out, or use multiple LSPs. This ensures they can choose the LSPs that have trade-offs they are comfortable with. + +It also prevents everyone from using the same LSP, improving [decentralization]({{ '/guide/getting-started/principles/#decentralization' | relative_url }}). + +{% include tip/close.html %} + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered.png" + retina = "/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/where-is-this-serviced-offered-mobile@2x.png" + alt-text = "Where LSP services are offered" + width = 800 + height = 348 +%} + +## What are Lightning wallet servers? + +Once a user is connected to the lightning network, likely through an LSP, lightning wallet servers (LWS) offer services that make using lightning easier for users. LSPs sometimes offer LWS services as part of their offering but this is not exclusive to LSPs. + +LWSs act as trust-minimized third parties, so when possible, users should be able to opt out and operate their lightning wallet manually. + +Below are some LWS services and the user friction points they solve. + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers.png" + retina = "/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/what-are-lightning-wallet-servers-mobile@2x.png" + alt-text = "What is a lightning wallet server (LWS)?" + width = 800 + height = 348 +%} + +### Backups + +[Backing up]({{ '/guide/daily-spending-wallet/backup-and-recovery/landing-page/' | relative_url }}) a lightning wallet requires a [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) and up-to-date payment channel states. + +Payment channel states need to be backed up each time a payment is received or sent. Users can make these backups, though if done incorrectly or stored insecurely, users are at risk of losing their bitcoin. + +An LWS backup service can automatically back up and store a user's channel states whenever they are updated. Giving the user the option to encrypt their backup prevents the LWS from stealing funds. + +{% include tip/open.html color="blue" icon="info" label="Non-freezability" %} + +Backing up your lightning wallet with a single LWS breaks non-freezability, meaning they can refuse to hand over your channel states when recovering. + +To prevent this, ensure your users can [manually backup their channel]({{ '//guide/daily-spending-wallet/backup-and-recovery/manual-backup/' | relative_url }}) states or use multiple LWSs for backups. + +{% include tip/close.html %} + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/Backups.png" + retina = "/assets/images/guide/how-it-works/lightning-services/Backups@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/Backups-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/Backups-mobile@2x.png" + alt-text = "How a LWS backups a users channel state as they change" + width = 800 + height = 348 +%} + +### Lightning address + +Lightning [payment requests]({{ '/guide/payments/request/payment-request-formats/' | relative_url }}) are not very human-readable and are mostly [single-use]({{ '/guide/daily-spending-wallet/requesting/#single-use-payment-requests' | relative_url }}). + +A [Lightning address](https://lightningaddress.com/) LWS service gives users a human-readable address that can be re-used to receive lightning payments. An example is bosch@bitcoin.design. + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/Lightning-address.png" + retina = "/assets/images/guide/how-it-works/lightning-services/Lightning-address@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/Lightning-address-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/Lightning-address-mobile@2x.png" + alt-text = "Examples of lightning addresses" + width = 800 + height = 348 +%} + +### Receive payments offline + +Non-custodial lightning wallets need to be online to receive payments. [Daily spending wallets]({{ '/guide/daily-spending-wallet/' | relative_url }}), in particular, are regularly offline, so receiving payments can be difficult. + +LWSs can hold onto a payment (without assuming custody) and forward it to the user once they come online. A product that offers this for users is [Greenlight](https://blockstream.com/lightning/greenlight/). + +This service is usually required to be offered alongside an LSP. Read more about this [here](https://medium.com/breez-technology/get-ready-for-a-fresh-breez-multiple-apps-one-node-optimal-ux-519c4daf2536). + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/Offline-payment.png" + retina = "/assets/images/guide/how-it-works/lightning-services/Offline-payment@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/Offline-payment-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/Offline-payment-mobile@2x.png" + alt-text = "How an LWS helps users accept payments while offline" + width = 800 + height = 348 +%} + +### Swaps + +Moving bitcoin between lightning and on-chain can be costly and complicated if done by opening and closing payment channels. + +[Submarine swaps](https://blog.muun.com/a-closer-look-at-submarine-swaps-in-the-lightning-network/) allow users to easily move bitcoin between lightning and on-chain without having to manage and deal with payment channels. + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/Submarine-swaps.png" + retina = "/assets/images/guide/how-it-works/lightning-services/Submarine-swaps@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/Submarine-swaps-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/Submarine-swaps-mobile@2x.png" + alt-text = "How an LWS can conduct swaps moving bitcoin between on-chain and lightning" + width = 800 + height = 348 +%} + +### Watchtowers + +A lightning wallet must be online on a regular basis to track it's payment channels for cheating attempts. A [daily spending wallet]({{ '/guide/daily-spending-wallet/' | relative_url }}), in particular, is offline whenever the user stops using the app. This means there is a greater risk of cheating attempts. + +A [watchtower](https://bitcoinops.org/en/topics/watchtowers/) service can fix this. Watchtowers monitor the payment channels of offline users. If a counterparty attempts to steal a user's funds, the watchtower can step in to help. The watchtower can prevent the theft by submitting a justice transaction. + +{% include tip/open.html color="blue" icon="info" label="Using watchtowers" %} + +It's best practice to use a watchtower that is not controlled by the user's LSP. This way, the watchtower has no incentive to cheat the user. + +Multiple watchtowers can be used to limit the chances a users counterparty will collude with the watchtower. + +{% include tip/close.html %} + +{% include picture.html + image = "/assets/images/guide/how-it-works/lightning-services/Watchtowers.png" + retina = "/assets/images/guide/how-it-works/lightning-services/Watchtowers@2x.png" + mobile = "/assets/images/guide/how-it-works/lightning-services/Watchtowers-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/lightning-services/Watchtowers-mobile@2x.png" + alt-text = "Watchtowers monitoring offline lightning users" + width = 800 + height = 348 +%} + +## Further reading + +- [Introducing lightning service providers](https://medium.com/breez-technology/introducing-lightning-service-providers-fe9fb1665d5f) +- [Envisioning LSPs in the lightning economy](https://medium.com/breez-technology/envisioning-lsps-in-the-lightning-economy-832b45871992) + +--- + +Now, lets learn how [nodes]({{ '/guide/how-it-works/nodes/' | relative_url }}) work. + +{% include next-previous.html + previousUrl = "/guide/how-it-works/liquidity/" + previousName = "Lightning liquidity" + nextUrl = "/guide/how-it-works/nodes/" + nextName = "Nodes" +%} diff --git a/guide/how-it-works/liquidity.md b/guide/how-it-works/liquidity.md index 43a20e426..d3373132d 100644 --- a/guide/how-it-works/liquidity.md +++ b/guide/how-it-works/liquidity.md @@ -284,7 +284,7 @@ If the user does not have bitcoin in their wallet, they do not need outbound liq One way to help your users receive inbound liquidity is through LSPs (Lightning Service Providers). You could run your own LSP service or integrate your product with an existing LSP. -[Read the LSP section]({{'/guide/how-it-works/lightning-service-providers/#inbound-liquidity' | relative_url}}) to learn more. [Breez](https://breez.technology/) is an example of a wallet that does this. +[Read the LSP section]({{'/guide/how-it-works/lightning-services/#what-is-a-lightning-service-provider' | relative_url}}) to learn more. [Breez](https://breez.technology/) is an example of a wallet that does this. ### Outbound liquidity @@ -296,7 +296,7 @@ One way to accomplish this could be through an [instant channel open]({{'/guide/ #### LSP Swap-In -Another way to handle this would be through a swap-in service, where the user sends on-chain funds to an LSP and the LSP opens a channel for them. [Read the LSP section]({{'/guide/how-it-works/lightning-service-providers/#swap-in' | relative_url}}) to learn more. [Phoenix](https://phoenix.acinq.co/) is an example of a wallet that does this. +Another way to handle this would be through a swap-in service, where the user sends on-chain funds to an LSP and the LSP opens a channel for them. [Read the LSP section]({{'/guide/how-it-works/lightning-services/#on-chain-funding' | relative_url}}) to learn more. [Phoenix](https://phoenix.acinq.co/) is an example of a wallet that does this. ### Channel Management @@ -310,11 +310,11 @@ By combining the business incentives of an LSP, clever engineering, and good des --- -Next, let's look at how [lightning service providers]({{ '/guide/how-it-works/lightning-service-providers/' | relative_url }}) work. +Next, let's look at how [lightning-services]({{ '/guide/how-it-works/lightning-services/' | relative_url }}) work. {% include next-previous.html previousUrl = "/guide/how-it-works/coin-selection/" previousName = "Coin selection" - nextUrl = "/guide/how-it-works/lightning-service-providers/" - nextName = "Lightning service providers" + nextUrl = "/guide/how-it-works/lightning-services/" + nextName = "Lightning services" %} diff --git a/guide/how-it-works/node.md b/guide/how-it-works/node.md index 648ad82d9..0afcc55cb 100644 --- a/guide/how-it-works/node.md +++ b/guide/how-it-works/node.md @@ -226,8 +226,8 @@ For more information: Next, let's learn about the different bitcoin [payment request formats]({{ '/guide/how-it-works/payment-request-formats/' | relative_url }}) that exist. {% include next-previous.html - previousUrl = "/guide/how-it-works/lightning-service-providers/" - previousName = "Lightning service providers" + previousUrl = "/guide/how-it-works/lightning-services/" + previousName = "Lightning services" nextUrl = "/guide/how-it-works/payment-request-formats/" nextName = "Payment request formats" %}