Waku node and protocol.
Go to file
NagyZoltanPeter 563b2b20a5
chore: move SubscriptionManager under waku_core (#2025)
* chore: cherry-pick from Filter V2 RestApi PR: move FilterPushHandler and SubscriptionManager from Filter V1 to under waku_core
2023-09-12 17:08:40 +02:00
.github chore(ci): add js-waku test to pre-release workflow (#2017) 2023-09-11 16:16:53 +02:00
.sv4git/templates feat: add release-notes target (#1734) 2023-05-18 14:45:45 +02:00
apps feat(rln-relay): removed rln from experimental 🚀 (#2001) 2023-09-11 12:02:31 +05:30
ci feat(rln-relay): removed rln from experimental 🚀 (#2001) 2023-09-11 12:02:31 +05:30
docker/binaries Add utils to Dockerfile (#1991) 2023-09-05 15:50:54 +02:00
docs feat(rln-relay): removed rln from experimental 🚀 (#2001) 2023-09-11 12:02:31 +05:30
examples chore(cbindings): Thread-safe libwaku. WakuNode instance created directly from the Waku Thread (#1957) 2023-09-01 08:37:02 +02:00
library chore(cbindings): Thread-safe libwaku. WakuNode instance created directly from the Waku Thread (#1957) 2023-09-01 08:37:02 +02: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 fix(rln-relay): bump zerokit to v0.3.2 (#1951) 2023-08-25 13:44:57 +05:30
tests fix: prevent IP 0.0.0.0 from being published and update peers with empty ENR data (#1982) 2023-09-11 11:30:12 +03:00
tools chore(rln-relay): updated docs (#1993) 2023-09-11 11:10:41 +05:30
vendor fix(rln-relay): bump zerokit to v0.3.2 (#1951) 2023-08-25 13:44:57 +05:30
waku chore: move SubscriptionManager under waku_core (#2025) 2023-09-12 17:08:40 +02: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 fix(rln-relay): bump zerokit to v0.3.2 (#1951) 2023-08-25 13:44:57 +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 feat(rln-relay): removed rln from experimental 🚀 (#2001) 2023-09-11 12:02:31 +05:30
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-relay): removed rln from experimental 🚀 (#2001) 2023-09-11 12:02:31 +05:30
README.md docs(README): List possible WSL Issue (#1995) 2023-09-11 18:06:19 +02: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_db_inspector): create rln_db_inspector tool (#1999) 2023-09-07 18:15:25 +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:

Issues

WSL

If you encounter difficulties building the project on WSL, consider placing the project within WSL's filesystem, avoiding the /mnt/ directory.

Developing

Nim Runtime

This repository is bundled with a Nim runtime that includes the necessary dependencies for the project.

Before you can utilise the runtime you'll need to build the project, as detailed in a previous section. This will generate a vendor directory containing various dependencies, including the nimbus-build-system which has the bundled nim runtime.

After successfully building the project, you may bring the bundled runtime into scope by running:

source env.sh

If everything went well, your should see your prompt suffixed with [Nimbus env]$. Now you can run nim commands as usual.

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.