logos-co
/
roadmap
mirror of https://github.com/logos-co/roadmap.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
roadmap/content/waku/collaboration/onboarding-guide.md

5.7 KiB
Raw Blame History

title tags date lastmod
Onboarding Guide
Waku
collaboration
2024-07-18 2024-07-18

Onboarding guide

Welcome to Waku! There’s quite a lot to learn so take your time. Here are a few links and some things to start with.

Vac & Waku

Vac is a wide team that builds public good protocols for the decentralized web - vac.

Waku originated as an incubation project within Vac with the goal of defining and implementing decentralized communication protocols. We have since evolved into a standalone team, while maintaining close collaboration with Vac, which continues to facilitate the RFC process - waku.

At Waku, each team member may split their working hours between research and sw development, depending on the team goals and personal interests.

Collaboration Guideline

Have a read at our Collaboration Guidelines to acquaint yourself with our collaboration best practices.

Starter tasks

  • Complete the BambooHR tasks (can be followed in parallel with other tasks.).

  • Try out the Status app

  • Get familiar with Nim. Recommendations:

  • Meet the Waku specification Waku is a communication layer for Web3. There are three main Waku-client implementations:

    • nwaku: Nim implementation aimed to be used by the infrastructure nodes.
    • go-waku: Golang implementation aimed to be used by the Desktop app.
    • js-waku: JavaScript implementation designed to be run by web browsers.

    Aside from the Waku project, Vac also gives a big contribution in the next ones:

    • Logos, a Blockchain protocol whose clients would be built in Nim and Rust - Logos.
    • Codex, a decentralized storage protocol (IPFS) - code-research, nim-codex.

  • Build nwaku. We encourage all core contributors to run a long-lived nwaku node as an operator. More details here. Useful resources:

  • Skim specs (primarily Vac, but also Status) and try to get a picture of how things fit together. You do not have to read all the specifications all at once (it may get a bit confusing). We suggest start reading them in the following order, it is just a suggestion, feel free to do it the way you want!:).

While reading RFCs note that there are two versions of WAKU namely WAKU1 and WAKU2. Vac RFCs related to WAKU2 are WAKU2 prefixed whereas other ones are prefixed by WAKU or WAKU1. For example, 8/WAKU-MAIL and 13/WAKU2-STORE are RFCs for WAKU1 and WAKU2, respectively. - 1/COSS - 10/WAKU2 - 16/WAKU2-RPC - 11/WAKU2-RELAY | 14/WAKU2-MESSAGE | 23/WAKU2-TOPICS | 26/WAKU2-PAYLOAD - 12/WAKU2-FILTER - 19/WAKU2-LIGHTPUSH - 13/WAKU2-STORE - 18/WAKU2-SWAP - 27/WAKU2-PEERS - 15/WAKU2-BRIDGE

  • Join the Vac, Waku, and Nimbus Discord servers and say hi!
  • Recommended: go through the list of existing open issues in the project repo (nwaku, go-waku or js-waku) you’ll mostly be working on and familiarise yourself with the current state of the project. This may take a while, but is an excellent exercise to get acquainted with some important conversations and project history. We encourage new contributors to ask questions in the comment sections of any past issues. You could even self-assign some issues that’s currently unassigned which you’d like to tackle! For this, the good-first-issue tag on Github may come in as a handy filter.

Resources

Vac

Status

Ecosystem