go-waku/docs/operators
Jakub Sokołowski fcee52757e
ci: use wakuorg Docker Hub organization
We've been using `statusteam` Docker Hub org for a while now which was
never intended for public use, and we should be using `wakuorg` instead.

I've also updated references to `statusteam` in documentation and scripts.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-09-20 12:45:27 +02:00
..
how-to ci: use wakuorg Docker Hub organization 2023-09-20 12:45:27 +02:00
README.md chore: rename status-im/go-waku to waku-org/go-waku 2022-11-09 16:03:40 -04:00
quickstart.md ci: use wakuorg Docker Hub organization 2023-09-20 12:45:27 +02:00

README.md

The go-waku guide for operators

If you're eager to get started, check out our quickstart guide.

go-waku is a client implementation in Go of the Waku v2 family of protocols for peer-to-peer communication. The protocols are designed to be secure, privacy-preserving, censorship-resistant and able to run in resource restricted environments. Moreover, we've taken a modular approach so that node operators can choose which protocols they want to support based on their own motivations and availability of resources. We call this concept "adaptive nodes", implying that a Waku v2 network can consist of heterogeneous nodes contributing at different levels to the network.

This guide provides step-by-step tutorials covering how to build and configure your own go-waku node, connect to an existing Waku v2 network and use existing tools for monitoring and maintaining a running node.

Helpful resources

Getting in touch or reporting an issue

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.