From 25984c0b142a3b284831e37e0f85cf7385e770ca Mon Sep 17 00:00:00 2001 From: fryorcraken Date: Mon, 30 Jun 2025 14:22:49 +1000 Subject: [PATCH] Remove shard relay subscription for init config Being able to set what shard to subscribe too when initialising a Waku node is a biased towards service nodes. Indeed, subscribing to shard should be done with the `subscribe` API (yet to be defined). Which can be used with a content topic, and pubsub topic (only if static sharding). A service node such as the `wakunode2` binary can still accept "shards to subscribe to" via CLI, but this is unrelated to the Waku node conf, and the `wakunode2` software should simply call `subscribe` when ready. --- standards/application/waku-api.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/standards/application/waku-api.md b/standards/application/waku-api.md index fa7b6fc..f9f3183 100644 --- a/standards/application/waku-api.md +++ b/standards/application/waku-api.md @@ -126,11 +126,6 @@ types: network_config: type: NetworkConfig default: TheWakuNetworkPreset - active_relay_shards: - type: array - constraints: mode == "relay" - default: [] - description: "The shards for relay to subscribe to and participate in." store_confirmation: type: bool default: false