Waku node and protocol.
Go to file
gabrielmer 01050138c6
fix: only set disconnect time on left event (#2831)
2024-06-24 10:20:09 +02:00
.github feat(rlnv2): clean fork of rlnv2 (#2828) 2024-06-20 11:35:21 +02:00
.sv4git/templates feat: add release-notes target (#1734) 2023-05-18 14:45:45 +02:00
apps feat(rlnv2): clean fork of rlnv2 (#2828) 2024-06-20 11:35:21 +02:00
ci fix(ci): use --tags to match non-annotated tags (#2814) 2024-06-19 17:54:19 +02:00
docker/binaries Add utils to Dockerfile (#1991) 2023-09-05 15:50:54 +02:00
docs release-process.md: add step to merge the release branch back to master (#2734) 2024-05-29 10:09:35 +02:00
examples chore: android support (#2554) 2024-05-21 21:00:22 -04:00
library fix: use `when` instead of `if` for adding soname on linux (#2721) 2024-05-23 10:05:53 -04:00
metrics chore: switch wakuv2 to waku fleet (#2519) 2024-03-20 16:28:00 +01:00
migrations add new index to optimize the order by storedAt (#2778) 2024-06-06 11:38:58 +02:00
scripts feat(rlnv2): clean fork of rlnv2 (#2828) 2024-06-20 11:35:21 +02:00
tests chore: better descriptive log (#2826) 2024-06-20 18:38:55 +05:30
tools feat(rlnv2): clean fork of rlnv2 (#2828) 2024-06-20 11:35:21 +02:00
vendor chore(zerokit): bump submodule (#2830) 2024-06-20 14:46:16 +02:00
waku fix: only set disconnect time on left event (#2831) 2024-06-24 10:20:09 +02:00
.dockerignore fix(dockerfile): update dockerignore and base image (#2262) 2023-12-01 11:35:50 +01:00
.editorconfig chore: add editorconfig file 2022-11-21 09:31:03 +01:00
.gitignore chore: android support (#2554) 2024-05-21 21:00:22 -04:00
.gitmodules feat(rlnv2): clean fork of rlnv2 (#2828) 2024-06-20 11:35:21 +02:00
.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: merging release v0.29 into master (#2802) 2024-06-20 09:39:28 +02:00
Dockerfile chore: add ARM64 support for Linux/MacOS (#2580) 2024-04-12 14:11:35 +08: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(rlnv2): clean fork of rlnv2 (#2828) 2024-06-20 11:35:21 +02:00
README.md chore: adding NIMFLAGS usage to readme (#2469) 2024-02-23 16:25:13 +02:00
config.nims chore: android support (#2554) 2024-05-21 21:00:22 -04: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 chore: android support (#2554) 2024-05-21 21:00:22 -04:00

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

# Build with custom compilation flags. Do not use NIM_PARAMS unless you know what you are doing.
# Replace with your own flags
make wakunode2 NIMFLAGS="-d:chronicles_colors:none -d:disableMarchNative"

# Run with DNS bootstrapping
./build/wakunode2 --dns-discovery --dns-discovery-url=DNS_BOOTSTRAP_NODE_URL

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

To join the network, you need to know the address of at least one bootstrap node. Please refer to the Waku README for more information.

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, you 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.

Docs