waku-org
/
waku-rust-bindings
mirror of https://github.com/waku-org/waku-rust-bindings.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
waku-rust-bindings/waku-sys
History
Daniel Sanchez 3593ff18e6
Expose local archive query method (#44) 
* Update vendor

* Expose local archive query
Update to beta4

* Update bindings package to beta4

* Update bindings package to beta4

* Make store response fields public

* Added store configuration

* Use decode response function
 		2023-02-15 10:57:39 +01:00
..
src Hide waku-sys binding warnings (#4) 2022-09-29 16:22:06 +02:00
vendor@11161b8919 Expose local archive query method (#44) 2023-02-15 10:57:39 +01:00
Cargo.toml Expose local archive query method (#44) 2023-02-15 10:57:39 +01:00
LICENSE-APACHEv2 Publish build (#22) 2022-11-28 17:57:20 +01:00
LICENSE-MIT Publish build (#22) 2022-11-28 17:57:20 +01:00
README.md Information prior to publishing (#21) 2022-11-28 10:18:42 +01:00
build.rs Run clippy --fix for updated lint requirements (#43) 2023-01-27 01:06:21 -08:00

README.md

Waku rust bindgen bindings

github crates.io docs.rs build status

Rust layer on top of go-waku c ffi bindings.

Usage

These are autogenerated, if you are looking for a proper Rust API version check on waku-bindings

Add this to your Cargo.toml:

[dependencies]
waku-sys = "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:

  1. Retrieving historical messages for mostly-offline devices.
  2. Adaptive nodes, allowing for heterogeneous nodes to contribute.
  3. 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