b48946a64a
The `rln` dependency exists only to force RLN symbols into the link, but it had drifted two majors from the library it is meant to mirror: the vendor pins `LIBRLN_VERSION := v2.0.2` and build.rs links that `librln_v2.0.2.a`, while this crate still asked for 0.3.4. That drift was invisible in isolation and fatal downstream. Every rln up to 0.6.1 pins `serde = "=1.0.163"` exactly, so any consumer resolving waku-bindings alongside a crate needing a newer serde -- openmls' tls_codec wants ^1.0.184 -- fails to resolve at all, since cargo will not duplicate serde 1.x. libchat cannot depend on this crate without it. 2.0.2 relaxes the pin to ^1.0.228 and matches what is linked. Verified by building and linking libchat against it: no duplicate-symbol clash with the vendor's archive. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ai43sF2rymPFMG9iki9fwL
Waku Rust bindings
Rust layer on top of logos-messaging-nim C FFI bindings.
Using the crate
For now this crate is consumed from a local checkout rather than a registry.
-
Clone the repo and check out the branch you want:
git clone --recurse-submodules https://github.com/logos-messaging/logos-delivery-rust-bindings cd logos-delivery-rust-bindings git checkout <branch> git submodule update --init --recursive -
Point your app at it by path:
# your app's Cargo.toml [dependencies] waku-bindings = { path = "../logos-delivery-rust-bindings/waku-bindings" }
Build prerequisites
waku-bindings builds the underlying Nim library from source the first time,
so the toolchain has to be present:
- Nim and nimble (installed by the vendored
maketargets, or bring your own onPATH) - make and a C/C++ toolchain
- A Rust toolchain (RLN is built from source)
The first build compiles the whole logos-delivery tree and is slow; subsequent builds are incremental.
What you can call
Everything is driven through LogosDeliveryCtx (re-exported at the crate root).
The crate docs group the available operations — node lifecycle, messaging,
reliable channels, and the typed event listeners — under Operations; run
cargo doc --open -p waku-bindings for the full, linked method list. A minimal
end-to-end example lives in examples/basic.
About Waku
Waku is a family of robust and censorship-resistant communication protocols enabling privacy-focused messaging for Web3 applications.
Private. Secure. Runs anywhere.
Read the Waku docs