Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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 <bolt11>
lightning-cli xpay <bolt11>
```

Note that there are lower-level interfaces (and more options to these
Expand Down
2 changes: 1 addition & 1 deletion doc/beginners-guide/beginners-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
6 changes: 3 additions & 3 deletions doc/lightningd.8.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
---
Expand Down Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion doc/node-operators-guide/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 ?
Expand Down
Loading