dd4d093945
examples/ is its own cargo workspace and only examples/basic is a member of the root one, so nothing built from the repo root ever compiled these two. They still used waku_new, set_event_callback, WakuEvent and the WakuNodeHandle typestate, none of which exist any more. Both collapse their App<State> typestate: the node no longer carries one, so neither can the app wrapping it. Event handling shrinks to a single add_on_received_message_listener -- the filter on content topic stays, but the enum match, the JSON parse and the panics on unexpected variants go, since a listener only receives what it registered for. Payloads are base64-decoded by the caller now. The store DTOs (StoreQueryRequest, StoreResponse, StoreWakuMessageResponse) come back as general/store.rs: they are plain serde shapes, and deleting node/store.rs took them out along with the FFI call they sat next to. toy-chat needs them to build the store query JSON and read the response. CI gains a check over examples/Cargo.toml. Without it these rot silently on the next API change, which is exactly how they got here. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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