Thanks, I’ve found it
- Self-deploy a DAO by reusing the publicly available SNS code and manually upgrade it. A developer or a community can choose to deploy the SNS code, which is open source, on a normal application subnet. They can then choose to follow the same SNS versions than system-provided SNSs follow or they can choose to deviate from this path. In this option, the DAO community has to be more active in implementing, testing and approving code versions.
I think this needs to be explicit in the documentation still (even though you could argue that it’s implicit). The distinction between ‘permissioned’ and ‘permissionless’ SNSs could actually be made more explicitly I think.
Is there any appetite for getting this back into the current SNS documentation?