Status: early drafting

Goal

Have a digital garden which is easy to maintain, quick to find a spec and easily reach to the mainstream stakeholders, includes but not limited to Waku researchers, developers, and general users.

With a spec first design, it will help the long term adoption of Waku, spec first means,

• stakeholders care about the user case enough, and discuss it widely.
• stakeholders know where to find the existing specs, and not missed and confused.
  • the current implementation of each spec (raw, draft, stable) should be clear to stakeholders
  • the importance of the spec to the overall Waku ecosystem should be clear to stakeholders (optional, recommended practice vs core specs)
• stakeholders feels motivated and welcomed to propose a new idea or spec.
• specs are maintained in an open and efficient way.

Status Quo

Waku specification lives in Vac RFC.

Research happens in Github issues of waku-org/research.

What’s the Problem?

• a developer needs to learn about Vac even Logos before dig into Waku spec.
• Vac RFC includes spec not related to Waku, which could be confusing for beginners.
• Research activity is not involving Waku community enough, which could lead to a spec/protocol not used or forked.
• Waku specs are divided into v1 and v2, which makes maintenance a burden.

Proposed Solution

• a centralized places for all the Waku (decentralized messaging) related specs, could be a new repo named waku-org/wips.