SIP-5: Close the waiting list to prepare for the next phase of Sismo DAO

Summary

Close the waiting list, open Discord’s public channels and only reopen the gates of the Sismo DAO for the first release of Sismo protocol.

Motivation

The Sismo Social DAO

The Sismo DAO was initially set up as a social DAO, gathering curated members sharing similar interests. It enabled us to have constructive conversations and feedback on our mission to create ZK Badges.

We, the Genesis team, have been joined by experts and like-minded individuals. Their enthusiasm and care for our mission, the survey we conducted and the hundreds of meetings with integrators and partners, gave us confidence to move the Sismo DAO towards its next phase.

From a Social to a Protocol DAO

Sismo Genesis team has grown to 9 members, we met with more than 200 partners and iterated three times on the product.

We are preparing the release of our first public product, which will mark a turning point for Sismo.

As we aim to build a new primitive for all, the product will be progressively driven by native badges, tokenomics and governed by the Sismo DAO.

This is why the Sismo DAO needs to evolve from a gated social DAO to a product-centric DAO accessible to all: a protocol DAO.

We suggest to put an end to the waiting list and open our Discord public channels to everyone.

For now, the Sismo DAO governance should remain reserved to already onboarded Zikies.

We will take a snapshot of the waiting list if this proposal passes and we will make sure to remember the people on it.

Some partners should still be onboarded in the DAO as part of the Gen[X] to help us ship our first product. Once the first version of the product goes live, the Sismo DAO shall open its gates to everyone, who will be gradually granted power over the protocol.

Specification

The Sismo DAO formally petitions the Sismo Genesis team to:

• Take a snapshot and close the waiting list,
• Suspend the onboarding of new Gen[A] members,
• Open Sismo DAO Discord public channels to everyone,
• Update Sismo.io to reflect those changes.