# Configurations

## DAO configuration

For safe measures against DAO attacks make sure you DAO configuration has a **high minimum of governance tokens** for it to be altered.

### Initial Config Visualisation <a href="#initial-config-visualisation" id="initial-config-visualisation"></a>

{% hint style="success" %}
**Jito** will be used below for example purposes. After a DAO is deployed the configuration of a DAO can be found in **Settings**.
{% endhint %}

Upon opening **Settings** you will find the DAO main addresses, configuration & governances (treasuries).

<div data-with-frame="true"><img src="/files/lzzAIDGz8tHfY7xeWPRj" alt="DAO Settings Page"></div>

### Addresses <a href="#parameters" id="parameters"></a>

In the addresses section users are able to see:

* **Realm/ Pubkey**: Address of the DAO
* **Realm Authority 'x DAO Treasury'**: Realm authority, usually set to one of the DAO wallets, the authority controls DAO configuration.
* **Owner 'Governance Program'**: spl-governance instance used by the DAO.
* **Community Mint**: Address of the chosen governance token.
* **Council Mint**: Address of the council token.

### Governance (Treasuries) <a href="#governance-treasuries" id="governance-treasuries"></a>

In the governances section users are able to see the DAO treasury/ treasuries and their parameters, accounts & statistics.

For every treasury created an authority is also given for each.

### Advanced Parameters/ Config <a href="#config" id="config"></a>

In the advanced parameters/ config section users are able to see:

* **Community max vote weight source**: Percentage of the token supply considered for quorum or absolute number of the token supply or set number by the DAO.
* **Min community tokens to create governance**: Amount of tokens needed to change the DAO Config
* **Use community voter weight add-in**: Indicates whether voter weight governance plugin is used by the DAO.
* **Use max community voter weight add-in**: Indicates whether max voter weight governance plugin is used by the DAO.

{% hint style="info" %}
For **Multisig DAOs** without the community governance token, this value is irrelevant and it's defaulted to disabled value.
{% endhint %}

### Config Modification <a href="#config-modification" id="config-modification"></a>

Only users with sufficient governance tokens can propose configuration changes to maintain DAO security.

#### Prerequisites for Config Changes <a href="#prerequisites-for-config-changes" id="prerequisites-for-config-changes"></a>

Before modifying DAO configuration, ensure you have:

* Sufficient governance tokens to meet the minimum proposal threshold
* Understanding of the proposed changes and their impact
* Community consensus or discussion around the modification

{% stepper %}
{% step %}

#### Access DAO Configuration

Navigate to your DAO create proposal wizard section and move forward to DAO config and review the current configuration settings.<br>

1. Create Proposal
2. Proposal Details
3. Select Governance Wallet (Main)
4. Add Instruction
5. DAO Config
   {% endstep %}

{% step %}

#### Select Configuration Type <a href="#step-2---select-configuration-type" id="step-2---select-configuration-type"></a>

Click on **"Change Config"** to start proposing configuration changes.

Choose the type of configuration you want to modify:

**How would you like to configure your community token**: Liquid, Disabled, Membership

* Liquid - Maybe be bought, sold, or transferred.
* Disabled - This removes voting & managing power for token owners.
* Membership - Cannot be traded or transferred, but can be revoked by the DAO.

**Do you want the community to be able to manage this DAO**: Anyone with the alloted amount of governance power can edit non security-related information without a proposal.

**What is the minimum amount of governance power needed to manage this DAO?**: A user will need at least this much governance power to manage and edit information for this DAO.

**What type of governance structure do you want your DAO's community to use**: Default, VSR, NFT, Civic, QV, Custom

* Default - Governance is based on token ownership
* VSR - Locked tokens (veTokens)
* NFT - Voting enabled and weighted based on NFTs owned
* Civic - Governance based on Civic verification
* QV - Quadratic voting
* Custom - Add a custom program ID for governance structure

{% hint style="danger" %}
QV & Civic plugins are disabled at the moment, if you wish to pursue them please reach out!
{% endhint %}

**How would you like to configure your council token**: Liquid, Disabled, Membership

* Liquid - Maybe be bought, sold, or transferred.
* Disabled - This removes voting & managing power for token owners.
* Membership - Cannot be traded or transferred, but can be revoked by the DAO.

**What Type of community maximum voter weight do you want to use?**: This determines the maximum voter weight used to calculate voting thresholds. Updating this option requires you to know the maximum supply of your governance token.

* Supply Fraction
* Absolute
  {% endstep %}
  {% endstepper %}

{% hint style="warning" %}
**Security Note**: Always set conservative thresholds to prevent governance attacks. Higher minimum token requirements provide better security against malicious proposals.
{% 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.realms.today/realms-v2/dao-creation-wizard/configurations.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.