mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-11-19 18:11:28 +01:00
Code Issues Projects Releases Wiki Activity
f100b1cdf1
core-lightning/common/features.h

180 lines
6.3 KiB
C
Raw Normal View History

features: Move feature-handling code to a common/features.c source.
2018-01-12 14:35:52 +01:00
#ifndef LIGHTNING_COMMON_FEATURES_H
#define LIGHTNING_COMMON_FEATURES_H
#include "config.h"
#include <ccan/short_types/short_types.h>
#include <ccan/tal/tal.h>
common/features: use bitmaps internally, have explicit init function. This is to prepare for dynamic features, including making plugins first class citizens at setting them. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-03-31 00:39:00 +02:00
enum feature_place {
INIT_FEATURE,
GLOBAL_INIT_FEATURE,
NODE_ANNOUNCE_FEATURE,
CHANNEL_FEATURE,
BOLT11_FEATURE,
common/features: add explicit bolt12 feature sets. The spec only specifies the mpp bit for invoices, but in general they are separate spaces. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-11-09 03:32:00 +01:00
BOLT12_OFFER_FEATURE,
BOLT12_INVREQ_FEATURE,
BOLT12_INVOICE_FEATURE,
common/features: use bitmaps internally, have explicit init function. This is to prepare for dynamic features, including making plugins first class citizens at setting them. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-03-31 00:39:00 +02:00
};
common/features: add explicit bolt12 feature sets. The spec only specifies the mpp bit for invoices, but in general they are separate spaces. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-11-09 03:32:00 +01:00
#define NUM_FEATURE_PLACE (BOLT12_INVOICE_FEATURE+1)
plugin: Move feature_place enum to features.h Better not duplicate these, we might end up mixing them.
2020-03-31 15:32:16 +02:00
extern const char *feature_place_names[NUM_FEATURE_PLACE];
common/features: use bitmaps internally, have explicit init function. This is to prepare for dynamic features, including making plugins first class citizens at setting them. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-03-31 00:39:00 +02:00
/* The complete set of features for all contexts */
struct feature_set {
u8 *bits[NUM_FEATURE_PLACE];
};
common/features: don't use internal global. Turns out that unnecessary: all callers can access the feature_set, so make it much more like a normal primitive. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-02 06:04:47 +02:00
/* Create feature set for a known feature. */
struct feature_set *feature_set_for_feature(const tal_t *ctx, int feature);
common/features: use bitmaps internally, have explicit init function. This is to prepare for dynamic features, including making plugins first class citizens at setting them. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-03-31 00:39:00 +02:00
common/features: don't use internal global. Turns out that unnecessary: all callers can access the feature_set, so make it much more like a normal primitive. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-02 06:04:47 +02:00
/* Marshalling a feature set */
subdaemons: initialize feature routines with explicit feature_set. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-03-31 00:39:00 +02:00
struct feature_set *fromwire_feature_set(const tal_t *ctx,
const u8 **ptr, size_t *max);
void towire_feature_set(u8 **pptr, const struct feature_set *fset);
common/features: don't use internal global. Turns out that unnecessary: all callers can access the feature_set, so make it much more like a normal primitive. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-02 06:04:47 +02:00
/* a |= b, or returns false if features already in a */
bool feature_set_or(struct feature_set *a,
const struct feature_set *b TAKES);
plugins: actually change global features when plugins tell us to. This cleans up the boutique handling of features, and importantly, it means that if a plugin says to offer a feature in init, we will now *accept* that feature. Changelog-Fixed: Plugins: setting an 'init' feature bit allows us to accept it from peers. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-03-31 00:39:00 +02:00
features: add 'feature_bit_sub', which will subtract/unset bits Given a two sets of featurebits, unset the featurebits in the first set that are set in the second set
2020-10-22 20:18:38 +02:00
/* a - b, or returns false if features not already in a */
bool feature_set_sub(struct feature_set *a,
const struct feature_set *b TAKES);
common: make BOLT11 use the normal feature array. This was decided at a recent spec meeting: in particular, mpp and var_onion_optin options will be used here. We enhanced "features_supported" into "features_unsupported" so it can return the first un-handlable bit number. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-11-23 01:19:23 +01:00
/* Returns -1 if we're OK with all these offered features, otherwise first
* unsupported (even) feature. */
cleanup: make 'u8 *features' and 'struct feature_set *fset' more explicit. It's almost always "their_features" and "our_features" respectively, so make those names clear. Suggested-by: @cdecker Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-03 02:03:59 +02:00
int features_unsupported(const struct feature_set *our_features,
const u8 *their_features,
common/features: don't use internal global. Turns out that unnecessary: all callers can access the feature_set, so make it much more like a normal primitive. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-02 06:04:47 +02:00
enum feature_place p);
features: more general accessor functions. As we add more features, the current code is insufficient. 1. Keep an array of single feature bits, for easy switching on and off. 2. Create feature_offered() which checks for both compulsory and optional variants. 3. Invert requires_unsupported_features() and unsupported_features() which tend to be double-negative, all_supported_features() and features_supported(). 4. Move single feature definition from wire/peer_wire.h to common/features.h. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-03-13 16:41:55 +01:00
features: add support for channel_announcement features. This will be needed for wumbo, for example. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-03-31 00:39:00 +02:00
/* For the features in channel_announcement */
common/features: don't use internal global. Turns out that unnecessary: all callers can access the feature_set, so make it much more like a normal primitive. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-02 06:04:47 +02:00
u8 *get_agreed_channelfeatures(const tal_t *ctx,
cleanup: make 'u8 *features' and 'struct feature_set *fset' more explicit. It's almost always "their_features" and "our_features" respectively, so make those names clear. Suggested-by: @cdecker Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-03 02:03:59 +02:00
const struct feature_set *our_features,
common/features: don't use internal global. Turns out that unnecessary: all callers can access the feature_set, so make it much more like a normal primitive. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-02 06:04:47 +02:00
const u8 *theirfeatures);
features: add support for channel_announcement features. This will be needed for wumbo, for example. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-03-31 00:39:00 +02:00
features: more general accessor functions. As we add more features, the current code is insufficient. 1. Keep an array of single feature bits, for easy switching on and off. 2. Create feature_offered() which checks for both compulsory and optional variants. 3. Invert requires_unsupported_features() and unsupported_features() which tend to be double-negative, all_supported_features() and features_supported(). 4. Move single feature definition from wire/peer_wire.h to common/features.h. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-03-13 16:41:55 +01:00
/* Is this feature bit requested? (Either compulsory or optional) */
bool feature_offered(const u8 *features, size_t f);
features: add local_feature_negotiated / global_feature_negotiated helpers. We currently generally assume the features we offer are fixed; this makes the code clearer and handles where we offer features iff EXPERIMENTAL_FEATURES=1 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-12-03 00:05:06 +01:00
/* Was this feature bit offered by them and us? */
cleanup: make 'u8 *features' and 'struct feature_set *fset' more explicit. It's almost always "their_features" and "our_features" respectively, so make those names clear. Suggested-by: @cdecker Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-03 02:03:59 +02:00
bool feature_negotiated(const struct feature_set *our_features,
const u8 *their_features, size_t f);
features: add local_feature_negotiated / global_feature_negotiated helpers. We currently generally assume the features we offer are fixed; this makes the code clearer and handles where we offer features iff EXPERIMENTAL_FEATURES=1 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-12-03 00:05:06 +01:00
features: require dependent features at init handshake. This simplifies our test matrix, as we never have to handle talking to peers that specify one but not the other. This is particularly important for option_anchor_outputs which assumes option_static_remotekey. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-08-13 19:38:02 +02:00
/* Features can depend on other features: both must be set!
* Sets @depender, @missing_dependency if returns false.
*/
bool feature_check_depends(const u8 *their_features,
size_t *depender, size_t *missing_dependency);
common/features: don't use internal global. Turns out that unnecessary: all callers can access the feature_set, so make it much more like a normal primitive. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-02 06:04:47 +02:00
/* Return a list of what (init) features we advertize. */
const char **list_supported_features(const tal_t *ctx,
cleanup: make 'u8 *features' and 'struct feature_set *fset' more explicit. It's almost always "their_features" and "our_features" respectively, so make those names clear. Suggested-by: @cdecker Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-03 02:03:59 +02:00
const struct feature_set *fset);
lightningd: create --list-features-only which lists what features we support. This allows the lightning-rfc protocol tests to automatically query what features we support. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-29 03:01:55 +02:00
devtools/features: tool to convert feature bitmap to names. For example: ``` $ ./devtools/features 80008008226aa2 option_data_loss_protect/odd (optional) option_upfront_shutdown_script/odd (optional) option_gossip_queries/odd (optional) option_var_onion_optin/odd (optional) option_gossip_queries_ex/odd (optional) option_static_remotekey/odd (optional) option_payment_secret/even (compulsory) option_basic_mpp/odd (optional) option_anchor_outputs/odd (optional) option_shutdown_anysegwit/odd (optional) option_onion_messages/odd (optional) option_unknown_54/odd (optional) ``` Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-09-23 04:29:48 +02:00
/* Give a name for this feature */
const char *feature_name(const tal_t *ctx, size_t f);
common/features: expose feature bitmap low-level functions. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-03 06:16:03 +02:00
/* Low-level helpers to deal with big-endian bitfields. */
bool feature_is_set(const u8 *features, size_t bit);
void set_feature_bit(u8 **ptr, u32 bit);
features: Add featurebits_or helper to combine two featurebitstrings We will be doing this when collecting featurebits from the plugins, so make this a reusable function.
2020-01-30 15:40:09 +01:00
/* Given two featurebit vectors, combine them by applying a logical OR. */
u8 *featurebits_or(const tal_t *ctx, const u8 *f1 TAKES, const u8 *f2 TAKES);
features: Add function to unset a featurebit Needed so we can blank optional bits when comparing channel_types.
2022-04-15 14:24:09 +02:00
/* Unset a given bit in a featurebits string */
void featurebits_unset(u8 **ptr, size_t bit);
features: Add featurebits_or helper to combine two featurebitstrings We will be doing this when collecting featurebits from the plugins, so make this a reusable function.
2020-01-30 15:40:09 +01:00
channeld: handle upgrade match. We don't actually set desired_type yet, but this handles it. Changelog-EXPERIMENTAL: Protocol: we can now upgrade old channels to `option_static_remotekey` from https://github.com/lightningnetwork/lightning-rfc/pull/868 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-06-04 07:13:47 +02:00
/* Are these two feature bitsets functionally equal (one may have
* trailing zeroes)? */
bool featurebits_eq(const u8 *f1, const u8 *f2);
common/features: helper to pretty-print feature bits. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-06-04 03:53:55 +02:00
/* Good for debugging: returns comma-separated string of bits. */
const char *fmt_featurebits(const tal_t *ctx, const u8 *featurebits);
bolt: Reflect the zeroconf featurebits in code
2022-04-14 14:35:39 +02:00
struct feature_set *feature_set_dup(const tal_t *ctx,
const struct feature_set *other);
BOLT: update to master with gossip_queries_ex. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-20 08:57:20 +02:00
/* BOLT #9:
features: don't assume we'll always only advertize optional features. Generalize things a bit so OPTIONAL_FEATURE() and COMPULSORY_FEATURE() work with either odd or even features, then explicitly use OPTIONAL_FEATURE in our internal feature array. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-28 06:09:04 +02:00
*
* Flags are numbered from the least-significant bit, at bit 0 (i.e. 0x1,
* an _even_ bit). They are generally assigned in pairs so that features
* can be introduced as optional (_odd_ bits) and later upgraded to be compulsory
* (_even_ bits), which will be refused by outdated nodes:
* see [BOLT #1: The `init` Message](01-messaging.md#the-init-message).
*/
#define COMPULSORY_FEATURE(x) ((x) & 0xFFFFFFFE)
#define OPTIONAL_FEATURE(x) ((x) | 1)
features: more general accessor functions. As we add more features, the current code is insufficient. 1. Keep an array of single feature bits, for easy switching on and off. 2. Create feature_offered() which checks for both compulsory and optional variants. 3. Invert requires_unsupported_features() and unsupported_features() which tend to be double-negative, all_supported_features() and features_supported(). 4. Move single feature definition from wire/peer_wire.h to common/features.h. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-03-13 16:41:55 +01:00
channeld: Code to implement splicing Update the lightningd <-> channeld interface with lots of new commands to needed to facilitate spicing. Implement the channeld splicing protocol leveraging the interactivetx protocol. Implement lightningd’s channel_control to support channeld in its splicing efforts. Changelog-Added: Added the features to enable splicing & resizing of active channels.
2023-07-27 23:37:52 +02:00
/* BOLT-a526652801a541ed33b34d000a3b686a857c811f #9:
features: more general accessor functions. As we add more features, the current code is insufficient. 1. Keep an array of single feature bits, for easy switching on and off. 2. Create feature_offered() which checks for both compulsory and optional variants. 3. Invert requires_unsupported_features() and unsupported_features() which tend to be double-negative, all_supported_features() and features_supported(). 4. Move single feature definition from wire/peer_wire.h to common/features.h. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-03-13 16:41:55 +01:00
*
common/features: add channel_type definition, neaten header. Put all the normal spec-defined ones together. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-07-23 08:54:19 +02:00
* | Bits | Name |...
* | 0/1 | `option_data_loss_protect` |... IN ...
* | 3 | `initial_routing_sync` |... I ...
* | 4/5 | `option_upfront_shutdown_script` |... IN ...
* | 6/7 | `gossip_queries` |... IN ...
* | 8/9 | `var_onion_optin` |... IN9 ...
* | 10/11 | `gossip_queries_ex` |... IN ...
* | 12/13 | `option_static_remotekey` |... IN ...
* | 14/15 | `payment_secret` |... IN9 ...
* | 16/17 | `basic_mpp` |... IN9 ...
* | 18/19 | `option_support_large_channel` |... IN ...
* | 20/21 | `option_anchor_outputs` |... IN ...
* | 22/23 | `option_anchors_zero_fee_htlc_tx` |... IN ...
Makefile: update to latest BOLT text. In particular: - Bolt 4: add route blinding construction - Bolt 4: add blinded payments And this means it's not experimental, so we can turn it on by default! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: Protocol: blinded payments are now supported by default (not just with `--experimental-onion-messages`)
2023-04-07 08:55:33 +02:00
* | 24/25 | `option_route_blinding` |...IN9 ...
common/features: add channel_type definition, neaten header. Put all the normal spec-defined ones together. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-07-23 08:54:19 +02:00
* | 26/27 | `option_shutdown_anysegwit` |... IN ...
* | 44/45 | `option_channel_type` |... IN ...
* | 48/49 | `option_payment_metadata` |... 9 ...
channeld: Code to implement splicing Update the lightningd <-> channeld interface with lots of new commands to needed to facilitate spicing. Implement the channeld splicing protocol leveraging the interactivetx protocol. Implement lightningd’s channel_control to support channeld in its splicing efforts. Changelog-Added: Added the features to enable splicing & resizing of active channels.
2023-07-27 23:37:52 +02:00
* | 62/63 | `option_splice` |... IN ...
features: don't assume we'll always only advertize optional features. Generalize things a bit so OPTIONAL_FEATURE() and COMPULSORY_FEATURE() work with either odd or even features, then explicitly use OPTIONAL_FEATURE in our internal feature array. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-28 06:09:04 +02:00
*/
common/features: only support a single feature bitset. This is mainly an internal-only change, especially since we don't offer any globalfeatures. However, LND (as of next release) will offer global features, and also expect option_static_remotekey to be a *global* feature. So we send our (merged) feature bitset as both global and local in init, and fold those bitsets together when we get an init msg. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-11 04:52:04 +02:00
#define OPT_DATA_LOSS_PROTECT 0
#define OPT_INITIAL_ROUTING_SYNC 2
#define OPT_UPFRONT_SHUTDOWN_SCRIPT 4
#define OPT_GOSSIP_QUERIES 6
Makefile: update BOLTVERSION to flatten features. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-01-31 02:37:12 +01:00
#define OPT_VAR_ONION 8
common/features: only support a single feature bitset. This is mainly an internal-only change, especially since we don't offer any globalfeatures. However, LND (as of next release) will offer global features, and also expect option_static_remotekey to be a *global* feature. So we send our (merged) feature bitset as both global and local in init, and fold those bitsets together when we get an init msg. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-11 04:52:04 +02:00
#define OPT_GOSSIP_QUERIES_EX 10
#define OPT_STATIC_REMOTEKEY 12
common/features: clean up feature handling for different cases. The spec is (RSN!) going to explicitly denote where each feature should be presented, so create that infrastructure. Incorporate the new proposed bolt11 features, which need this. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-11-23 01:19:23 +01:00
#define OPT_PAYMENT_SECRET 14
#define OPT_BASIC_MPP 16
common/features: add option_support_large_channel. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-02 06:09:47 +02:00
#define OPT_LARGE_CHANNELS 18
features: define option_anchor_outputs. As specified by https://github.com/lightningnetwork/lightning-rfc/pull/688. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-08-13 19:39:02 +02:00
#define OPT_ANCHOR_OUTPUTS 20
shutdown: don't allow shutdown to p2pkh or p2sh addresses for anchor outputs. This doesn't have an effect now (except in experimental mode), but it will when we support anchors. So we deprecate the use of those in the close command too. For experimental mode we have to avoid using p2pkh; adapt that test. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Deprecated: JSON-RPC: `shutdown` no longer allows p2pkh or p2sh addresses.
2022-03-31 11:10:50 +02:00
#define OPT_ANCHORS_ZERO_FEE_HTLC_TX 22
Makefile: update to latest BOLT text. In particular: - Bolt 4: add route blinding construction - Bolt 4: add blinded payments And this means it's not experimental, so we can turn it on by default! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: Protocol: blinded payments are now supported by default (not just with `--experimental-onion-messages`)
2023-04-07 08:55:33 +02:00
#define OPT_ROUTE_BLINDING 24
common: support opt_shutdown_anysegwit checks (EXPERIMENTAL_FEATURES). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-02-24 03:53:12 +01:00
#define OPT_SHUTDOWN_ANYSEGWIT 26
common/features: add channel_type definition, neaten header. Put all the normal spec-defined ones together. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-07-23 08:54:19 +02:00
#define OPT_CHANNEL_TYPE 44
bolt11: support payment_metadata. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-03-31 11:10:50 +02:00
#define OPT_PAYMENT_METADATA 48
splice: Move splice to experimental feature bit This was recommended by @t-bast: if the final spec commits to something compatible, we can simply advertize and accept both features, but if it does change in incompatible ways we won't cause problems for nodes who implement the official spec. (I split this, so first, we remove the OPT_SPLICE entirely, to make sure we caught them all. --RR) Suggested-by: @t-bast Changelog-None
2023-08-10 02:20:29 +02:00
/* BOLT-splice #9:
* | 62/63 | `option_splice` | ... IN ...
*/
common: restore OPT_SPLICE definition for the day it's ratified. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2023-08-10 02:20:38 +02:00
#define OPT_SPLICE 62
splice: Move splice to experimental feature bit This was recommended by @t-bast: if the final spec commits to something compatible, we can simply advertize and accept both features, but if it does change in incompatible ways we won't cause problems for nodes who implement the official spec. (I split this, so first, we remove the OPT_SPLICE entirely, to make sure we caught them all. --RR) Suggested-by: @t-bast Changelog-None
2023-08-10 02:20:29 +02:00
#define OPT_EXPERIMENTAL_SPLICE 162
common: support opt_shutdown_anysegwit checks (EXPERIMENTAL_FEATURES). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-02-24 03:53:12 +01:00
dual-funding: use correct feature bit number!! Use designated feature bit, instead of future-bit.
2021-03-12 01:21:21 +01:00
/* BOLT-f53ca2301232db780843e894f55d95d512f297f9 #9:
* | 28/29 | `option_dual_fund` | ... IN9 ...
experimental-dual-fund: add config level option for enabling dual-fund Allow a user to switch on dual-funding without needing to compile as EXPERIMENTAL_FEATURES. Doesn't work yet, since everything is still behind 'EXPERIMENTAL_FEATURES' compile time flags... but useful for testing
2020-12-10 01:10:17 +01:00
*/
dual-funding: use correct feature bit number!! Use designated feature bit, instead of future-bit.
2021-03-12 01:21:21 +01:00
#define OPT_DUAL_FUND 28
experimental-dual-fund: add config level option for enabling dual-fund Allow a user to switch on dual-funding without needing to compile as EXPERIMENTAL_FEATURES. Doesn't work yet, since everything is still behind 'EXPERIMENTAL_FEATURES' compile time flags... but useful for testing
2020-12-10 01:10:17 +01:00
bolt: Reflect the zeroconf featurebits in code
2022-04-14 14:35:39 +02:00
/* BOLT-519be05f61e2c35ddf95b731203f89b4ee0946c3 #9:
* | 46/47 | `option_scid_alias` | ... IN ...
* | 50/51 | `option_eroconf` | ... IN ...
*/
#define OPT_SCID_ALIAS 46
#define OPT_ZEROCONF 50
features: EXPERIMENTAL_FEATURES: advertize option_quiesce The latest draft has a feature bit here. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-10-08 01:31:04 +02:00
/* BOLT-quiescent #9:
* | 34/35 | `option_quiesce` | ... IN ...
*/
#define OPT_QUIESCE 34
doc: clean up offers bolt quotes As of 2b923a0367c5f9154fcec706e3302cc4658dd889. Recurrence quotes need to be marked separately, since they're no longer in offers main bolt. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-11-30 04:06:05 +01:00
/* BOLT-offers #9:
features: add EXPERIMENTAL option_onion_messages from draft. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-11 04:48:51 +02:00
*
features: don't announce onion_messages in bolt11 invoices. As noted by Joost. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-11-30 04:06:05 +01:00
* | 38/39 | `option_onion_messages` |... IN ...
features: add EXPERIMENTAL option_onion_messages from draft. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-04-11 04:48:51 +02:00
*/
features: renumber from 102/103 to 38/39. 100+ is for experimentation, modern spec practice is to assign feature bits sequentially as PRs get added, to avoid later renumbering. Still respect the old bit for now. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-07-02 02:11:30 +02:00
#define OPT_ONION_MESSAGES 38
Experimental option option_shutdown_wrong_funding: help me, I screwed up! It's not unheard of for people to give the wrong funding tx to us, getting their funds stuck. Interestingly, we can allow mutual close using a different txid and output number as long as they (solely) funded the channel, and the channel hasn't been used. This defines a "play area" feature to do just that. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-03-15 04:39:44 +01:00
#define OPT_SHUTDOWN_WRONG_FUNDING 104
features: make name of peer storage features match spec. And we should always represent them as is, not as optional: it's possible in future we could *require* "WANT_PEER_BACKUP_STORAGE". Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2023-02-04 06:48:24 +01:00
/* BOLT-peer-storage #9:
*
* | 40/41 | `want_peer_backup_storage` | Want to use other nodes to store encrypted backup data | IN ...
* | 42/43 | `provide_peer_backup_storage` | Can store other nodes' encrypted backup data | IN ...
*/
#define OPT_WANT_PEER_BACKUP_STORAGE 40
#define OPT_PROVIDE_PEER_BACKUP_STORAGE 42
features: Move feature-handling code to a common/features.c source.
2018-01-12 14:35:52 +01:00
#endif /* LIGHTNING_COMMON_FEATURES_H */
Reference in New Issue Copy Permalink