Waku node and protocol.
Go to file
Simon-Pierre Vivier c369b3294e
feat: topic subscriptions updates discv5 ENR (#1875)
2023-08-23 09:53:17 -04:00
.github chore(ci): add a job checking config options and db schema (#1927) 2023-08-23 09:33:11 +02:00
.sv4git/templates feat: add release-notes target (#1734) 2023-05-18 14:45:45 +02:00
apps feat: topic subscriptions updates discv5 ENR (#1875) 2023-08-23 09:53:17 -04:00
ci chore: remove references to v2 (#1898) 2023-08-09 18:11:50 +01:00
docker/binaries feat(ci): add docker image builds per PR (#1881) 2023-08-09 13:13:37 +02:00
docs fix(rln-relay): remove registration capability (#1916) 2023-08-22 11:49:18 +05:30
examples chore: remove references to v2 (#1898) 2023-08-09 18:11:50 +01:00
library chore: remove references to v2 (#1898) 2023-08-09 18:11:50 +01:00
metrics chore(rln-relay): update metrics dashboard (#1745) 2023-05-19 16:24:53 +05:30
migrations chore(migrations): move migration scripts to project root 2022-11-03 17:58:05 +01:00
scripts chore(submodules): use zerokit v0.3.1 only (#1886) 2023-08-09 20:21:06 +05:30
tests feat: topic subscriptions updates discv5 ENR (#1875) 2023-08-23 09:53:17 -04:00
tools/rln_keystore_generator feat(rln_keystore_generator): wired to onchain group manager (#1931) 2023-08-23 18:20:40 +05:30
vendor chore(submodules): use zerokit v0.3.1 only (#1886) 2023-08-09 20:21:06 +05:30
waku feat: topic subscriptions updates discv5 ENR (#1875) 2023-08-23 09:53:17 -04:00
.dockerignore add a Dockerfile for creating nim-waku images 2020-05-27 12:51:20 +02:00
.editorconfig chore: add editorconfig file 2022-11-21 09:31:03 +01:00
.gitignore feat: Rest API interface for legacy (v1) filter service. (#1851) 2023-08-04 11:34:22 +02:00
.gitmodules chore(submodules): use zerokit v0.3.1 only (#1886) 2023-08-09 20:21:06 +05:30
.sv4git.yml chore(ci): extend and rename nightly workflow to support RC builds (#1784) 2023-06-08 17:13:40 +02:00
CHANGELOG.md chore(release): update changelog for delayed v0.19.0 release (#1911) 2023-08-16 14:44:33 +02:00
Dockerfile chore: remove references to v2 (#1898) 2023-08-09 18:11:50 +01:00
LICENSE-APACHEv2 Fix name in licence (#517) 2021-04-28 20:00:45 +10:00
LICENSE-MIT Fix name in licence (#517) 2021-04-28 20:00:45 +10:00
Makefile feat(rln_keystore_generator): wired to onchain group manager (#1931) 2023-08-23 18:20:40 +05:30
README.md chore: remove Waku v1 and wakubridge code (#1874) 2023-08-07 15:11:46 +01:00
config.nims chore(ci): properly set os and architecture for nightly and release (#1780) 2023-06-06 17:41:41 +02:00
env.sh Set up repo to make use of nimbus-build-system 2020-05-01 11:29:16 +02:00
shell.nix feat(store): simplify wakunode2 configuration options 2022-10-26 17:10:30 +02:00
waku.nimble feat(rln): init rln_keystore_generator (#1925) 2023-08-22 19:53:05 +05:30

README.md

Nwaku

Introduction

The nwaku repository implements Waku, and provides tools related to it.

  • A Nim implementation of the Waku (v2) protocol.
  • CLI application wakunode2 that allows you to run a Waku node.
  • Examples of Waku usage.
  • Various tests of above.

For more details see the source code

How to Build & Run

These instructions are generic. For more detailed instructions, see the Waku source code above.

Prerequisites

The standard developer tools, including a C compiler, GNU Make, Bash, and Git. More information on these installations can be found here.

Wakunode

# The first `make` invocation will update all Git submodules.
# You'll run `make update` after each `git pull` in the future to keep those submodules updated.
make wakunode2

# See available command line options
./build/wakunode2 --help

For more on how to run wakunode2, refer to:

Waku Protocol Test Suite

# Run all the Waku tests
make test

Examples

Examples can be found in the examples folder. This includes a fully featured chat example.

Tools

Different tools and their corresponding how-to guides can be found in the tools folder.

Bugs, Questions & Features

For an inquiry, or if you would like to propose new features, feel free to open a general issue.

For bug reports, please tag your issue with the bug label.

If you believe the reported issue requires critical attention, please use the critical label to assist with triaging.

To get help, or participate in the conversation, join the Waku Discord server.