logos-messaging-nim/library/kernel_api/protocols/lightpush_api.nim

proc lightpush_publish*(
    self: LogosDelivery, pubsubTopic: string, message: WakuMessage
): Future[Result[string, string]] {.ffi.} =
  ## Returns the published message hash.
  let hash = (await self.waku.lightpushPublish(PubsubTopic(pubsubTopic), message)).valueOr:
    return err(error)
  return ok(hash)
Migrate FFI to nim-ffi v0.2.0-rc.3 (typed procs, direct params) Rewrite the C FFI over the new per-layer APIs using nim-ffi v0.2.0 typed {.ffiCtor.}/{.ffiDtor.}/{.ffi.}/{.ffiEvent.} + CBOR, replacing the hand-written cstring/JSON bridge and the declare/lifecycle scaffolding. Final API shape from the start (no intermediate request wrappers): - every {.ffi.} proc takes its parameters directly; the macro bundles them into the per-proc CBOR request, so no `*Request` objects are needed - WakuMessage rides the wire directly (its fields are CBOR-serializable) - multi-parameter {.ffiEvent.} via the rc.3 envelope synthesis - events are fed by internal nim-broker listeners (no AppCallbacks) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-06-25 11:54:47 +02:00			`proc lightpush_publish*(`
			`self: LogosDelivery, pubsubTopic: string, message: WakuMessage`
			`): Future[Result[string, string]] {.ffi.} =`
			`## Returns the published message hash.`
			`let hash = (await self.waku.lightpushPublish(PubsubTopic(pubsubTopic), message)).valueOr:`
Reshape per-layer API into api/ folders and thin the FFI over them Each layer now separates its constructible core from its public surface: - core module (waku.nim / messaging_client.nim / reliable_channel_manager.nim): the type plus new/start/stop and the private construction helpers. - api/ folder: one module per differentiated set of operations (waku: topics/relay/filter/lightpush/store/peer_manager/discovery/ debug/health) plus an events surface. The waku api is reshaped to be the complete operation surface the C bindings need, so the library no longer reaches into node internals: relayPublish returns the message hash, relaySubscribe takes an optional handler, filter/lightpush auto-select the service peer, connectedPeersInfo returns structured data, pingPeer honours the timeout, plus relayNumPeersInMesh / relayNumConnectedPeers / isOnline. library/ is now a thin C-ABI shim: each {.ffi.} proc only marshals cstring/JSON/callbacks and delegates to ctx.myLib[].waku.<op> (or messagingClient.<op>). app_callbacks re-exports the modules defining its handler types, which the included FFI files previously relied on by leakage. Events move next to the surface that owns them, with each dependency kept pointing the right way: - waku/events/ relocated under waku/api/events/. - channel events live in channels/api/events.nim. - the four messaging-level message events move to messaging/api/events; MessageSeenEvent stays in waku because it is emitted by waku core, so moving it would make waku depend on the messaging layer. - delivery_events renamed to filter_subscribe_events to match the OnFilterSubscribe/Unsubscribe events it actually declares. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-06-25 00:40:02 +02:00			`return err(error)`
Migrate FFI to nim-ffi v0.2.0-rc.3 (typed procs, direct params) Rewrite the C FFI over the new per-layer APIs using nim-ffi v0.2.0 typed {.ffiCtor.}/{.ffiDtor.}/{.ffi.}/{.ffiEvent.} + CBOR, replacing the hand-written cstring/JSON bridge and the declare/lifecycle scaffolding. Final API shape from the start (no intermediate request wrappers): - every {.ffi.} proc takes its parameters directly; the macro bundles them into the per-proc CBOR request, so no `*Request` objects are needed - WakuMessage rides the wire directly (its fields are CBOR-serializable) - multi-parameter {.ffiEvent.} via the rc.3 envelope synthesis - events are fed by internal nim-broker listeners (no AppCallbacks) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-06-25 11:54:47 +02:00			`return ok(hash)`