Waku node and protocol.
Go to file
Ivan Folgueira Bande 9e2d0860c9
Updating 'vendor/nim-json-rpc' to get fix for wrong header in rpc response (#1802)
2023-06-15 15:21:46 +02:00
.github chore(ci): extend and rename nightly workflow to support RC builds (#1784) 2023-06-08 17:13:40 +02:00
.sv4git/templates feat: add release-notes target (#1734) 2023-05-18 14:45:45 +02:00
apps chore(rln-relay): pass in the path to the tree db (#1782) 2023-06-08 17:22:21 +05:30
ci chore(makefile): unify where chronicles_log_level is set (#1748) 2023-05-23 10:44:57 +02:00
docs chore(ci): extend and rename nightly workflow to support RC builds (#1784) 2023-06-08 17:13:40 +02:00
examples feat(networking): integrate gossipsub scoring (#1769) 2023-06-06 19:28:47 +02:00
library refactor: proper use of setupNat (#1740) 2023-05-17 18:32:53 +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): buildscript bad cp (#1636) 2023-03-31 17:15:46 +05:30
tests fix(rln-relay): flaky static group manager test (#1798) 2023-06-14 20:55:33 +05:30
vendor Updating 'vendor/nim-json-rpc' to get fix for wrong header in rpc response (#1802) 2023-06-15 15:21:46 +02:00
waku chore(deps): bump libp2p & websock (#1800) 2023-06-15 13:17:19 +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 fix(rln-relay): keystore usage (#1750) 2023-05-22 22:06:55 +05:30
.gitmodules chore: removed unused submodule (#1580) 2023-02-28 10:35:20 +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 docs(changelog): release notes for v0.18.0 (#1791) 2023-06-13 22:48:53 +02:00
Dockerfile chore(makefile): unify where chronicles_log_level is set (#1748) 2023-05-23 10:44:57 +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(ci): properly set os and architecture for nightly and release (#1780) 2023-06-06 17:41:41 +02:00
README.md chore(docs): add docker-compose instructions (#1444) 2022-12-05 16:25:37 +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(docs): fix docs and mark some as deprecated (#1754) 2023-05-25 13:37:49 +02:00

README.md

nim-waku

Introduction

The nim-waku repository implements Waku v1 and v2, and provides tools related to it.

  • A Nim implementation of the Waku v1 protocol.
  • A Nim implementation of the Waku v2 protocol.
  • CLI applications wakunode and wakunode2 that allows you to run a Waku v1 or v2 node.
  • Examples of Waku v1 and v2 usage.
  • Various tests of above.

For more details on Waku v1 and v2, see their respective home folders:

How to Build & Run

These instructions are generic and apply to both Waku v1 and v2. For more detailed instructions, see Waku v1 and v2 home above.

Prerequisites

  • GNU Make, Bash and the usual POSIX utilities. Git 2.9.4 or newer.
  • Rust

More information on the installation of these 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 up to date.
make wakunode1 wakunode2

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

For more on how to run wakunode2, refer to:

Waku Protocol Test Suite

# Run all the Waku v1 and v2 tests
make test

Examples

Examples can be found in the examples folder. For Waku v2, there is 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 Vac Discord server.