Current status: draft

Background

https://forum.vac.dev/t/optimizing-community-description/339

The root problem

The community metadata is frequently changed by most events happened in a Status community, and broadcast in the Waku relay network. The message size is a few megabytes for a regular community, source.

Overview

This doc lists the steps to improve community metadata to reduce the overall bandwidth consumption from users’ devices.

Related Code in Status-go

Message Type: ApplicationMetadataMessage_COMMUNITY_DESCRIPTION

Pubsub Topic: Use global shard (waku/2/rs/32) if not customized, otherwise use community self assigned shard.

How to assign a custom shard for a community?

TBD

Main Business Logic

handleCommunitiesSubscription: handles the events in a community

publishOrg: the method to send the message.

communityAdvertiseIntervalSecond: interval of control node regular publish

List The Events

What are the events that trigger the community description?