The issue is that the key is used for gossipsub validation. Meaning you’d have to first propagate the new key, but not use it.
Then everyone will need to start using the new key at the same time to not split the gossipsub network.
- What about fleet nodes and other Waku nodes deployed to support the community? You’d need to add some API there to allow community owner to tell them new key
- What nodes which are offlines? they would need to do store queries before they can enable relay
Not impossible but hard.
I think this can be challenged, how often do you stare at the member list?
Yes noted, I think we would need to be able to infer this from somewhere (eg smart contract) in any case.
You’re unlikely to need a @mentions if you have never seen the user online. You would only need to see a user once to get their details via store.
Thanks for the information. All to be taken in account here. It helps.
Great to hear. I didn’t know. Thanks for that.
Why is that an issue? Because of the following?:
Yes indeed, we need to find a balance.
In summary, thank you for the insight. It helps understand the possible directions and risks.