mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2025-02-23 06:55:13 +01:00
Code Issues Projects Releases Wiki Activity
core-lightning/plugins/offers_invreq_hook.h

17 lines
537 B
C
Raw Normal View History

plugins/offers: add code to catch invoice_request onion messages. We prepare an invoice, but there's no code to send an error reply yet (future patch). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-12-16 13:43:32 +10:30
#ifndef LIGHTNING_PLUGINS_OFFERS_INVREQ_HOOK_H
#define LIGHTNING_PLUGINS_OFFERS_INVREQ_HOOK_H
#include "config.h"
#include <plugins/libplugin.h>
offers: import latest variant from draft. In particular, this changes the name of a field in invoice_request: `payer_signature` becomes simply `signature`. So we allow both for now, and send the old one unless deprecated_apis is disabled. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-03-22 19:20:13 +10:30
extern u16 cltv_final;
offers: create a real blinded path, if necessary. It's just to a direct peer, and we only create one, but this is enough to test, and make payments to non-public nodes work. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-11-09 13:02:00 +10:30
extern u32 blockheight;
extern struct secret invoicesecret_base;
extern struct pubkey id;
plugin/offers: connect if necessary for replying to invoice_request. You can disable this with `fetchinvoice-noconnect`. Changelog-EXPERIMENTAL: We will now reply to invoice_request messages even if reply path requires us to make an outgoing connection (LDK does this) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2024-05-13 18:19:45 +09:30
extern bool disable_connect;
plugins/offers: add code to catch invoice_request onion messages. We prepare an invoice, but there's no code to send an error reply yet (future patch). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-12-16 13:43:32 +10:30
/* We got an onionmessage with an invreq! */
struct command_result *handle_invoice_request(struct command *cmd,
common: remove support for pre v0.10.2 onionmessages. Temporarily disable sendpay_blinding test which uses obsolete onionmsg; there's still some debate on the PR about how blinded HTLCs will work. Changelog-EXPERIMENTAL: onionmessage: removed support for v0.10.1 onion messages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-11-30 13:36:04 +10:30
const u8 *invreqbin,
common: update to latest onion message spec. Mainly, field name changes. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-EXPERIMENTAL: Protocol: Support for forwarding blinded payments (as per latest draft)
2022-10-17 11:14:39 +10:30
struct blinded_path *reply_path STEALS);
plugins/offers: add code to catch invoice_request onion messages. We prepare an invoice, but there's no code to send an error reply yet (future patch). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-12-16 13:43:32 +10:30
#endif /* LIGHTNING_PLUGINS_OFFERS_INVREQ_HOOK_H */
Reference in a new issue Copy permalink