# [ZIP-1]: ZIPs & ZCCPs Purpose and Guidelines

- Space: [Zaros Governance](https://snapshot.box/s:zarosfi.eth.md)
- Author: 0x80D910f5A481eb04cFb9184DF7358B5E6f790888
- State: Closed
- Voting type: Single choice
- Start: 2024-07-31 17:17 UTC
- End: 2024-08-04 18:00 UTC
- Votes: 5
- Discussion: https://discord.com/channels/1023936505321881641/1260656138547101716
- Open in Snapshot: https://snapshot.box/#/s:zarosfi.eth/proposal/0xb1f800177c58cacec6291090642bca1a47eb0391195751920b204df9c2b88146

## Results

- Yes, let's do it: 5 voting power, 100.0%
- No, that's not the way.: 0 voting power, 0.0%

## Proposal

# 

| Author | Guilherme Bettanin |
| --- | --- |
| Type | Governance |
| Network | Arbitrum & Monad |
| Status | Vote In Progress  |
| Created | 2024-06-31 |

The V1 governance framework proposal is based on Ethereum EIPs framework and Synthetix DAO SCCPs framework because of its large adoption both by protocols and its communities, participating on votings and successfully maintaining the decentralization of the protocol

# What is a ZIP?

Zaros Improvement Proposals’ purpose is to ensure changes to Zaros are transparent and well governed. A ZIP is a design document providing information to the Zaros community about a proposed change to the system. The author is responsible for building consensus within the community and documenting dissenting opinions.

# What is a ZCCP?

Zaros Configuration Change Proposals’ purpose is to modify one of the system configuration variables. The intent is to provide a clear and detailed history behind each configuration change and the rationale behind it at the time it was implemented. The author of the document is responsible for building consensus within the community and documenting dissenting opinions.

# ZIP & ZCCP Rationale

We intend ZIPs and ZCCPs to be the primary mechanisms for proposing new features, collecting community input on an issue, and for documenting the design decisions for changes to Zaros. 

It is highly recommended that a single ZIP contain a single key proposal or new idea. The more focused the ZIP, the more successful it is likely to be.

A ZIP or ZCCP must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement.

By encompassing these aspects, ZIPs help maintain clarity in Zaros’ development roadmap, enabling stakeholders to collectively steer the course of the platform's growth.

# ZIP Work Flow

Parties involved in the process include the *author*, the ***ZIP Editors***, the Zaros Core Contributors (CCs), the Zaros Council, and the Zaros Community.

Given the decentralized nature of the Zaros development process, anyone within the Zaros community is welcome to submit a ZIP. However, to foster a collaborative environment, it is strongly encouraged that proposers engage in discussions within the [Zaros Discord](https://discord.com/invite/zarosfi) community before formally submitting their proposals. This preliminary discourse allows for the exchange of ideas, feedback, and refinement of concepts, ultimately leading to more robust and well-considered ZIPs.

Progression through the ZIP workflow is requested by the ZIP author through a pull request, and reviewed by the ZIP editors.

The ZIP workflow comprises three main stages:

1. Creation

Once submitted, every ZIP will begin as a **`Draft`**. It must then meet specific formatting criteria (largely, correct metadata in the header which will be discussed later), and be manually approved by an editor for further community discussion and consideration.

The author of the ZIP proposal is responsible for building consensus within the community and documenting dissenting opinions. Authors must include a link to where people should continue discussing your ZIP.

1. Voting

Once a **`Draft`** is believed to be mature enough and ready to progress, it must be **`Approved`** to be executed. Approval of an ZIP will be granted through:

- Consultation with at least one member of the Zaros council, found through the Zaros Discord. They will assess whether the proposal needs a ‘Feasibility study’.
- If it does need a ‘Feasibility Study’, the ZIP will progress to the **`Feasibility`** stage. It will then be assigned a CC who will work with the author to conduct a ‘Feasibility study’. Once all parties are satisfied, the ZIP is moved to **`ZC Review Pending`** where it will be discussed.
- If it does not need a ‘Feasibility Study’, the ZIP will progress straight to **`ZC Review Pending`** where it will be discussed.
- The Zaros council can send it back to the **`Draft`** or **`Feasibility`** stage if they believe more edits are required, if not, it will enter the next stage
1. Approval

ZIPs will be voted on by the Zaros Council (**`ZC Vote Pending`**) for **five (5) days,** and proposals will be passed only under a majority decision. Approved ZIPs are moved to **`Approved`**, and then **`Implemented`** once executed by the Zaros Council, protocol CCs, or community members. Otherwise, it is **`Rejected`**.

## **ZIP status terms**

- **Draft** – The initial state of a new ZIP before the Zaros Council and core contributors have assessed it.
- **Feasibility** – a ZIP that is being assessed for feasibility with an assigned Core Contributor.
- **ZC Review Pending** – a ZIP that is awaiting a Zaros Council Review after the Author and Core Contributor are satisfied with feasibility.
- **Vote In Progress** – a ZIP currently being voted on by the council.
- **Approved** – a ZIP that has successfully reached a majority Zaros Council vote in favour.
- **Rejected** – a ZIP that has failed to reach a majority Zaros Council vote in favour.
- **Under Implementation** - a ZIP that is under implementation by the Zaros Council, protocol CCs, or community members.
- **Implemented** – a ZIP that has been released and implemented.

## **What belongs in a successful ZIP?**

Each ZIP should have the following parts:

- Preamble – RFC 822 style headers containing metadata about the ZIP, including the ZIP number, a short descriptive title (limited to a maximum of 44 characters), and the author details.
- Simple Summary – “If you can’t explain it simply, you don’t understand it well enough.” Provide a simplified and layman-accessible explanation of the ZIP.
- Abstract – a short description (~200 words) of the technical issue being addressed.
- Motivation (*optional) – The ‘motivation’ is critical for ZIPs that want to change any aspect of Zaros. It should clearly explain why the existing specification is inadequate to address the problem that the ZIP solves. ZIP submissions without sufficient motivation may be rejected outright.
- Specification – The technical specification should describe the syntax and semantics of any new feature.
- Parameters – The configurable parameters set in this section can be updated by a proposal with **`type`** header set to **`parameter-change`** to simplify the specification. New parameters should have initialised values under this heading.
- Rationale – The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community and should discuss important objections or concerns raised during discussion.
- Test Cases – Test cases may be added during the implementation phase but are required before implementation.
- Copyright Waiver – All ZIPs must be in the public domain. See the bottom of this ZIP for an example copyright waiver.

## ZIP **Editor Responsibilities**

For every new ZIP submitted, at least one (1) council members and one (1) core-contributor must operate as editors. During the drafting stage of the process, the assigned members will work closely with the Author to:

- Ensure the title accurately describes the content.
- Read the ZIP to check if it is ready: sound and complete. The ideas must make technical sense, even if they don't seem likely to get to final status.
- Check the ZIP for language (spelling, grammar, sentence structure, etc.), markup (Github flavored Markdown), and code style

If the ZIP isn't ready, the editor will send it back to the author for revision, with specific instructions.

Once the ZIP is ready for the repository, the ZIP editors will:

- Assign an ZIP number (generally the PR number or, if preferred by the author, the Issue # if there was discussion in the Issues section of this repository about this ZIP)
- Merge the corresponding pull request
- Assign a Core Contributor to conduct a feasibility study on the ZIP.
- Send a message back to the ZIP author with the next step.

The editors do not pass judgment on ZIPs. They merely hold an administrative and editorial role.

## ZIP Template

[Click here to access the ZIP Template notion page](https://www.notion.so/ZIP-Template-1b9ec4d6ed51433b84f0d2623c766996?pvs=21)

## **History**

This ZIP document was derived heavily from the SIP Synthetix Improvement Proposal document and in many places, text was simply copied and modified. Any comments about the ZIP document should be directed to the ZIP editors. The history of the ZIP is quoted below from the ZIP document for context:

- *“The SIP document was derived heavily from the EIP Ethereum Improvement Proposal document. In many places text was simply copied and modified. Any comments about the SIP document should be directed to the SIP editors. The history of the EIP is quoted below from the EIP document for context:”*
    - *"This document (EIP) was derived heavily from[**Bitcoin's BIP-0001**](https://github.com/bitcoin/bips)written by Amir Taaki which in turn was derived from[**Python's PEP-0001**](https://www.python.org/dev/peps/). In many places text was simply copied and modified. Although the PEP-0001 text was written by Barry Warsaw, Jeremy Hylton, and David Goodger, they are not responsible for its use..."* *

## **Copyright**

Copyright and related rights waived via [**CC0**](https://creativecommons.org/publicdomain/zero/1.0/).

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

