> For the complete documentation index, see [llms.txt](https://docs.superverse.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superverse.co/dao-staking/dao-staker.md).

# DAO STAKER

Today is not only a significant milestone in our journey but also a shift towards new decentralized possibilities. This transition provides SUPER asset holders with the opportunity to continue to actively participate in our community and network by staking their tokens to earn ETH rewards generated by the decentraised network. \
\
Following the community's successful approval of the 3 SVIPs during the DAO vote, we have been administering the passed proposals and have set the foundation for the DAO operating framework to be built upon. On this note, we’re thrilled to announce that the staking smart contracts have been deployed and **DAO staking is now officially live!**

{% hint style="warning" %}
For enhanced transparency, operational details are shared below:

* <mark style="color:orange;">**DAO Staking Website:**</mark> [staking.superverse.cool](https://staking.superverse.cool/)
* <mark style="color:orange;">**DAO Staking Contract:**</mark> 0x8c96edc82d111e3c5686f5abe738a82d54d0b887
* <mark style="color:orange;">**DAO Treasury Wallet:**</mark> 0x0b989Eb5271535F75e4Cb967406e99a36C3c2E9b
* <mark style="color:orange;">**Current Holdings:**</mark>
  * <mark style="color:red;">**ETH + WETH Balance:**</mark> **335.6** currently held in the DAO Treasury wallet. *(100 ETH will be sent to the staking contract for initial infusion)*
  * <mark style="color:red;">**USDC Balance:**</mark> **1,689,060.48** currently held in the DAO Treasury wallet.
* <mark style="color:orange;">**GEM Conversion Website:**</mark> [staking.superverse.cool/gem-claim](https://staking.superverse.cool/gem-claim)
* <mark style="color:orange;">**GEM Conversion Contract:**</mark> 0xba48bcc66b6665495ec643ece7811db5723aaf91
  {% endhint %}

While launching the DAO staker is the initial step, administering the SVIPs concerning proposals and voting is ongoing. The GEM conversion and NFT Booster utilities, which are delineated below, form the backbone of the new phase, aligning with the ecosystem's core mission. \
\
As you navigate through the upcoming sections, we will delve further into these vital components, marking the continuous progression of our ecosystem.

### <mark style="color:yellow;">Section Overview:</mark>

{% content-ref url="/pages/d0thP8PxIOuf8E08UZgU" %}
[Staking Mechanism](/dao-staking/dao-staker/staking-mechanism.md)
{% endcontent-ref %}

{% content-ref url="/pages/9Gb4gwLZieVFPTju469k" %}
[NFT BOOSTS](/dao-staking/nft-boosts.md)
{% endcontent-ref %}

{% content-ref url="/pages/kVfJdbqenlOIL4wCPGYi" %}
[GEM CONVERSION](/dao-staking/gem-conversion.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, and the optional `goal` query parameter:

```
GET https://docs.superverse.co/dao-staking/dao-staker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
