Last Update:16/09/2024





1 Introduction

Decentralized Autonomous Organizations (DAOs) have emerged in the Web3 ecosystem. They enable these communities to self-govern their projects. On ETH, major DeFi DAOs like Uniswap and MakerDAO collectively manage billions of dollars in smart contracts, underscoring the significant traction behind on-chain governance.

The Internet Computer itself is governed by the Network Nervous System (NNS), an on-chain DAO that manages everything from protocol upgrades to network economics. Building on this foundation, the ICP Community also introduces the Service Nervous System (SNS) framework to extend decentralized governance to individual dapps. Technologically, the Internet Computer also offers unique support for fully decentralized organizations. Unlike the traditional smart contract platforms that often rely on off-chain cloud servers for front-ends data, ICP can host entire applications (FE, BE, and storage) 100% on-chain. This means a DAO on ICP isn’t limited to governing a few contracts, but it can directly control software updates and features of a live web service. In conclusion, the ICO Ecosystem provides a robust foundation for next-generation DAOs that can serve entire communities directly from the blockchain.

1.1 Existing Gaps

Decentralized Autonomous Organization (DAO) is already a popular concept in the Web3 World. The system allows people to create a community that can manage their works transparently.

This rigidity limits community innovation: if a group devises a novel voting scheme or a treasury management tweak, how would they do it?

1.2 What is SUDAO?

SUDAO addresses these gaps by being is a decentralized autonomous organization platform on ICP Ecosystem that extends core governance with modular, plugin-based architecture built in Motoko. We hope that members can extend and shape their DAO to better serve their community goals.

<aside> <img src="attachment:6eb1149d-f5c2-4124-8f59-037a50af500c:SUDAO_-White.png" alt="attachment:6eb1149d-f5c2-4124-8f59-037a50af500c:SUDAO-_White.png" width="40px" />

The name is inspired by sudo in Unix, which grants elevated privileges. SUDAO symbolizes a DAO Framework that gives super-level control to communities, enabling them to govern not just treasury but the entire functionality of their organization.

</aside>

1.2.1 Target Users

We targets web3-engaged individuals who understand blockchain principles and community governance but lack the coding skills to implement technical solutions.

Regional Round - SUDAO Pitch Deck_page-0004.jpg

Our target users is basically social entrepreneurs who have access to tech and motivated by a mission on their community.

These types of people will be early adopters of SUDAO, which will have iterative development of the group.

While SUDAO can be used by all kinds of communities, our platform is especially appealing to activist movements and local communities. The group often need unique decision-making models. They also have customized treasury rules, like allocating a percentage to funds or social programs, or rotating leadership roles. See our market here.

1.2.2 Solution Key Points

image.png

  1. No-Code DAO A no-code DAO is important because it removes the technical barriers that comes with blockchain governance. Instead of requiring members to understand smart contracts or hire developers, communities can launch and run their DAO through simple interfaces. This accessibility empowers more grassroots movements, student clubs, and activist groups—people to take ownership of their governance and treasury. By making DAO creation as easy as filling out a form, it opens decentralized decision-making to anyone with an internet connection.
  2. Customizable Core No two communities operate in exactly the same way, and rigid frameworks can struggle growth or exclude unique needs. A customizable core allows each DAO to adjust or extend its governance features, treasury setup, and proposal mechanisms to reflect its culture and goals. In SUDAO, the core functionality like the proposal mechanism of a DAO is even manageable.
  3. Operates as the Community Landing Page Your DAO in SUDAO is not just a tool for your members, it becomes the central hub where members and outsiders alike can understand the mission, track progress, and stay informed. Instead of scattering updates across chats, social media posts, or spreadsheets, the DAO’s landing page consolidates news, proposals, and key information in one accessible place. We were highly inspired by Wordpress and want to make a similar product for your community.
  4. Creator Dashboard Initial organizers still has control over the management of their DAO without overwhelming with technical complexity. Soon, these roles can be available to delegate to moderators and administrators that helps to run the DAO. With a reliable dashboard, they can focus on nurturing the community to guide governance, finances, and engagement efficiently.

2 Architecture

SUDAO’s helps you create your community Website, deployed on its own isolated IC canister stack and runs whatever you need. Motoko canisters for backend logic, TypeScript/JS bindings for canister interfaces, and a React/Vite frontend for user interaction. The system is designed for the Internet Computer (IC) ecosystem, supporting DAO and AMM functionalities.

suDAO WCHL

2.1 DAO Creation Flow

At a glance, DAO Creation follows this sequence described by the diagram.

<aside> 💡

Steps 2-4 runs asynchronously so the DAO ID is returned immediately after step 1; The actor can fetch DAO information + deployment status afterward.

</aside>

image.png

END TO END SEQUENCE

  1. Immediate DAO ID Assignment & Progress Feedback When a user submits the DAO creation form, the frontend immediately receives a dao_id from the backend (factory canister). 🌟 Purpose: This allows the UI to show progress and status updates, even while the actual canister deployment and initialization are still running asynchronously.

  2. Canister Creation via Factory (Explorer) The DAO Factory (Explorer) is responsible for orchestrating the creation of all required canisters. The factory calls Internet Computer (IC) management APIs to create three separate canisters:

  3. Code Installation After the canisters are created, the factory installs the appropriate code (WASM modules) into each canister.

  4. Canister Initialization The factory then initializes each canister:

    The Token/Ledger canister performs an initial mint, sending tokens directly to the AMM canister.

  5. Asynchronous Completion & Status Polling

    Asynchronous operations and status updates are managed in Motoko backend files, with progress exposed via canister methods.

WIPs

Currently, the DAO Creation Flow asks for payment to be made after the deployment has successfully finished. This is honestly a workaround.

<aside> ℹ️

This hinders from the error that if the deployment fails at any stage (e.g., during canister creation, code installation, or initialization), the payment will not be consumed. This exposes users to the risk of losing cycles in the event of an incomplete deployment.

</aside>

In the future, the system will be extended so that payment required to be made up front before the deployment process begins. To mitigate this issue, we would also add:

This enhancement will ensure that user payments are not wasted due to temporary errors and that DAO deployments can reliably complete end-to-end without manual intervention. Explore more here for our future roadmap.

2.2 Plugins as Decentralized Feature Development

In SUDAO, plugins are modular extensions that add or modify the functionality of a DAO. Every core feature—including proposals—is delivered as a plugin, ensuring the system stays lightweight and flexible. Communities can install published plugins directly to extend their DAO and developers can build and publish new ones to be shared or sold in the marketplace. This structure allows anyone to integrate governance tools, analytics, or community apps with a simple installation, while giving creators the ability to monetize their contributions.

2.2.1 How do Our Plugins Work?

image.png

  1. Plugin creation

This is when a developer wanted to code a new plugin. They run sudao new <project>. This generates a sudao.json template metadata that contains something like:

{
  "name": "plugin",
  "version": "1.0.0",
  "creator": "abcd"
}

It also defines plugins specific routes/components.

{
  "routes": [
    { "path": "/analytics", "component": "Dashboard" },
    { "path": "/analytics/reports", "component": "Reports" }
  ]
}
  1. Plugin Bundling and Publishing Once the plugin logic and UI are implemented, it is packaged into a Plugin Bundle. This bundle is the distributable format that can be uploaded and shared through the registry. The bundled plugin is then published into the Plugin Registry. The registry acts as a central hub, storing plugin metadata, versions, and references, similar to an app store.

  2. Plugin Retrieval by DAOs When an individual DAO needs a plugin, its frontend calls getPlugin() to fetch the required plugins from the registry. The registry returns URLs or references that allow the DAO to dynamically load and use the plugin. Finally, the DAO frontend integrates the retrieved plugin into its interface. This allows the community to instantly extend DAO functionality (e.g., dashboards, analytics, reports) without changing the DAO’s core.

2.2.2 Publish Your Own Plugin

To publish your own plugin in SUDAO, you begin by creating a new project with sudao new <project>, which generates a sudao.json template containing the plugin’s metadata and route definitions. After implementing your logic and UI, the plugin is bundled into a distributable package and uploaded to the Plugin Registry. Once published, it becomes available for any DAO frontend to discover, fetch, and integrate dynamically, enabling communities to extend their functionality instantly without altering their core system.

3 SUDAO As A Product

Decentralized Autonomous Organizations (DAOs) have been growing at an estimated 30% annual rate since 2021, indicating it has robust expansion. The global market has validated the need for tools that enable decentralized governance.

3.1 Product Market Fit

As of 2025, over 13,000 DAOs have been established globally, collectively managing around $24-25 billion in treasury assets and involving over 11 million governance token holders. One clear trend in the DAO space is the demand for user-friendly, no-code platforms that allow non-developers (general Web3 enthusiasts, community leaders, entrepreneurs) to create and manage DAOs.

image.png

To strengthen our digital presence, we leverage our official YouTube channel SUDAO Core Team (http://www.youtube.com/@sudaocoreteam) for storytelling, tutorials, and community updates, as well as our X account (https://x.com/sudao_org) for active engagement, timely communication, and movement building.

| --- | --- | --- | --- |

*These can change during development process.