![]() |
![]()
| ![]() |
![]()
NAMElightning-bkpr-editdescriptionbypaymentid -- Command to change the description for events with {payment_id} after they're made SYNOPSISbkpr-editdescriptionbypaymentid payment_id description DESCRIPTIONThe bkpr-editdescriptionbypaymentid RPC command updates all chain and channel events that match the {payment_id} with the provided {description}
RETURN VALUEOn success, an object containing updated is returned. It is an array of objects, where each object contains:
If type is "chain": - outpoint (string): The txid:outnum for this event. - blockheight (u32): For chain events, blockheight this occured at. - origin (string, optional): The account this movement originated from. - payment_id (hex, optional): Lightning payment identifier. For an htlc, this will be the preimage. - txid (txid, optional): The txid of the transaction that created this event. If type is "onchain_fee": - txid (txid): The txid of the transaction that created this event. If type is "channel": - fees_msat (msat, optional): Amount paid in fees. - is_rebalance (boolean, optional): Is this payment part of a rebalance. - payment_id (hex, optional): Lightning payment identifier. For an htlc, this will be the preimage. - part_id (u32, optional): Counter for multi-part payments. AUTHORLisa Neigut <niftynei@gmail.com> is mainly responsible. SEE ALSOlightning-bkpr-editdescriptionbyoutpoint(7), lightning-bkpr-listaccountevents(7), lightning-bkpr-listincome(7) RESOURCESMain web site: https://github.com/ElementsProject/lightning EXAMPLESExample 1: Request: $ lightning-cli bkpr-editdescriptionbypaymentid -k "payment_id"="paymentid0000202020202020202020202020202020202020202020202020202" "description"="edited invoice description from description send some sats l2 to l3" { Response: { Example 2: Request: $ lightning-cli bkpr-editdescriptionbypaymentid -k "payment_id"="c000010101010101010101010101010101010101010101010101010101010101" "description"="edited invoice description for non existing payment id" { Response: {
|