# Glory Badge

The section of Glory Badge is the core section of City of Dream and the way to realize the characteristic DAO of City of Dream, which is closely related to the development of the COD ecosystem. The user who owns the badge will become the co-founder of City of Dream, acquire the right to mint $COD, participate in project governance, and some other welfare.

At the same time, the Glory Badge serves as the companion of City of Dream's chain-sale model, bundled by the transaction signature between the wallet addresses on the chain, which establishes a chain of interests through the payment behavior between addresses and addresses. Thus the perfect closed loop of chain-sale is created, breaking the increasingly solidified trust crisis and giving new meaning and content to the blockchain.

{% hint style="info" %}
Chain Sales: A sales mechanism that combines multi-level bonus rules with cash flow distribution, running on a fully decentralized, non-tamperable public chain.
{% endhint %}

![Glory Badge](/files/IDp5TWAyN2NuRTYtrJUp)

### How to get the Glory Badge?

City of Dream issues four kinds of badges, a total of 2620, each is a unique NFT, the badge owner will directly become the co-founder of City of Dream, and obtain the right to mint coins and participate in community governance. Different categories of badges are obtained in different ways, roughly divided into two kinds: purchase to obtain and recommend to obtain, that is, users can directly purchase to obtain the Marquis Badge or Viscount Badge, but also can recommend five users to purchase the lower level of medals to obtain the Duke Badge and Earl/Count Badge.

### **Launching Method of Glory Badge**

<table><thead><tr><th width="170">Type</th><th align="center">Condition</th><th width="199" align="center">How to win?</th><th align="center">Quantity</th></tr></thead><tbody><tr><td>Duke</td><td align="center">5 Referees with Marquis Badge</td><td align="center">Giveaway</td><td align="center">20</td></tr><tr><td>Marquis</td><td align="center">Purchase</td><td align="center">2000 usdt</td><td align="center">200</td></tr><tr><td>Count/Earl</td><td align="center">5 Referees with Viscount Badge</td><td align="center">Giveaway</td><td align="center">400</td></tr><tr><td>Viscount</td><td align="center">Purchase</td><td align="center">500 usdt</td><td align="center">2000</td></tr></tbody></table>

Each address can merely receive a giveaway with one badge, the rest badges can be traded in [Marketplace](/whitepaper/ecosystem/marketplace.md).

Users can light up a star for every invitee who buys a badge, and after lighting up five stars, they can receive the corresponding badge.

{% hint style="info" %}
Assuming that a user has purchased a premium badge such as the Marquis Badge, and his or her subordinates buy 5 Viscount Badge, he or she will receive a Count Badge. But keep in mind, he or she could only receive a giveaway once.

Each address can only get a different grade badge once, that is to say, supposing a user recommends 10 invitees to buy Marquis Badges, he or she can only gain one Duke Badge.
{% endhint %}

### Badge Welfare

|             Badge Grade             |       Duke      |     Marquis     |      Count      |     Visount    |
| :---------------------------------: | :-------------: | :-------------: | :-------------: | :------------: |
|              Commission             |       40%       |       30%       |       20%       |       10%      |
|               Giveaway              |    200M $COD    |    100M $COD    |     40M $COD    |    20M $COD    |
|  Open Character Blind Box for Free  | 4 times per day | 3 times per day | 2 times per day | 1 time per day |
| Purchase Amount for Future Projects |     500 USD     |     250 USD     |     100 USD     |     50 USD     |

![Glory Badg](/files/e2tyyBN6vXO9adGJFBdu)

5% of the giveaway token will be directly released to the badge holder's wallet, the rest 95% will be locked. The locked tokens are bound to badge, once the holder trades the badge to other, so do the locked tokens.

The locked token can be withdrawn by providing Liquidity, the stake rules are below:

<details>

<summary>The Staked token will be linearly released by 2.2 times within 60 days during which no other stake could be processed. The badge will also be locked for 60 days at the same time. After the release of the 60 days, the Badge can be transferred and traded.</summary>

</details>

For example, suppose that 5 million $COD is equal to 1000 USDT, you have to stake 5 million $COD and 1000 USDT to Liquidity Pool. Till the stake (60 days) ends,11 million $COD will be released to your wallet high-linearly, with almost 183,300 $COD per day.&#x20;

Only Badge holders could own the mint right in the COD ecosystem, the inflation depends on holders' stake scale.

80% of the staking token will be destroyed, and the rest 20% will be redistributed, including 40% for holders according to Badge level, 20% for DAO, and 40% for DAO-30.

{% hint style="info" %}
Blind box and broadcasting income, the upcoming ERC-1155 chain-sale API, dividends of other online projects. Sale team and lottery tickets.

Key is necessary for [Global Lottery Pool](/whitepaper/product/global-lottery-pool.md).
{% endhint %}

{% content-ref url="/pages/KBfbjcVtixG1ThQ45QJH" %}
[Global Lottery Pool](/whitepaper/product/global-lottery-pool.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://cityofdream.gitbook.io/whitepaper/product/glory-badge.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.
