Positioning: RLNP2P

[oskarth]

(Discussed during PM call)

Problem

Currently RLN and RLN-Relay are kind of treated as one thing in terms of positioning. Additionally, we see a lot of potential usage of RLN and RLN in a p2p setting outside of Waku Relay only. E.g. Dandellion, GossipSub, Tor, Cell Phone tower... etc.

It is desirable to make this distinction more clear, as well as distinction with RLN on its own. Both for ourselves but also for other projects who aren't familiar with details of RLN, Waku, RLNP2P etc.

Additionally, RLNP2P can be seen as its own product bet, similar to how how Waku was spawned out of Vac Research.

Details

(Can be broken out into separate issues)

• Spec change RLN-RELAY to RLNP2P being main spec, similar to how Dandellion and Waku interacts
• Super basic site up e.g. rlnp2p.vac.dev - can just be a few bullet points and links
  - [ ] Ping AppliedZK ppl about this to get link on their site too
• Update references in relevant places
  • don't need everywhere, just "live" places, and can just add a two sentence prelude about clarification
  • tracks e.g.
• Disseminate link in e.g. upstream GHI (libp2p), Twitter, vac.dev project site update
• Start of/WIP of separating out into own library
  - can happen concurrently/after - but repo with README should exist before

Probably missing a few things, but I think this is a start. If we keep each item minimal basics should be doable within ~1w or so. Then it can be expanded from there.

Acceptance criteria

Reposition RLNRelay to RLN-P2P in all relevant places, see details above.

[oskarth]

cc @staheri14 @rymnc

[oskarth]

Can possibly be a milestone too

[staheri14]

FYI: There was already a tracking issue #110, would be great to merge them and only track from one place.

[oskarth]

Reposition RLNRelay to RLN-P2P in all relevant places, see details above.

This issue is different in scope from previously cut one, but can link/supersede as appropriate

[amirhouieh]

RLNP2P is going to be a fully standalone product (similar to Waku) but not fully developed or as mature probably and therefore we need to manifest it within the Vac website without detaching it from the Vac context. (correct me if i am wrong). in this case, I can think of two approaches;

1. Create a subdirectory including a couple of MD files inside the vac.dev repo. This would be then listed on the sidebar in a similar fashion as "research" section.

2. Create one MD file and include all relevant information inside that file.

[AtHeartEngineer]

👋 Hey we are working on a p2p chat using RLN, https://github.com/kayleegeorge/zk-chat is the repo, https://hackmd.io/dX1qoy6cTtSXJ7TdB8muIw?both is our rough plan. We are planning on building a library using Waku with Gossipsub over WebRTC/WebSockets for use in the browser, and then building a browser extension on top of that.

Just talked to @staheri14 some about this and wanted to start a communication effort in this area.

CC: @kayleegeorge

[oskarth]

@AtHeartEngineer Nice! This sounds exactly what @fryorcraken and @richard-ramos et al has done with RLN in Waku in the browser, with nodes validating on nwaku/go-waku.

A bit off-topic for OP, but probably worth linking up with @fryorcraken if you guys haven't already? Using e.g. https://github.com/waku-org/js-waku-examples/blob/master/rln-js/index.html and https://github.com/status-im/nwaku/blob/master/docs/tutorial/rln-chat-cross-client.md as a starting point seems like it'd make a lot of sense

[oskarth]

Put up a very basic first cut of site just to have something up: https://rlnp2p.vac.dev/

It definitely needs to be improved wrt to content, structure etc, but this is the minimally useful thing for workshop. Was easier to just do first cut myself.

I suggest further enhancements can be made as PRs in github.com/vacp2p/rlnp2p repo

[rymnc]

As discussed with @oskarth, the next two issues to be tackled are in this order of priority -

• Spec change RLN-RELAY to RLNP2P being main spec, similar to how Dandellion and Waku interacts
• Start of/WIP of separating out into own library