Skip to main content

Introduction

Note: This project is actively being developed, and features may evolve based on feedback from users.

What is a "Toolkit Project"?​

Toolkit projects provide creators with a streamlined way to manage and monitor their decentralized applications (dApps). By creating a toolkit project, you gain access to comprehensive tools to:

  • Manage and monitor the canisters that form your app
  • Add and install new canisters
  • Enable various governance modes
  • Manage shared assets, and more

Additionally, you can publish your project on the Toolkit website, making it discoverable to a broad audience. This enables users to see what you've built from the beginning and follow your progress.

Is it Similar to an SNS?​

In some ways, yes, but Toolkit projects have unique features that set them apart:

Control​

A toolkit project is fundamentally based on a single root canister, which is managed by the root registry canister.

When you add canisters to your toolkit project, they are assigned a single controller: the toolkit root canister. If you want to bring any canister back under your direct control, you currently have two options:

  • Deregister the canister to remove it from the toolkit project
  • Detach your toolkit project root (feature in development)

This structure provides centralized control for your project while maintaining flexibility for future adjustments.

Key Features​

  1. Toggleable Governance
    For smaller teams, governance may not always be necessary. However, as your project and team grow, or if you want greater control and transparency, you can enable a vote-based system. With governance enabled, any significant changes require approval through a proposal process.

  2. Members
    Adding a new team member? If governance is disabled, the project owner can add members directly. When governance is enabled, new members are added only through proposals. Members have equal rights and can make changes across the project, except for project wallet transfers and adding new members—these actions require special permissions.

  3. Logging
    Root canisters keep detailed logs of all mutation actions, ensuring transparency and traceability. This includes changes like updating intervals or adding new canisters, helping keep everyone informed about project developments.

  4. Less Cycle Consumption
    While the SNS architecture can incur high cycle consumption due to multiple canisters, Toolkit projects use a single Root canister, reducing costs without sacrificing functionality.

Future Features​

  1. Convert a Toolkit Project to an SNS
    When your project is ready, you'll have the option to convert it into an SNS. The toolkit aims to offer a simple, user-friendly solution for this transition, with more details coming as the feature is developed.

  2. Extended Governance
    We plan to expand current governance options by introducing a permission-based system for members. Additionally, you’ll be able to create a project token to enable a ballot-per-token voting system, where voting power is tied to token ownership.

  3. Add a Token
    A future step will allow you to easily create a token for your project, which will set up an ICRC ledger, index, and archive canister. You’ll have options to distribute tokens, either through sales or manually. Tokens can be used for specific use cases within your dApp or for governance as described above.