SNS DAOs and the decentralization swap

A project launches its SNS through a decentralization swap. The project proposes the launch to the NNS, and if the proposal passes the network creates the SNS canisters and opens a swap in which participants exchange ICP for the new SNS token. The documentation describes the swap as having a minimum and a maximum participation target, and a duration.

The outcome depends on how the swap fills. If participation reaches the maximum, the swap succeeds and the excess is returned. If it reaches at least the minimum but not the maximum, the swap succeeds at the level reached. If it does not reach the minimum, the swap fails and participants' ICP is returned. The documentation is explicit that a failed swap leaves the project's canisters under the control of the original developer, because the SNS was never created.

The swap is not a public offering in the regulatory sense and the documentation does not present it as one. It is a mechanism for distributing governance tokens to a community in exchange for the ICP that funds the SNS's treasury and its cycles. What the token confers is voting power over the dapp, not a claim on revenue.

Once the SNS is running, its governance mirrors the NNS in structure. Token holders stake into neurons, neurons vote on proposals, and voting power depends on the stake and the dissolve delay. The documentation describes the same follow mechanism, so a holder can delegate their vote on a topic to a neuron they trust. The proposal types are the ones the dapp needs: upgrading its canisters, changing its settings, spending its treasury, and adjusting its own governance.

The documentation describes a versioning mechanism that lets the SNS advance its own framework version automatically when the NNS approves a new one, subject to a setting the community controls. That is how an SNS keeps up with improvements to the governance system without a manual migration for every release.

The honest caveat is that governance is only as meaningful as the distribution of the token. A swap that concentrates the token in a few hands produces a governance system that a few hands control, and the mechanism does not prevent that. The documentation describes the tool; it does not claim the outcome.

The relationship is one of creation and oversight rather than control. The NNS approves the launch and creates the SNS canisters, and the SNS then governs the dapp independently. The documentation describes the SNS as owning the dapp's canisters, with the NNS no longer able to control them directly. That separation is what makes the handover real rather than nominal.

The Network Nervous System page covers the network-level governance that approves the launch. The two systems share a design vocabulary — neurons, proposals, dissolve delays, following — which is deliberate: a participant who understands one understands the other.

The documentation also notes that an SNS can be upgraded and that its canisters are ordinary canisters running on the network. There is no special execution environment for a governed dapp, and no exemption from the cycles model. An SNS that runs out of cycles stops serving update calls exactly as any other canister would.