From d43e341c7d169e8dc525b05307da3e7da94a1211 Mon Sep 17 00:00:00 2001 From: Lagrang3 Date: Wed, 9 Sep 2026 08:44:01 +0100 Subject: [PATCH] docs: remove old references to pay, use xpay Changelog-None. Signed-off-by: Lagrang3 --- README.md | 6 +++--- doc/beginners-guide/beginners-guide.md | 2 +- doc/lightningd.8.md | 6 +++--- doc/node-operators-guide/faq.md | 2 +- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 48445f7c5f6e..2413580d0b1d 100644 --- a/README.md +++ b/README.md @@ -94,7 +94,7 @@ Useful commands: * [connect](https://docs.corelightning.org/reference/connect): connect to another lightning node. * [fundchannel](https://docs.corelightning.org/reference/fundchannel): create a channel to another connected node. * [invoice](https://docs.corelightning.org/reference/invoice): create an invoice to get paid by another node. -* [pay](https://docs.corelightning.org/reference/pay): pay someone else's invoice. +* [xpay](https://docs.corelightning.org/reference/xpay): pay someone else's invoice. * [plugin](https://docs.corelightning.org/reference/plugin): commands to control extensions. ### Care And Feeding Of Your New Lightning Node @@ -167,10 +167,10 @@ This returns some internal details, and a standard invoice string called `bolt11 [BOLT11]: https://github.com/lightning/bolts/blob/master/11-payment-encoding.md -The sender can feed this `bolt11` string to the `decode` command to see what it is, and pay it simply using the `pay` command: +The sender can feed this `bolt11` string to the `decode` command to see what it is, and pay it simply using the `xpay` command: ```bash -lightning-cli pay +lightning-cli xpay ``` Note that there are lower-level interfaces (and more options to these diff --git a/doc/beginners-guide/beginners-guide.md b/doc/beginners-guide/beginners-guide.md index 430a28ad189b..47f501e04d92 100644 --- a/doc/beginners-guide/beginners-guide.md +++ b/doc/beginners-guide/beginners-guide.md @@ -48,7 +48,7 @@ Useful commands: - [connect](ref:connect): connect to another lightning node. - [fundchannel](ref:fundchannel): create a channel to another connected node. - [invoice](ref:invoice): create an invoice to get paid by another node. -- [pay](ref:pay): pay someone else's invoice. +- [xpay](ref:xpay): pay someone else's invoice. - [plugin](ref:plugin): commands to control extensions. ## Care And Feeding Of Your New Lightning Node diff --git a/doc/lightningd.8.md b/doc/lightningd.8.md index 85c3717572ff..4765401e6d78 100644 --- a/doc/lightningd.8.md +++ b/doc/lightningd.8.md @@ -148,9 +148,9 @@ confirmed deeply. Once the channel *state* is *CHANNELD\_NORMAL*, you can start paying merchants over Lightning. Acquire a Lightning invoice from your favorite -merchant, and use lightning-pay(7) to pay it: +merchant, and use lightning-xpay(7) to pay it: - $ lightning-cli pay $INVOICE + $ lightning-cli xpay $INVOICE ERRORS CODE --- @@ -184,7 +184,7 @@ SEE ALSO lightningd-rpc(7), lightning-listconfigs(7), lightningd-config(5), lightning-cli(1), lightning-newaddr(7), lightning-listfunds(7), lightning-connect(7), -lightning-fundchannel(7), lightning-listpeers(7), lightning-pay(7), +lightning-fundchannel(7), lightning-listpeers(7), lightning-xpay(7), lightning-hsmtool(8) RESOURCES diff --git a/doc/node-operators-guide/faq.md b/doc/node-operators-guide/faq.md index 17ad832d7174..23bdbfd67edd 100644 --- a/doc/node-operators-guide/faq.md +++ b/doc/node-operators-guide/faq.md @@ -24,7 +24,7 @@ See the [listpeers](ref:listpeers) command. There are many reasons for a payment failure. The most common one is a [failure](https://github.com/lightning/bolts/blob/master/04-onion-routing.md#failure-messages) along the route from you to the payee. The best (and most common) solution to a route failure problem is to open more channels, which should increase the available routes to the recipient and lower the probability of a failure. -**Hint:** use the [`pay`](ref:pay) command which is will iterate through trying all possible routes, +**Hint:** use the [`xpay`](ref:xpay) command which is will iterate through trying all possible routes, instead of the low-level `sendpay` command which only tries the passed in route. ### How can I receive payments ?