fryorcraken 25984c0b14

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.

2025-06-30 14:22:49 +10:00

..

dandelion.md

Update dandelion.md

2024-07-09 04:34:01 -04:00

device-pairing.md

Update device-pairing.md

2025-05-22 09:10:25 -04:00

noise-sessions.md

Update noise-sessions.md

2024-07-09 06:03:39 -04:00

noise.md

Update noise.md

2024-07-09 06:17:34 -04:00

p2p-reliability.md

docs: clarify that losses are possible message losses (#59)

2025-03-26 12:34:56 +00:00

rln-keystore.md

Create rln-keystore.md

2024-02-28 21:48:27 -05:00

tor-push.md

Update tor-push.md

2024-07-09 06:26:27 -04:00

waku-api.md

Remove shard relay subscription for init config

2025-06-30 14:22:49 +10:00