Waku node and protocol.
Go to file
gabrielmer 43e040e0a9
chore(release): update changelog for v0.21.3 release (#2208)
2023-11-09 16:10:09 +02:00
.github chore: remove js-node tests as release candidate dependencies (#2123) 2023-10-13 11:45:18 +03:00
.sv4git/templates feat: add release-notes target (#1734) 2023-05-18 14:45:45 +02:00
apps feat: rln-keystore-generator is now a subcommand (#2189) 2023-11-09 12:52:08 +02:00
ci fix(ci): fix name of discord notify method 2023-09-27 18:43:52 +02:00
docker/binaries Add utils to Dockerfile (#1991) 2023-09-05 15:50:54 +02:00
docs chore: added size based retention policy (#2098) 2023-10-10 15:29:09 +05:30
examples chore(cbindings): Adding cpp example that integrates the 'libwaku' (#2079) 2023-09-28 11:10:42 +02:00
library chore(cbindings): Adding cpp example that integrates the 'libwaku' (#2079) 2023-09-28 11:10:42 +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 feat(coverage): Add simple coverage (#2067) 2023-09-27 15:53:23 +02:00
tests feat: rln-keystore-generator is now a subcommand (#2189) 2023-11-09 12:52:08 +02:00
tools feat: rln-keystore-generator is now a subcommand (#2189) 2023-11-09 12:52:08 +02:00
vendor chore: bumping nim-libp2p to include WSS fix (#2150) 2023-10-25 11:04:41 +03:00
waku fix(rest): fix bug in rest api when sending rln message (#2169) 2023-10-30 17:58:56 +02:00
.dockerignore
.editorconfig chore: add editorconfig file 2022-11-21 09:31:03 +01:00
.gitignore feat(coverage): Add simple coverage (#2067) 2023-09-27 15:53:23 +02:00
.gitmodules Bumping vendor/nim-stew. Adding vendor/nim-results (#2055) 2023-09-20 17:46:27 +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(release): update changelog for v0.21.3 release (#2208) 2023-11-09 16:10:09 +02:00
Dockerfile ci: add jq, fix RLN build script to not use rustup 2023-09-19 16:20:06 +02: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 chore(cbindings): Adding cpp example that integrates the 'libwaku' (#2079) 2023-09-28 11:10:42 +02:00
README.md docs: Clarify running instructions (#2038) 2023-10-05 15:04:57 +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
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

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