Make Waku Web Client relay spec compliant

[oskarth]

Problem

Currently browser/node impl are not spec compliant. Client should conform to spec: https://specs.vac.dev/specs/waku/v2/waku-v2.html

Details

1. Most immediately, messages should be wrapped in WakuMessage.
2. Currently there's a hack to overwrite GossipSub. This should inherit and be relay protocol.
3. There is probably something related to signing policy etc

Acceptance

Implementation is according to spec, at a minimum wrap with WakuMessage protobuf.

Further enhancement

Implement store and filter protocol.

[oskarth]

FYI: Barry @bgits is working on this, can't assign on GH though (pending invitation).

[oskarth]

Not sure if any progress is happening here. I started here https://github.com/vacp2p/waku-web-chat/blob/master/nodejs/src/chat.js#L75

[oskarth]

There's quite a bunch of dimensions here:

• (subscribe, publish)
• (nodejs, browser)
• nim-waku interop both ways
• wrapping request protocol on both waku web and chat2 side

So might have to cut this issue up a bit more / limit capabilities of this example.

For now it is under a flag.

[oskarth]

Follow up issues:

• NodeJS WakuMessage basic interop #6
• Browser WakuMessage basic interop #7

Might create more. I believe after these two are closed the minimal path for original issue is done, though it could definitely be enhanced.

[oskarth]

Minimal steps done. Leaving enhancements for later.