Proto commits in ElementsProject/lightning

These commits are when the Protocol Buffers files have changed: (only the last 100 relevant commits are shown)

2025-05-08

msggen: regenerate. Somehow GitHub's "Enable auto-merge" merged the PR without it actually passing. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

The documentation is generated from this commit.

lightningd: deprecate (undocumented!) "unknown" old_state field in channel_state_changed notification. Reported-by: daywalker90 Changelog-Deprecated: JSON-RPC: channel_state_changed notification field `old_state` value "unknown" (it will be omitted, instead) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2025-04-29

lightningd: support index/start/end pagination for listhtlcs. Changelog-Added: JSON-RPC: `listhtlcs` supports `index`, `start` and `end` parameters for pagination support. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

lightningd: wait interface for htlcs indexes. Note that documentation says invoice expiries can batch, but that's no longer true, so delete it. Usually, we miss a number because the change is too fast. This adds the wait interface, but it doesn't actually fire until the next commit, which wires it into the db code. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: JSON-RPC: `wait` now supports the `htlcs` (`listhtlcs`) subsystem.

lightningd: improve wait API by making details fields per-subsystem. It makes the schema simpler, and indeed, expressable by GRPC. Changelog-Added: JSON-RPC: `wait` now has separate `invoices`, `forwards` and `sendpays` objects for each subsystem. Changelog-Deprecated: JSON-RPC: `wait` reply `details` object: use subsytem specific object instead. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

lightningd: add created_index and updated_index to listhtlcs. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: JSON-RPC: `listhtlcs` has `created_index` and `updated_index` fields.

2025-04-28

lightningd: add `short_channel_id` option to listpeerchannels. Requested-by: @whitslack Closes: https://github.com/ElementsProject/lightning/issues/8233 Changelog-Added: JSON-RPC: `listpeerchannels` now has a `short_channel_id` parameter for just listing a specific channel. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2025-03-11

lightningd: remove accept-htlc-tlv-types. Changelog-Removed: accept-htlc-tlv-types (deprecated v23.08, disabled by default in v24.11). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2025-02-27

msggen: comply with grpc and rust naming conventions Changelog-Changed: Some enums, structs, functions in pyln-grpc-proto/cln-grpc/cln-rpc have been slightly renamed so they follow grpc and rust's naming convention

msggen: add channel_state_changed notification Changelog-None

msggen: add InjectOnionMessage Changelog-None

2025-02-24

setconfig: add transient option. Changelog-Added: JSON-RPC: `setconfig` now has a `transient` flag which means it won't rewrite your config file. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2025-02-21

add max_htlc_value_in_flight_msat to listpeerchan Changelog-Added: JSON-RPC: `listpeerchannels` new output fields `their_max_total_htlc_out_msat` and `our_max_total_htlc_out_msat` as the value of `max_htlc_value_in_flight` (as of BOLT02) set by the local and remote nodes on channel creation. Changelog-Deprecated: JSON-RPC: `listpeerchannels` value `max_total_htlc_in_msat`: use `our_max_total_htlc_out_msat` instead to follow spec naming convention.

2025-02-12

decode: handle new bip353 fields. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

fetchinvoice: allow user to specify bip353 name corresponding to how they got offer. Changelog-Added: JSON-RPC: `fetchinvoice` BIP 353 name support (`bip353`). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2025-02-05

lightningd: implement unblacklist. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: JSON-RPC: `blacklistrune` now has an option to un-blacklist (`relist`).

2025-01-22

xpay: add maxdelay parameter Changelog-Added: Plugins: `xpay` now supports a `maxdelay` parameter for better `xpay-handle-pay` compatibility.

2024-12-17

doc: fix injectpaymentonion schema. I used an unknown arg and it didn't complain. injectpaymentonion's schema predated the sweep which fixed up use of "additionalProperties". Indeed, we were missing some properties! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

injectpaymentionion: allow specification of actual amount which reaches destination. This appears in listsendpays / listpays, and is useful information (if we know!). This doesn't fix old payments, but means that xpay can use this for new payments. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2024-12-16

doc: fix injectpaymentonion schema. I used an unknown arg and it didn't complain. injectpaymentonion's schema predated the sweep which fixed up use of "additionalProperties". Indeed, we were missing some properties! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

injectpaymentionion: allow specification of actual amount which reaches destination. This appears in listsendpays / listpays, and is useful information (if we know!). This doesn't fix old payments, but means that xpay can use this for new payments. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2024-11-28

msggen: add missing rpc commands new to 24.11 Changelog-None

2024-11-22

lightningd: add option for minimum seeker autoconnect peers Changelog-added: Added option --autoconnect-seeker-peers, allowing seeker to reach out to new nodes for additional gossip.

2024-11-19

bolt12: allow to inject payer_metadata Payer metadata is a field that controls the payer ID provided during the fetchinvoice process. There are use cases where this is highly useful, such as proving that the payer has paid for the correct item. Imagine visiting a merchant's website to pay for multiple offers, where one of these offers is a default offer (with no description and no set amount). In this scenario, the merchant could claim not to have received payment for a specific item. Since the same offer may be used to fetch invoices for different products, there needs to be a way to identify which product the invoice corresponds to. With this commit, it will be possible to inject payer metadata, which helps solve the issue described above. For example, possible payer metadata could be `to_hex(b"{payer_node_id}.{product_id}.{created_at}")`. Changelog-Added: JSON-RPC: `fetchinvoice` allows setting invreq_metadata via `payer_metadata` parameter. Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

2024-11-17

close: Print multiple txs; Fixes #6467 Changelog-Changed: `close` now outputs txs & txids of all closing transactions (splice candidates can cause there to be multiple).

2024-11-12

add listing options to listpays Changelog-Added: JSON-RPC: `listpays` has `index`, `start` and `limit` parameters for listing control.

2024-11-11

splice: Modify splice_signed to work with multiple channels `splice_signed` now searchs the PSBT for channel ids Changelog-Changed: `splice_signed` parameters are switched in order to make `channel_id` an optional parameter, enabling multi-splice-signatures.

splice: Allow splice_update to return signatures This is needed to all multi-channel splices. When channeld can return the signatures to the user (based on signing order precedent), it now does from splice_update. Additionally, we move sending of the initial psbt from splice_init down to splice_update. This is also necessary for correct psbt diff detection during multi-channel splices. Changelog-Changed: splice_update can in some cases now return the remotely partiall signed psbt to the user, if so `signtures_secured` will be true.

2024-10-30

doc: fix up missing fields from schemas. This allows the next patch (which makes the schemas stricter) to not break our tests. We add some missing fields (including dev fields, but they're empty and hidden), and add a few minor clarifications and a spelling fix. Most of these are new schemas for this release, so no mention in Changelog. Here is the difference in the man pages: --- doc/lightning-askrene-inform-channel.7.md.old 2024-10-29 17:33:07.714521584 +1030 +++ doc/lightning-askrene-inform-channel.7.md 2024-10-29 17:42:37.434280109 +1030 @@ -24,6 +24,8 @@ - **short\_channel\_id\_dir** (short\_channel\_id\_dir): The short channel id and direction +- **layer** (string): The name of the layer to apply this change to. +- **timestamp** (u64): The UNIX timestamp when this constraint was created. - **maximum\_msat** (msat, optional): The maximum value which this channel could pass. --- doc/lightning-askrene-listlayers.7.md.old 2024-10-29 17:33:07.716521571 +1030 +++ doc/lightning-askrene-listlayers.7.md 2024-10-29 17:42:37.424280316 +1030 @@ -29,13 +29,16 @@ - **channel\_updates** (array of objects): + - **short\_channel\_id\_dir** (short\_channel\_id\_dir): The short channel id and direction this update applies to. + - **enabled** (boolean, optional): True if this can be used, false otherwise. - **htlc\_minimum\_msat** (msat, optional): The minimum value allowed in this direction. - **htlc\_maximum\_msat** (msat, optional): The maximum value allowed in this direction. - **fee\_base\_msat** (msat, optional): The base fee to apply to use the channel in this direction. - **fee\_proportional\_millionths** (u32, optional): The proportional fee (in parts per million) to apply to use the channel in this direction. - - **delay** (u16, optional): The CLTV delay required for this direction. + - **cltv\_expiry\_delta** (u16, optional): The CLTV delay required for this direction. - **constraints** (array of objects): - **short\_channel\_id\_dir** (short\_channel\_id\_dir): The short channel id and direction + - **timestamp** (u64, optional): The UNIX timestamp when this constraint was created. - **maximum\_msat** (msat, optional): The maximum value which this channel could pass. --- doc/lightning-askrene-listreservations.7.md.old 2024-10-29 17:33:07.719521550 +1030 +++ doc/lightning-askrene-listreservations.7.md 2024-10-29 17:42:37.428280233 +1030 @@ -16,7 +16,7 @@ -On success, an object containing **layers** is returned. It is an array of objects, where each object contains: +On success, an object containing **reservations** is returned. It is an array of objects, where each object contains: --- doc/lightning-autoclean-status.7.md.old 2024-10-29 17:33:07.732521462 +1030 +++ doc/lightning-autoclean-status.7.md 2024-10-29 17:42:37.441279965 +1030 @@ -9,7 +9,7 @@ -The **autoclean-status** RPC command tells you about the status of the autclean plugin, optionally for only one subsystem. +The **autoclean-status** RPC command tells you about the status of the autoclean plugin, optionally for only one subsystem. --- doc/lightning-renepay.7.md.old 2024-10-29 17:33:07.927520140 +1030 +++ doc/lightning-renepay.7.md 2024-10-29 17:42:37.996268504 +1030 @@ -58,6 +58,9 @@ - **status** (string) (one of "complete", "pending", "failed"): Status of payment. +- **bolt11** (string, optional): The bolt11 invoice paid. *(added v23.08)* +- **bolt12** (string, optional): The bolt12 invoice paid. *(added v23.08)* +- **groupid** (u64, optional): The groupid used for these payment parts (as can be seen in listsendpays) *(added v23.08)* - **destination** (pubkey, optional): The final destination of the payment. --- doc/lightning-sendonion.7.md.old 2024-10-29 17:33:07.937520073 +1030 +++ doc/lightning-sendonion.7.md 2024-10-29 17:42:37.957269309 +1030 @@ -22,7 +22,7 @@ -- **first\_hop** (object): 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*.: +- **first\_hop** (object): 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* (so fields not mentioned here are ignored).: Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-EXPERIMENTAL: `renepay` return fields documented in schema (`bolt11`, `bolt12` and `groupid`)

2024-10-18

cln-grpc: add anchors/even to primitives The `anchors/even` channel type was missing from the grpc bindings. It is now the default channel type, so `fundchannel` over grpc fails with: ``` Failed to deserialize response : unknown variant `anchors/even`, expected one of `static_remotekey/even`, `anchor_outputs/even`, `anchors_zero_fee_htlc_tx/even`, `scid_alias/even`, `zeroconf/even` ``` Changelog-Changed: Channel type `anchors/even` was added to the grpc bindings.

2024-10-15

global: deprecate old names in JSON fields, add new ones. Changelog-Added: JSON-RPC: `decode` now used modern BOLT 4 language for blinded paths, `first_path_key`. Changelog-Deprecated: JSON-RPC: `decode` `blinding` in blinded path: use `first_path_key`. Changelog-Added: Plugins: `onion_message_recv` and `onion_message_recv_secret` hooks now used modern BOLT 4 language for blinded paths, `first_path_key`. Changelog-Deprecated: JSON-RPC: `onion_message_recv` and `onion_message_recv_secret` hooks `blinding` in blinded path: use `first_path_key`.

2024-10-14

keysend: Add `maxfee` to keysend for consistency with pay. ([#7227]) Changelog-Added: keysend: Add `maxfee` to keysend for consistency with pay. ([#7227])

2024-09-21

cln-grpc: add anchors/even to primitives The `anchors/even` channel type was missing from the grpc bindings. It is now the default channel type, so `fundchannel` over grpc fails with: ``` Failed to deserialize response : unknown variant `anchors/even`, expected one of `static_remotekey/even`, `anchor_outputs/even`, `anchors_zero_fee_htlc_tx/even`, `scid_alias/even`, `zeroconf/even` ``` Changelog-Changed: Channel type `anchors/even` was added to the grpc bindings.

2024-09-17

schemas: "description" field in "wait(any)invoice" is optional since BOLT12 For BOLT12 invoices, the "description" is field missing in the invoice responses. Update the schemas accordingly: - `doc/schemas/lightning-waitanyinvoice.json` - `doc/schemas/lightning-waitinvoice.json` Also commit the generated msggen, cln-grpc, cln-rpc and pyln-grpc-proto files. Changelog-Fixed: schemas: Make description in `Wait(any)invoiceResponse` optional to handle BOLT12

2024-09-16

schemas: "description" field in "wait(any)invoice" is optional since BOLT12 For BOLT12 invoices, the "description" is field missing in the invoice responses. Update the schemas accordingly: - `doc/schemas/lightning-waitanyinvoice.json` - `doc/schemas/lightning-waitinvoice.json` Also commit the generated msggen, cln-grpc, cln-rpc and pyln-grpc-proto files. Changelog-Fixed: schemas: Make description in `Wait(any)invoiceResponse` optional to handle BOLT12

2024-08-13

renepay: add cli option exclude msggen cannot handle the complex type in renepay-exclude, therefore I added a rule override for it, just like pay-exclude. ``` msggen cln-grpc/proto/node.proto Traceback (most recent call last): File "/home/rusty/devel/cvs/lightning/contrib/msggen/msggen/__main__.py", line 131, in <module> main() File "/home/rusty/devel/cvs/lightning/contrib/msggen/msggen/__main__.py", line 115, in main run() File "/home/rusty/devel/cvs/lightning/contrib/msggen/msggen/__main__.py", line 72, in run service = load_jsonrpc_service( ^^^^^^^^^^^^^^^^^^^^^ File "/home/rusty/devel/cvs/lightning/contrib/msggen/msggen/utils/utils.py", line 241, in load_jsonrpc_service methods = [load_jsonrpc_method(name) for name in grpc_method_names] ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/rusty/devel/cvs/lightning/contrib/msggen/msggen/utils/utils.py", line 209, in load_jsonrpc_method request = CompositeField.from_js(schema["methods"][rpc_name]['request'], path=name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/rusty/devel/cvs/lightning/contrib/msggen/msggen/model.py", line 297, in from_js field = ArrayField.from_js(fpath, ftype) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/rusty/devel/cvs/lightning/contrib/msggen/msggen/model.py", line 464, in from_js itemtype = UnionField.from_js(child_js, path) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/rusty/devel/cvs/lightning/contrib/msggen/msggen/model.py", line 393, in from_js itemtype = PrimitiveField( ^^^^^^^^^^^^^^^ TypeError: PrimitiveField.__init__() missing 2 required positional arguments: 'added' and 'deprecated' ``` Signed-off-by: Lagrang3 <lagrang3@protonmail.com> Changelog-EXPERIMENTAL: renepay: add cli option "exclude" to manually disable channels and nodes.

2024-08-12

bkpr: add payment_id parameter to listaccountevents to filter events. When you have *lots* of events in your bkpr database looking up a specific event via calling bkpr-listaccountevents and using jq or grep to filter gets very slow (and wasteful of CPU and disk resources). This commit adds the paremeter payment_id to the call to filter for a specific payment id via a where clause in the request to the database of bkpr. Changelog-Added: Plugins: Add payment_id parameter to bkpr-listaccountevents to filter events.

2024-08-01

wire: rename "offer_node_id" to "offer_issuer_id" to match latest BOLT. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

global: update BOLT12 quotes. This is a final sweep to match the current BOLT12 text: 1563d13999d342680140c693de0b9d65aa522372 ("More bolt12 test vectors.") Only two code changes, to change the order of checks to match the bolt, and to give a warning on decode if a path is empty. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

plugins/offers: handle invreq_paths in invoice_requests, set them if necessary. Changelog-EXPERIMENTAL: offers: `invoicerequest` will set a blinded path if we're an unannounced node. Changelog-EXPERIMENTAL: offers: `sendinvoice` will use a blinded path in an invoice_request, if specified. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2024-07-31

rpc: Removing `category` and `verbose` from json_command struct

rpc: Removing `description` from json_command struct

2024-07-18

lightningd: remove expermential "sendonionmessage" function. It was only ever expermental, so I don't feel bad about just removing it. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Removed: JSON-RPC: `sendonionmessage` (was experimental only, use `injectonionmessage`)

2024-07-15

splice: Add funding outnum Fixes #7005 Changelog-Changed: Added outnum of new funding output to splice_signed RPC command

2024-07-11

bolt12: partial support for minimal offer Making sure that we are able to fetch the invoice from an offer without description E pyln.client.lightning.RpcError: RPC call failed: method: offer, payload: {'amount': '2msat'}, error: {'code': -32602, 'message': 'bolt12: Offer does not contain a description: invalid token \'"lno1qgsqvgnwgcg35z6ee2h3yczraddm72xrfua9uve2rlrm9deu7xyfzrcgqyppvggz953rvg9rtxj8lalh43z8epwydjfrmffn3y3p5qz5cywpu09rr4vs"\''} Link: https://github.com/ElementsProject/lightning/issues/7405 Link: https://github.com/ElementsProject/lightning/issues/7404 Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

2024-07-09

doc: fix schema for listconfigs. We never call `listconfigs` in our tests with `experimental-offers` enabled, so we didn't notice that the schema is wrong: it does not expect the "plugin" field in 'fetchinvoice-noconnect'. The next patch folds the fetchinvoice plugin into the offers plugin, which is enabled even if `experimental-offers` isn't (for `decode`), so we notice it. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2024-06-27

docs: notifications schema update Changelog-None.

2024-06-20

autoclean: remove autocleaninvoice command. Changelog-Removed: JSON-RPC: `autocleaninvoice` command (deprecated v22.11, EOL v24.02) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2024-06-14

offers: remove deprecated @ prefix. Somehow, this documentation got lost during the Great Rewrite, so restore that too. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-EXPERIMENTAL: JSON-RPC: `offer` removed `@` prefix support from `recurrence_base` (use `recurrence_start_any_period` set to `false`)

2024-05-23

msggen: Include AddPsbtOutput to RPC list and meta field map; regenerate libraries

2024-05-17

msggen: add emergencyrecover, recover, recoverchannel methods Changelog-None

msggen: add funderupdate method Changelog-None

msggen: add help method Changelog-None

msggen: fix invoice request missing exposeprivatechannels Changelog-None

msggen: add routes to decode and decodepay Changelog-None

msggen: add listinvoicerequests, disableinvoicerequest, invoicerequest methods Changelog-None

msggen: add makesecret method Changelog-None

msggen: add multiwithdraw method Changelog-None

msggen: add showrunes method Changelog-None

msggen: add createrune method

msggen: add blacklistrune method

msggen: add listconfigs method Changelog-None

msggen: add checkrune method

msggen: add dev-forget-channel method Changelog-None

2024-05-16

msggen: Add notifications to proto-file

msggen: Schema for ConnectNotification + collisions The schema in the docs for the `ConnectNotification` was faulty. I've already fix this in https://github.com/ElementsProject/lightning/pull/7085 The new schema is ``` { "connect" : { "address" : { "address" : "127.0.0.1", "port" : 38012, "type" : "ipv4" }, "direction" : "in", "id" : "022d223620a359a47ff7f7ac447c85c46c923da53389221a0054c11c1e3ca31d59" } } ``` The `address` in the `connect` field will be encoded in protobuf as `ConnectAddress`. However, this collides with the `ConnectAddress` that is defined in the `connect` rpc-method. This commit - Updates the schema in `doc/schemas/notification/connect.json` - Changes `msggen` to include an override to `PeerConnect` for any notification typename that starts with `Connect` Both have an `address` field which is a composite type. This results in naming collisions schema's: Updated schema for connect-notification schema for connect notification + overrides Override ConnectAddress to `PeerConnectAddress` in protobuf for notifications

msggen : Add notification-messages to proto-file

msggen: Choose better when a subfield is optional **Problem Description** In previous commits I introduced some new fields to `msggen`. One example is `CustomMsgResponse` in `cln-grpc/src/notification.rs`. ```rust pub struct CustomMsgResponse { #[serde(skip_serializing_if = "Option::is_none")] pub peer_id: Option<PublicKey>, #[serde(skip_serializing_if = "Option::is_none")] pub payload: Option<String>, } ``` The `peer_id` and `payload` are required parameters. However, the generated code is still marking them as `Optional`. This is a choice made by `msggen`. It does this because `payload` and `peer_id` are recently added fields. By marking the field as optional the language bindings would also work when used on an older version of Core-Lightning. In this scenario. Marking them as optional is overkill. The `CustomMsgStruct` and `payload` field are created in the same version of CoreLightning. This commit solves this behavior.

2024-05-15

msggen: add sendonionmessage method Changelog-None

msggen: add setconfig method Changelog-None

msggen: add setpsbtversion method Changelog-None

msggen: add upgradewallet method Changelog-None

msggen: add reserveinputs method Changelog-None

msggen: add unreserveinputs method Changelog-None

msggen: add splice_signed method

msggen: add splice_update method

2024-05-13

msggen: add plugin method Changelog-None

msggen: add renepay method Changelog-None

msggen: add renepaystatus method Changelog-None

msggen: add sendinvoice method Changelog-None

bolt12: allow first_node_id in blinded path to be a scid. We don't actually support it yet, but this threads through the type change, puts it in "decode" etc. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2024-05-09

logging: add TRACE between DEBUG and IO By moving super-noisy debugging logging to new TRACE level we can make long-term logging at DEBUG possible w/o removing any logging. Addresses ([#7279]) Related Issues: https://github.com/ElementsProject/lightning/issues/6927 https://github.com/chrisguida/smaug/issues/34 https://github.com/ZmnSCPxj/clboss/issues/194

2024-04-25

plugin/clnrest: Adding new config param as `clnrest-swagger-root` - Updated config params and plugin - Updated documentation Changelog-Added: Added a new configuration for clnrest plugin to change the default Swagger UI path from `/` to custom url.

msggen: add getlog method Changelog-None

msggen: add missing bkpr-* methods Changelog-None

2024-04-24

msggen: add delforward method Changelog-None

2024-04-23

msggen: add low level fundchannel methods Changelog-None

msggen: add methods autoclean-once and autoclean-status, fix bkpr-listincome Changelog-None

2024-04-22

msggen: add delpay method

2024-04-21

msggen: add low level openchannel methods Changelog-None

2024-04-18

msggen: fix walk through nested json schemas Changelog-None

2024-04-17

schema: add multifundchannel generation Changelog-None

2024-03-25

lightningd: remove delexpiredinvoice Changelog-Removed: JSON-RPC: `delexpiredinvoice` (deprecated v22.11, EOL v24.02) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

lightningd: remove `channels` from `listpeers`. Changelog-Removed: JSON-RPC: `listpeers` `channels` (deprecated v23.02, EOL v24.02) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2024-03-20

pay: add `partial_msat` option to make partial payment. a.k.a. "Pay with a friend!". Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: JSON-RPC: `pay` has a new parameter `partial_msat` to only pay part of an invoice (someone else presumably will pay the rest at the same time!) Suggested-by: Calle

2024-03-19

doc: Updated parameter descriptions for *.request.json Added descriptions for rpc command parameters This also performs the following fixes: 1. delforward parameters are compulsory (required). 2. disableinvoicerequest request added `added` field. 3. invoice request order fixed (label then description, not vice-versa!). 4. listpeers log levels are a proper enum 5. description parameter documented for sendonion requests. 6. deprecatred amount_msat removed from sendpay request. 7. sendpay request partid type fixed to u64 (was u16!) 8. sendpay request localinvreqid type tightened to hash (was hex) 9. sendpay request payment_metadata and description fields documented. 10. sendpsbt request reserve type fixed to u32 (was boolean) 11. utxopsbt request satoshi type fixed to msat_or_all (was msat) 12. withdraw request parameter satoshi is compulsory (required) 13. fundchannel_start request amount is sat, not msat_or_all. 14. openchannel_init request amount is sat, not msat 15. openchannel_init close_to is a string, not hex. 16: invoice labels can be strings OR numbers. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

script: Update scripts - Update `make doc-all` script - `fromschema.py` script - Updated to generate whole doc/lightning-*.md via doc/schemas/lightning-*.json file - Updated to print request params - Added `oneOfMany` condition for request params - Added `pairedWith` condition for request params - Added `dependentUpon` condition for request params - Updated for pre and post_return_value for response - Hiding `hidden` fields - `descriptions` are array now - Unified gaps between titles - Added default key-value pair - script: msggen, sql-schema, listconfig and pyln-testing script updates This does not add created markdowns for cleaner review. We will add the markdown files in a separate commit.

JSON: don't return a raw result string for "stop" and "recover". In general, results should always be an object, so we can add new fields later (e.g. warnings!). But we violated this for "stop", and when "recover" used the same infrastructure, it started doing the same thing. I'm assuming nobody cares, so we don't need to do a deprecation cycle. Changelog-Changed: JSON-RPC: `stop` and `recover` now return a JSON object (not a raw string!) like every other command does. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

2024-02-16

peer_control: Add lost_state param inside listpeerchannels rpc, which'd help us identify if we've fall behind or lost some state.

2024-02-07

doc: Fix schema for `offer.amount`, it can be a non-BTC unit too The `amount` field is intended to be either a native unit (`msat`, `sat` or `btc`) or it can also be a non-native unit that needs to be converted into native when creating the invoice. As such limiting the `amount` to only be native is very restrictive.