# 🏛️ Governance

VIBES is a decentralized [cryptonetwork](/protocol/vibes-token.md) that is owned by the community. 

While VIBES is a token-coordinated protocol, **it was designed to be as governance-minimal as possible** and encourage more [decentralized coordination](/protocol/curation.md#influence) and [organization](/protocol/community.md) over monolithic "governance".

{% hint style="info" %}
🚀 You do not need anybody's approval to start building in VIBES.
{% endhint %}

## Process

VIBES is a process-minimal organization, but below is a rough outline of how we coordinate.

### Discord Discussion

Protocol governance starts with informal discussion on Discord. Have an idea? Want to see something changed? Float it in the chat and see what others think. 

{% hint style="info" %}
Use the [#⚙️-protocol channel](https://discord.gg/C5TFZVjSZ5) on Discord to discuss any ideas for changes or possible future proposals for VIBES.
{% endhint %}

### Off-chain Signaling

VIBES uses [Snapshot](https://snapshot.org/#/sickvibes.eth) for off-chain signaling, which lets you securely vote by using your web3 wallet to cast a signed ballot. 

Off-chain signaling is great for gauging community consensus around how to use shared resources or signal support for a change in the protocol. Feel free to use Snapshot in more creative ways if you think it'd be helpful or fun.

Don't feel like a Snapshot proposal needs to be created for everything (we build first and ask for permission later), but it can be a great way to encourage community involvement and allow people to voice their opinion

{% hint style="info" %}
**Snapshot is just a tool**: since it's not on-chain it's not binding except at the "social layer". 
{% endhint %}

## Organization

The organization of VIBES is intentionally very flat, simple, and non-prescriptive.

We are an early-phase protocol and are avoiding having explicit roles and favor open, permissionless contribution. 

### VIBES Multisig

The VIBES multisig members where chosen by @bvalosek in the initial phases of VIBES based on mutual trust, friendship, crypto fluency, and support of both the VIBES project and the [BVAL NFT project](/resources/updates/prologue.md) that started it.

The multisig is a social-layer coordination group, and a Gnosis Safe has been deployed to manage protocol assets and smart contract control in a way that requires **3-of-5 consensus** on all transfers or contract invokes.

{% hint style="info" %}
**The VIBES Multisig is controls a relatively small part of VIBES**. 

Multisig action is only required occasionally, and the community, protocol, and art collective can evolve and change without any need to involve the multisig.

**You do not need the approval of the multisig to start building in VIBES.**
{% endhint %}

The address of the multisig Gnosis Safe:

* `0x41925458151134A5324c9382915fc94C31Bce1B3` \[[polygonscan](https://polygonscan.com/address/0x41925458151134A5324c9382915fc94C31Bce1B3)]

The multisig is responsible for:

* Handling [VIBES Treasury](/protocol/vibes-token/treasury-allocations.md) funds
* Setting / resetting [Influence](/protocol/curation.md) for curators
* [Smart Contract](/resources/architecture.md) administration and protocol control
* [Snapshot Space](https://snapshot.org/#/sickvibes.eth) configuration
* [Discord](https://discord.gg/qDrsjcGR2F) administration

#### VIBES Multisig Members

Members can be identified in Discord via the **@VIBES multisig** role.

| Discord          | Address                                      |
| ---------------- | -------------------------------------------- |
| `bvalosek#9578`  | `0x303eefedee1ba8e5d507a55465d946b2fea18583` |
| `zamboni#2731`   | `0x8AbAf5733742B1506F6a1255de0e37aEc76b7940` |
| `leesah#3235`    | `0xf8530CcA204442e56F8f55ea35Eb0fDF0b40eEc8` |
| `lootsoot#7959`  | `0x0c6204B8ebaF837d5cff51447050777CD9B39FC4` |
| `jpangelle#5070` | `0xf976128e5c9214F802184A3d6f97DdEeEa78c124` |

{% hint style="info" %}
**Please do not DM members of the multisig** regarding any administrative questions or requests, ask in public Discord channels and tag the **@VIBES Multisig** role.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sickvibes.xyz/protocol/governance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.