# $SUMR Token

The $SUMR token is the governance token for the Summer Protocol. Holders of $SUMR and delegators make up the Summer DAO, which oversees and governs the protocol. Governance operates on a weighted voting system, where the number of $SUMR tokens held determines voting power.

• Community (35%, 350M): The largest allocation ensures the community remains the driving force behind $SUMR, rewarding active participation and engagement. At deployment, approximately 8.5% of the total supply, is set aside for governance grants. However, it is ultimately the DAO's responsibility to determine how the entire community allocation is distributed, ensuring flexibility and alignment with the protocol's goals.

• Key Stakeholders and Strategic Partners (25%, 250M): These tokens are set aside to strengthen collaborations and build a resilient ecosystem through key partnerships.

• Core Contributors (20%, 200M): Dedicated to the developers, maintainers, and contributors who power the protocol’s evolution and innovation.

• Foundation (Development, Ecosystem Growth and Marketing) (20%, 200M): Reserved to fund ongoing development, expand the ecosystem, and drive long-term growth initiatives.

<figure><img src="/files/PLUWbFdj8pnEV4ndw22z" alt=""><figcaption></figcaption></figure>

$SUMR token holders are at the heart of the protocol’s evolution, ensuring a decentralized, community-driven approach to governance.

Contract Address (SUMR): <https://basescan.org/token/0x194f360d130f2393a5e9f3117a6a1b78abea1624>

Contract Address (stSUMR): <https://basescan.org/token/0x7cc488f2681cfc2a5e8a00184bfa94ea6d520d1c>


---

# 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.summer.fi/lazy-summer-protocol/governance/usdsumr-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.