Sismo DAO

Summary

Grant temporary Badge Curation power to Sismo Core Team for the next 3 months so that they can deploy internally developed ZK Badge to the curated protocol (https://app.sismo.io/) without going through a governance vote. The community will keep on curating badges proposed by external teams.

Abstract

This proposal aims to enable the Sismo Core team to deploy Sismo Core ZK Badges to the curated protocol without going through the full process of the badge curation governance vote for 3 months after acceptance of the proposal.

It will introduce a distinction between Sismo Core ZK Badges that are internally developed by the Sismo Core Team and Community ZK Badges that are developed by other external teams and projects.

The internally developed Sismo Core ZK Badges will be considered as internally assessed as compliant to the Badge Curation Guidelines by the Sismo Core team and thus deployable to the Curated protocol to enable a better delivery speed. A confirmation process described below acts as a counterbalance to this power.

The Community ZK Badges, developed by external teams and projects, will still go through a Badge Curation governance vote and community-verification of compliance to the Guidelines to ensure their minimum quality level.

Motivation

The main motivation behind the Sismo Badge Curation framework (that has been introduced in the proposal SIP-6 and accepted by the community) is to filter out bad quality, non-ethos-aligned or harmful ZK badges deployed by external builders on the playground protocol and keep them away from the curated protocol.

While it allows a healthy community-led sanity check for Community ZK Badges, it might hinder the delivery speed of new ZK Badges internally developed by the Sismo Core Team, as those badges could be time-sensitive (related to a recent event) or require fast-track deployment for a specific event.

Because reactivity and flexibility is critical to an early stage project (one of the most important roles of the Sismo Core Team is to inspire other teams to build on top of Sismo), this proposal suggest granting temporary power to the Sismo Core Team to internally assess the compliance of the ZK Badges it develops by itself and the ability to deploy them to the curated protocol without a vote. We think will increase the speed of the general adoption of the protocol and is beneficial.

This power would have to be reassessed through Sismo Governance at the end of the 3 months period.

Confirmation Process

To keep balance of this temporary granted power, the Sismo community will have the power to challenge any Sismo Core ZK Badge deployed on the curated protocol by launching a “Temperature Check” poll (as described in Governance Process) in the #core-team-badges Discord channel.

If this poll gets a majority of votes siding with the challenge, a Confirmation Snapshot proposal will be submitted to decide if the Sismo Core ZK Badge remains available or not on the curated protocol, following the traditional process.

Implementation

• The Sismo Core Team will be able to deploy new internally developed ZK Badges to the curated ZK Badge contract, attestations collections and flows without a governance vote.
• A channel called #core-team-badges (in Sismo’s Discord “Governance” section) will be created for the core team to bring transparency about new badges and for the community to express their thoughts with the opportunity to challenge any Sismo Core ZK Badge deployed by the Sismo Core Team.