Ivan FB 0590b2bf68

messaging: route api send/subscription through the Waku kernel ...

The messaging api layer reached around the Waku kernel into the libp2p
node (`waku.node.subscriptionManager`, `waku.node.rng`,
`waku.node.brokerCtx`). That breaks the declared layering: messaging
depends on the Waku *kernel* abstraction, not the raw node.

Add a content-topic subscription api on the Waku layer
(`waku/api/subscriptions.nim`) and switch the messaging send/subscription
paths onto it, plus the kernel's own `rng`/`brokerCtx` fields, so the
layer no longer touches `node` internals.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-26 13:40:40 +02:00

..

api

Move events back into interface-class source files (restore #3975 placement)

2026-06-25 23:07:13 +02:00

channels

adjust nph

2026-06-26 12:43:31 +02:00

messaging

messaging: route api send/subscription through the Waku kernel

2026-06-26 13:40:40 +02:00

waku

messaging: route api send/subscription through the Waku kernel

2026-06-26 13:40:40 +02:00

logos_delivery.nim

messaging: route api send/subscription through the Waku kernel

2026-06-26 13:40:40 +02:00