Agenda Core dev call #36

[cammellos]

Monday September 24
12:00 UTC
Participate: https://meet.google.com/uyn-yfrq-uka?authuser=1&hs=122
View: https://www.youtube.com/channel/UCFzdJTUdzqyX4e9dOW7UpPQ/videos

Assign notetaker
Agenda setting (~5')
Announcements (~5')
Expected changes/proposals
a. waku async or sync updated
Review previous actions (~5') if available
Specs review > open PR's for Discussion (~10')
a. Organisation channels status-im/specs#151
b. ChatIdentity PR status-im/specs#150
AOB (~5')
YouTube:
Google Hangouts: https://meet.google.com/uyn-yfrq-uka?authuser=1&hs=122
Notes: https://notes.status.im/core-dev-call_36#

[cammellos]

@oskarth @decanus Would will you be able to give update/estimation on waku-2 timeline?
Thanks

[oskarth]

@decanus was supposed to join but won't be able to due to some personal events. 14:00 UTC is unfortunately too late for me. Here's an async update on Waku v2:

1) Current status

We are still focused on track 1 (https://vac.dev/waku-v2-plan) right now, i.e. basic libp2p integration. Last week had internal Nangang testnet, it does very little but it tests basics across network (https://github.com/status-im/nim-waku/blob/master/docs/tutorial/nangang.md). With this main spec moved to draft including relay spec (https://specs.vac.dev/specs/waku/waku-v2.html)

Store, Filter protocol are still WIP. Encryption spec still being considered - feedback/discussion welcome here: vacp2p/rfc#181

2) Re integration timelines

Early integration largely depends on resources for Stimbus (and Core/Desktop). From a spec/api POV this is ready. My understanding is that nim-waku v1 work is currently started but still experimental. Suggest course of action is for Stimbus to reach out in #waku when they are ready to look into nim-waku v2 integration. API basics are there and then we can work more iteratively.

3) Waku web

I got a basic PoC up and running here https://github.com/vacp2p/waku-web-chat/ - if someone has bandwidth to run with implementing it ping me or #waku for figuring out how to push this.

4) Misc updates

We got 1-2 hires joining beginning of October which will be a welcome addition.

More detailed write-up to come soon. Best place to ask specific questions or discuss things is #waku and/or specifics GHIs in github.com/vacp2p/specs/ and github.com/status-im/nim-waku/ repo (e.g.).

[oskarth]

According to agenda it is 1400 UTC but according to Status Calendar it is 1200 UTC. Which is it? If it is the latter, I'll try to phone in briefly, though I might be a bit late. I've also asked @kdeme if he is able to speak for Waku.

[cammellos]

@oskarth thanks for the update, the correct time is status calendar, no worries if you can't make it.

[Samyoul]

I'd like opinions on specs#150 - Introduction of ChatMessageIdentity, particularly any objections to the implementation of the display_name field.

Note for example of differentiation between ENS and display names see Maciej's sample https://github.com/status-im/status-react/issues/11047#issuecomment-675915787