Dear SNS communities,
According to the SNS topics release plan, SNSs should categorize their existing, custom proposal types to topics. This will enable topic-based following for the SNS (as opposed to following on each individual proposal type) and improve user experience.
-
It’s possible to categorize custom proposal types either in one batch or in multiple batches; so, if there’s a controversial proposal type that an SNS community doesn’t know exactly how to categorize — no problem, we should first agree on the less controversial proposals / topics.
-
To identify which proposal types are still uncategorized, users can call
SnsGov.list_topics()and check what’s in theuncategorized_functionsfield of the response. -
It’s rather easy to submit the required proposal via DFX, the example command can be found here. E.g., the proposal action should be set to something like:
SetTopicsForCustomProposals = record { custom_function_id_to_topic = vec { record { 1001 : nat64; variant { ApplicationBusinessLogic }; }; record { 1002 : nat64; variant { DaoCommunitySettings }; }; }; }where
1001and1002are IDs of some existing custom proposals (a.k.a. generic nervous system functions). -
The SNS framework is soon expected to stop allowing custom proposals to be submitted without first setting the respective topics. The current ETA is March 24, 2025. Please inform us in this thread if this timeline does not work for your SNS for some reason.
