logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-04 07:03:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove shard relay subscription for init config

Browse Source 
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.
This commit is contained in:
fryorcraken 2025-06-30 14:22:49 +10:00
parent 95ebcd9ea0
commit 25984c0b14
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
1 changed files with 0 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
standards/application/waku-api.md
View File

@ -126,11 +126,6 @@ types:
network_config: network_config:
type: NetworkConfig type: NetworkConfig
default: TheWakuNetworkPreset default: TheWakuNetworkPreset
active_relay_shards:
type: array<uint>
constraints: mode == "relay"
default: []
description: "The shards for relay to subscribe to and participate in."
store_confirmation: store_confirmation:
type: bool type: bool
default: false default: false