Waku v2 - Dingpu testnet

[oskarth]

Follows on Nangang testnet (#43) but with slightly more capabilities.

Scope

In addition to Nangang:

1. Store and filter usage
2. Specs: store and filter in draft
3. Second client: basic Waku Web support
4. Interface: basic chat-style interface

Stretch goals

5. Closer towards bridge: run node with Waku v1 and v2 together
6. Companion spec with legacy/existing for encryption Provide optional encryption & signing scheme for Waku v2 or not? rfc#181 Allow versioned payload spec rfc#194

Where does the name from?

頂埔站 Dingpu metro station in Taipei https://en.wikipedia.org/wiki/Dingpu_metro_station

Acceptance criteria

1. All devs can use basic chat interface example to talk to each other
2. This includes storeclient for basic history view
3. Ditto for filter
4. Can interface using Waku Web (e.g. Node or possibly browser, might be hacky)
5. Store and filter specs marked as draft

Stretch:
5. Run node with v1 and v2 both running
6. Use envelope data field spec for inside of message as PoC

Tasks

(Not a complete list yet)

General

• End to end interface Waku v2: Create basic example chat waku-org/nwaku#177
• Waku Web spec compliant Make Waku Web Client relay spec compliant waku-web-chat#1
• Content topic compatible for bridge Waku v2 contentTopic type rfc#180
• Allow versioned payload spec rfc#194

Store and filter

• integrate store to chat example Integrate store protocol into chat2 example waku-org/nwaku#196
• deploy cluster node Deploy and ensure cluster node support store and filter server role waku-org/nwaku#198
• store spec draft Get store protocol to draft state rfc#200
• filter spec draft Get filter protocol to draft state rfc#201

Stretch goals

• Two nodes in one Run Waku v1 and v2 in same process (pre-req for bridge) waku-org/nwaku#188
• Companion spec Provide optional encryption & signing scheme for Waku v2 or not? rfc#181

---

• integrate filter to chat example Integrate filter protocol into chat2 example waku-org/nwaku#197 (out of scope)

• Use encrypted payload from waku envelope spec Waku Message support version 1 (v1 waku envelope data format) for encrypted payload waku-org/nwaku#192 (out of socpe for now)

[oskarth]

Update: vacp2p/rfc#194 and vacp2p/rfc#181 addressed.

Implementation issues created in nim-waku: waku-org/nwaku#191 and waku-org/nwaku#192

Strictly speaking the former isn't a must (protobuf defaults to 0) but it helps to make it explicit. The second is part of the stretch goal.

[oskarth]

End to end interface implemented #48

[oskarth]

Updated issue and board with store and filter todos. As you can see it is quite a lot. @decanus

[oskarth]

Brief update: main blocker waku-org/nwaku#215 was addressed.

@decanus is working on vacp2p/rfc#180

I started working on vacp2p/waku-web-chat#1 issue.

Any luck with the two nodes in one or including v1 encrypted payload @kdeme? Would be nice to have these as part of the testnet

[oskarth]

Waku web spec compliant (though not very stable but eh)

[oskarth]

Update: above addressed.

Also adding vacp2p/rfc#222 to scope to get all specs to draft status.

Removing encrypted payload from scope (stretch goal initially).

[oskarth]

As soon as waku-org/nwaku#228 is merged we can close this

[oskarth]

Done!