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 api on top of waku-sys bindgen bindings to c ffi bindings.
Usage
Add this to your Cargo.toml:
[dependencies]
waku-bindings = "0.1.0"
About Waku
Waku is the communication layer for Web3. Decentralized communication that scales.
Private. Secure. Runs anywhere.
What is Waku?
Waku is a suite of privacy-preserving, peer-to-peer messaging protocols.
Waku removes centralized third parties from messaging, enabling private, secure, censorship-free communication with no single point of failure.
Waku provides privacy-preserving capabilities, such as sender anonymity,metadata protection and unlinkability to personally identifiable information.
Waku is designed for generalized messaging, enabling human-to-human, machine-to-machine or hybrid communication.
Waku runs everywhere: desktop, server, including resource-restricted devices, such as mobile devices and browsers. How does it work?
The first version of Waku had its origins in the Whisper protocol, with optimizations for scalability and usability. Waku v2 is a complete rewrite. Its relay protocol implements pub/sub over libp2p, and also introduces additional capabilities:
- Retrieving historical messages for mostly-offline devices.
- Adaptive nodes, allowing for heterogeneous nodes to contribute.
- Bandwidth preservation for light nodes.
This makes it ideal for running a p2p protocol on mobile, or in other similarly resource-restricted environments.
Read the Waku docs