How to manage an SNS
Audience: Once an SNS is launched, neither the dapp that the SNS controls, nor the SNS canisters are under the control of a singe entity such as a developer. This means that the dapp and to the SNS canisters, as well as which changes can be made to them, are controlled by the SNS community. Anyone with an SNS neuron can make a proposal to suggest a change in the dapp or to modify a parameter in the SNS governance and, if the majority agrees, the proposal is automatically executed on-chain. For this reason, the following pages are not only relevant for developers but for any member of an SNS community who would like to actively help managing the SNS.
On this page we will introduce a few aspects that are relevant for managing an SNS. As we complete more detailed pages for these different topics, we will link to them here.
As every piece of software, after an SNS is launched is has to be maintained. This includes ensuring that the SNS canisters are running the latest version and that they have enough cycles to continue operating. You can find more information on cycle management on this page.
While SNSs that are provided as a system function can only be upgraded to canister versions blessed by the NNS, each SNS community can configure their SNS according to their needs. Most chosen configurations can also be adjusted over time, for example to adopt to new situations or to experiment with different governance and tokenomic models. Therefore, managing an SNS also means that the community should regularly consider and adjust these configurations, which are defined by the SNS's nervous system parameters.