# Nose DAO

Every project has a DAO now, do we *need* another one? The DAO is required for the longevity of the project and will have a steady handle on all upcoming project decisions. The DAO will also be heavily rewarded for engaging in building the future, because otherwise, what are the devs good for?&#x20;

### **DAO Supply Allocation** :gem:

We do not want to double-dip on our current supporters for releasing another project when the original one has not minted out. Therefore:

> **37 of the 333** Diamonoses are reserved for **existing Summoners** of the 999 Noses.\
> A further **13 pre-minted** Diamonoses are **reserved** for **partnering communities**.

### DAO Utility :toolbox:

The 333 Diamonoses that represent access to the Nose DAO, benefits include:

1. DAO-only channels.
2. Governance votes on:
   * Next <img src="/files/v4lWqQLheO33PWIbaexL" alt="" data-size="line">$SNIFF sinks.
   * Next featured Artist on our <img src="/files/v4lWqQLheO33PWIbaexL" alt="" data-size="line">$SNIFF-only drops.
3. A significant multiplier on <img src="/files/v4lWqQLheO33PWIbaexL" alt="" data-size="line">$SNIFF earned.
4. Can propose internal utility ideas that will be put up for a vote.
5. Priority builder/artist nomination for future drops or 1/1 auctions.
6. Revenue share on a portion of <img src="/files/v4lWqQLheO33PWIbaexL" alt="" data-size="line">$SNIFFs earned.

{% hint style="info" %}
When generating the artwork for the original 3,456 Noses, this diamond skin type was set to a rarity weightage *so low* that the generator completely missed it in the output. As did we. We found the perfect way for the Diamond-skinned Noses to make their comeback.
{% endhint %}

### **Mint Info** :herb:

The **333 Diamonoses** are **WL-only** mints. We want builders and artists of the space to join in, and we would love to handpick our WL spot winners. They should be deserved, not only based on luck. This guarantees a supply-demand balance.

![](/files/mIgTKy6ekUvEFDRX7hYl)

#### **WL Spot Allocation**

1. **100** will be given away as **partner-run contests** for WL spots, only for those who want in.
2. The remaining **183 WL spots** will be **given away to the public**, by:
   * Showing proof of **builder contribution** (a GitHub link to your contribution) and/or participation in web3 courses/tutorials. (ie. [buildspace](https://buildspace.so/))
   * Showing your **existing artwork and portfolio**. **Fanart** of the Noses is **welcome**.

#### **Mint Mechanics**

Here's where it gets interesting. This is a <img src="/files/v4lWqQLheO33PWIbaexL" alt="" data-size="line">$SNIFF-only, WL-only mint. But we also want to make it possible for newcomers to earn <img src="/files/v4lWqQLheO33PWIbaexL" alt="" data-size="line">$SNIFF.

{% hint style="info" %}
The ***easiest way*** would be to **mint 3 Noses** from the original Nose Age NFT **3,456 collection**, and burn them on our custom program for <img src="/files/v4lWqQLheO33PWIbaexL" alt="" data-size="line">$SNIFF.
{% endhint %}

> Price per Nose: **0.25 SOL**\
> \
> Price per Diamonose (DAO): **40,000** <img src="/files/v4lWqQLheO33PWIbaexL" alt="" data-size="line">**$SNIFF** (Equivalent to 4 sacrificed Noses, worth **1 SOL**)

#### **Wen mint?**

When all the WL spots have gone out, and when everyone is ready with their <img src="/files/v4lWqQLheO33PWIbaexL" alt="" data-size="line">$SNIFFs to mint.


---

# 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://noseage.gitbook.io/nose-age-nft-aitepaper/saga-nfts/nose-dao.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.
