> For the complete documentation index, see [llms.txt](https://seeswap-one.gitbook.io/seeswap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seeswap-one.gitbook.io/seeswap/understanding-see-token/see-protocol-governance-token.md).

# SEE - Protocol Governance Token

Since its inception, we have envisioned SeeSwap Protocol's future as a completely Decentralized Autonomous Organization. To build an autonomous decision-making mechanism is the *only* way to ensure the long-term security and sustainability of the SeeSwap Protocol and avoid any centralized point of failure.&#x20;

We have looked into several community-oriented approaches and methodologies and have landed on an approach: Protocol Governance Token - which we believe serves as alignment between token holders and protocol stakeholders. SEE tokens will be used by the voting community to drive participation to make decisions on adding new pools, changing pool parameters and many other aspects of the SeeSwap Protocol.&#x20;

### **SeeSwap Most Important Stakeholders: Liquidity Providers**

As a recap, SeeSwap Protocol allows any Harmony address to existing SeeSwap pools, or even create their own pools. Liquidity attracts traders, trading generates fees, and ultimately pool profitability attracts more liquidity. This is a flywheel effect that we are beginning to see happen within SeeSwap protocol.

Early liquidity providers take on more risks and opportunity costs: contract risk, low initial pool profitability, etc. We believe that these protocol users should get to participate early on in deciding how the protocol evolves.&#x20;

SeeSwap core team has proposed the implementation of SEE tokens - a utility token and governance token which will decide the resource allocation of the SeeSwap ecosystem. Via manual airdrops in version 1 by the core team and liquidity mining in version 2, the ownership of SeeSwap will be decentralized and transferred to the community gradually.

### How is governance implemented?

![](/files/-MhVGmdRr0w3CnoRooTc)

SEE ([contract address](https://explorer.harmony.one/#/address/one1073q9ldnkrktjag3nnp639dlkvgy4kngn2j086)) is an HRC-20 token that allows the owner to vote for any protocol proposal. Changes to the owner’s token balance automatically adjust the voting rights. Genesis supply of SEE token is 1,000,000, allocated to 5 categories based on the unlock schedule.

As a governance token, SEE is used by the token holders to vote for the pool management and resources allocation of the SeeSwap ecosystem. Good pool management is important for the long-term security and sustainability of the protocol, and is done in practice by voting on changing pool parameters and adding assets. Another important factor to determine is the collateral assets used in the stablecoin (BUSD/USDs) wrapper, which will be implemented in v2. Also, 500,000 SEE tokens are allocated to the ecosystem development for incentivization of strategic partners that will help our ecosystem to thrive, where community voting will also be an important input.

We have decided to use weighted voting for the governance process (subject to change based on community feedback) - each SEE holder can submit a new proposal or vote for any number of proposals with the SEE he holds. Each of the SEE token counts a vote, i.e. the more tokens he holds, the higher his weight is in the voting. The proposal receiving the most votes will be activated to implement changes to create new pools or change pool parameters.

The initial governance framework will be using the community channel to spread awareness around new proposals, and coordinate votes. A new page on [seeswap.one](https://seeswap.one/) will be available for all SEE holders to easily vote with their SEE by using [ONE Wallet](http://harmony.one/onewallet). In version 3, a SEE holder will be able to delegate votes to a proxy voter.

### **Token Supply and Allocation**

**10,000,000 SEE have been minted at genesis and will be allocated based on the following tokenomics design (publicly available** [**here**](https://docs.google.com/spreadsheets/d/1gCOdPKtE9pU_-tG-ShT3LEYMiA3JyrIpidjNmyufDi0/edit#gid=845017851)**):**

* 2.5M to the Core Team, subject to [vesting schedule](https://docs.google.com/spreadsheets/d/1gCOdPKtE9pU_-tG-ShT3LEYMiA3JyrIpidjNmyufDi0/edit#gid=957358217).
* 0.5M to Protocol Development, as incentivization for developer contributions to the core protocol.
* 0.5M to Ecosystem & Grants, as incentivization of strategic partners to help the SeeSWAP ecosystem thrive.&#x20;
* 1.5M to initial liquidity providers and initial SEE demonstration pools to bootstrap community-led growth.
* 5M to the LP community as rewards from liquidity mining.

![](/files/-MhVGsLkasZG9tkBaEdI)

![](/files/-MhVGvPnLadKDD60A7fM)

**Treasury Addresses:**

| Account                  | Amount    | Address                                                                                                                                                |
| ------------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Core Team**            | **2.5 M** | [**one1hc4eckffh7h64tcrl3pgjs0m4luekvdatcshg9**](https://explorer.harmony.one/#/tx/0x5362953e5ca538fc26cfbdc3e42ec62041263cba087e54cb1832d90e544b56a8) |
| **Protocol Development** | **0.5 M** | [**one1yv5r8ty3lfuwvcvep6da9rpjlky3gkym7wefzu**](https://explorer.harmony.one/#/tx/0x087430f711cc19d852974eed826a2791c899506251f961da9a0fc8e9f0d568fd) |
| **Ecosystem & Grants**   | **0.5 M** | [**one1ckjh65psxe9cpr54rmvpuuxuqq8a72vzlyvuea**](https://explorer.harmony.one/#/tx/0xcaa245cf2c78bc7f3e32a5b5ded2c7fb287515c02436b9ac7b4f3340c8798068) |
| **Initial LP Incentive** | **1.5 M** | [**one16m02xd80w44557l0fkmdcanavq5x98wjll6jsh**](https://explorer.harmony.one/#/tx/0xc8024160095c31124882a504227473e886ed7eb486a6b32263bb97987c79e74b) |

**version1 Airdrop**

The first SEE Airdrop is scheduled on the SeeSwap Launch Date 31-10-2020 (1.5 SEE token will be distributed to each telegram member/first users on Sunday 01-11-2020).

In practice, every week the core team will:

* Define the starting and ending epoch of the week for snapshots. Both are chosen as the epoch with the closest timestamp to a fixed weekly time (e.g. Sunday 10:00 AM PST).&#x20;
* For each snapshot period, the SeeSwap Core team will rank all user address based on it's highest txns on the ONE<>ONEs wrapper and finalize the distribution as below. This info will be publicly shared in our [community](https://t.me/joinchat/OB-IYBptEmqS9SUjMpTBVA) and publicly available at [seeswap.one/airdrop](https://docs.google.com/spreadsheets/d/10rhG2CeF0FNb2-GrVADet5jxi9sGxpSJfdcBzSq7A1o/edit#gid=112705390).

![](/files/-MhVH-2WbBOA1nld9ep8)

👇 Unlock schedule for "Initial LP Incentives" via airdrop (assuming V2 release occurs after one year) -  10600 SEE tokens.

![](/files/-MhVH3RGqHAhxm3en_w7)

**version 2 liquidity mining:**

5M SEE tokens will be distributed as incentives for liquidity providers since version 2.

Each week 14,500 SEE, or approximately 0.75M per year, are distributed to liquidity providers after SeeSwap v2 Launch. This meant to kickstart the distribution of governance rights of the protocol, transitioning the ownership of the protocol from the core team to the community. At the scheduled rate of 14,500 SEE/week, it would take 6.4 years to distribute the 5M Liquidity Mining rewards before the 10M cap is reached.

The schedule of SEE distribution (and if it should stop before the 10M cap is reached) for the following years is going to be extensively discussed and determined by the SEESWAP [community](https://t.me/joinchat/OB-IYBptEmqS9SUjMpTBVA) via our governance mechanism.


---

# 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://seeswap-one.gitbook.io/seeswap/understanding-see-token/see-protocol-governance-token.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.
