Waku node and protocol.
Go to file
Ivan Folgueira Bande 4650f8f161
Dockerfile workaround
2024-04-05 16:39:55 +02:00
.github chore: creating prepare_release template (#2225) 2023-11-30 10:29:26 +01:00
.sv4git/templates feat: add release-notes target (#1734) 2023-05-18 14:45:45 +02:00
apps chore: message.nim - set max message size to 150KiB according to spec (#2298) 2024-01-03 13:11:50 +01:00
ci feat: setting image deployment to harbor registry 2023-11-29 11:54:17 +01:00
docker/binaries Add utils to Dockerfile (#1991) 2023-09-05 15:50:54 +02:00
docs docs: update after release steps (#2336) 2024-01-08 08:11:06 -05:00
examples fix: Set `record` to the Waku Node Builder in the examples as it is required (#2328) 2024-01-05 10:00:41 +01:00
library libwaku: avoid using waku_init. Only use waku_new to create node and context (#2282) 2023-12-15 13:32:12 +01:00
metrics chore(rln-relay): update metrics dashboard (#1745) 2023-05-19 16:24:53 +05:30
migrations feat: Add new DB column `messageHash` (#2202) 2023-11-22 17:32:56 +01:00
scripts feat(coverage): Add simple coverage (#2067) 2023-09-27 15:53:23 +02:00
tests feat: adding filter data admin endpoint (REST) (#2314) 2024-01-09 11:42:29 +01:00
tools chore: vendor bump for 0.23.0 (#2274) 2023-12-14 07:16:39 +01:00
vendor update nim-libp2p vendor 2024-04-05 12:35:14 +02:00
waku Give more msg_hash log detail 2024-04-05 12:35:07 +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 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: update CHANGELOG.md for v0.24.0 2024-01-12 07:33:00 -05:00
Dockerfile Dockerfile workaround 2024-04-05 16:39:55 +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: update docs for rln-keystore-generator (#2210) 2023-11-21 16:43:15 +03:00
README.md chore: fix typos (#2239) 2023-11-30 11:08:08 +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 chore: update docs for rln-keystore-generator (#2210) 2023-11-21 16:43:15 +03: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

# 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