mirror of
https://github.com/ElementsProject/lightning.git
synced 2024-11-19 18:11:28 +01:00
00ac1a9475
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: JSON-RPC: `sendpay`, `listsendpays`, `delpay` new fields `created_index` (old: `id`) and `updated_index`.
141 lines
6.0 KiB
Markdown
141 lines
6.0 KiB
Markdown
lightning-sendonion -- Send a payment with a custom onion packet
|
|
================================================================
|
|
|
|
SYNOPSIS
|
|
--------
|
|
|
|
**sendonion** *onion* *first\_hop* *payment\_hash* [*label*] [*shared\_secrets*] [*partid*] [*bolt11*]
|
|
[*amount\_msat*] [*destination*]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
|
|
The **sendonion** RPC command can be used to initiate a payment attempt with a
|
|
custom onion packet. The onion packet is used to deliver instructions for hops
|
|
along the route on how to behave. Normally these instructions are indications
|
|
on where to forward a payment and what parameters to use, or contain details
|
|
of the payment for the final hop. However, it is possible to add arbitrary
|
|
information for hops in the custom onion, allowing for custom extensions that
|
|
are not directly supported by Core Lightning.
|
|
|
|
The onion is specific to the route that is being used and the *payment\_hash*
|
|
used to construct, and therefore cannot be reused for other payments or to
|
|
attempt a separate route. The custom onion can generally be created using the
|
|
`devtools/onion` CLI tool, or the **createonion** RPC command.
|
|
|
|
The *onion* parameter is a hex-encoded 1366 bytes long blob that was returned
|
|
by either of the tools that can generate onions. It contains the payloads
|
|
destined for each hop and some metadata. Please refer to [BOLT 04][bolt04] for
|
|
further details.
|
|
|
|
The *first\_hop* parameter instructs Core Lightning which peer to send the onion
|
|
to. It is a JSON dictionary that corresponds to the first element of the route
|
|
array returned by *getroute*. The following is a minimal example telling
|
|
Core Lightning to use any available channel to `022d223620a359a47ff7f7ac447c85c46c923da53389221a0054c11c1e3ca31d59`
|
|
to add an HTLC for 1002 millisatoshis and a delay of 21 blocks on top of the current blockheight:
|
|
|
|
```json
|
|
{
|
|
"id": "022d223620a359a47ff7f7ac447c85c46c923da53389221a0054c11c1e3ca31d59",
|
|
"amount_msat": "1002msat",
|
|
"delay": 21,
|
|
}
|
|
```
|
|
|
|
If the first element of *route* does not have "channel" set, a
|
|
suitable channel (if any) will be chosen, otherwise that specific
|
|
short-channel-id is used.
|
|
|
|
The *payment\_hash* parameter specifies the 32 byte hex-encoded hash to use as
|
|
a challenge to the HTLC that we are sending. It is specific to the onion and
|
|
has to match the one the onion was created with.
|
|
|
|
The *label* parameter can be used to provide a human readable reference to
|
|
retrieve the payment at a later time.
|
|
|
|
The *shared\_secrets* parameter is a JSON list of 32 byte hex-encoded secrets
|
|
that were used when creating the onion. Core Lightning can send a payment with a
|
|
custom onion without the knowledge of these secrets, however it will not be
|
|
able to parse an eventual error message since that is encrypted with the
|
|
shared secrets used in the onion. If *shared\_secrets* is provided Core Lightning
|
|
will decrypt the error, act accordingly, e.g., add a `channel_update` included
|
|
in the error to its network view, and set the details in *listsendpays*
|
|
correctly. If it is not provided Core Lightning will store the encrypted onion,
|
|
and expose it in *listsendpays* allowing the caller to decrypt it
|
|
externally. The following is an example of a 3 hop onion:
|
|
|
|
```json
|
|
[
|
|
"298606954e9de3e9d938d18a74fed794c440e8eda82e52dc08600953c8acf9c4",
|
|
"2dc094de72adb03b90894192edf9f67919cb2691b37b1f7d4a2f4f31c108b087",
|
|
"a7b82b240dbd77a4ac8ea07709b1395d8c510c73c17b4b392bb1f0605d989c85"
|
|
]
|
|
```
|
|
|
|
If *shared\_secrets* is not provided the Core Lightning node does not know how
|
|
long the route is, which channels or nodes are involved, and what an eventual
|
|
error could have been. It can therefore be used for oblivious payments.
|
|
|
|
The *partid* value, if provided and non-zero, allows for multiple parallel
|
|
partial payments with the same *payment\_hash*.
|
|
|
|
The *bolt11* parameter, if provided, will be returned in
|
|
*waitsendpay* and *listsendpays* results.
|
|
|
|
The *destination* parameter, if provided, will be returned in **listpays** result.
|
|
|
|
The *amount\_msat* parameter is used to annotate the payment, and is returned by
|
|
*waitsendpay* and *listsendpays*.
|
|
|
|
RETURN VALUE
|
|
------------
|
|
|
|
[comment]: # (GENERATE-FROM-SCHEMA-START)
|
|
On success, an object is returned, containing:
|
|
|
|
- **created\_index** (u64): 1-based index indicating order this payment was created in *(added v23.11)*
|
|
- **id** (u64): old synonym for created\_index
|
|
- **payment\_hash** (hash): the hash of the *payment\_preimage* which will prove payment
|
|
- **status** (string): status of the payment (could be complete if already sent previously) (one of "pending", "complete")
|
|
- **created\_at** (u64): the UNIX timestamp showing when this payment was initiated
|
|
- **amount\_sent\_msat** (msat): The amount sent
|
|
- **amount\_msat** (msat, optional): The amount delivered to destination (if known)
|
|
- **destination** (pubkey, optional): the final destination of the payment if known
|
|
- **label** (string, optional): the label, if given to sendpay
|
|
- **bolt11** (string, optional): the bolt11 string (if supplied)
|
|
- **bolt12** (string, optional): the bolt12 string (if supplied: **experimental-offers** only).
|
|
- **partid** (u64, optional): the partid (if supplied) to sendonion/sendpay
|
|
|
|
If **status** is "complete":
|
|
|
|
- **payment\_preimage** (secret): the proof of payment: SHA256 of this **payment\_hash**
|
|
- **updated\_index** (u64, optional): 1-based index indicating order this payment was changed *(added v23.11)*
|
|
|
|
If **status** is "pending":
|
|
|
|
- **message** (string, optional): Monitor status with listpays or waitsendpay
|
|
|
|
[comment]: # (GENERATE-FROM-SCHEMA-END)
|
|
|
|
If *shared\_secrets* was provided and an error was returned by one of the
|
|
intermediate nodes the error details are decrypted and presented
|
|
here. Otherwise the error code is 202 for an unparseable onion.
|
|
|
|
AUTHOR
|
|
------
|
|
|
|
Christian Decker <<decker.christian@gmail.com>> is mainly responsible.
|
|
|
|
SEE ALSO
|
|
--------
|
|
|
|
lightning-createonion(7), lightning-sendpay(7), lightning-listsendpays(7)
|
|
|
|
RESOURCES
|
|
---------
|
|
|
|
Main web site: <https://github.com/ElementsProject/lightning>
|
|
|
|
[bolt04]: https://github.com/lightning/bolts/blob/master/04-onion-routing.md
|
|
[comment]: # ( SHA256STAMP:ebda126fec67fe3b556a34b57323d13e20a996bc221cb0c48fbd1e16241259a0)
|