# Delegation: The Key to Voting

### **An Introduction to Delegation**

Delegation is required for SEAM tokens to be utilized in proposals and voting. It allows a SEAM token holder to authorize an address (i.e. a delegate) to vote by granting that delegated address the voting power from the original SEAM tokens.

There are two types of delegation, and both require the same process: 1) self-delegation or 2) delegation to another address. For self-delegation, a SEAM token holder simply chooses to delegate to their own address. Once SEAM tokens are delegated, the voting power of all SEAM tokens present within the original delegating wallet will be given to the wallet receiving the delegation. If the SEAM quantities change in the original wallet, the delegated voting power would change accordingly.

Delegated addresses are able to participate in the Seamless Protocol governance processes, including the abilities to create proposals and to vote.

This mirrors the delegation structure seen in many project governance tokens like Compound Finance.

A few important things to note:

* SEAM/esSEAM/stkSEAM can be equally delegated and used for governance.&#x20;
* Delegation **does not** transfer token ownership, it only grants “Voting Power” to the delegated address.
* SEAM tokens held within wallets that have not yet performed delegation **do not** have voting power and therefore cannot participate in Seamless Protocol governance (i.e. proposals and voting). Even for someone wishing to vote themselves, users must delegate to their own address.
* Delegation may benefit users seeking governance participation without the continuous responsibility of direct involvement or technical expertise, much like voting to elect a local government representative who handles policy issues full-time.

### **How to delegate voting power**

Within the Seamless Protocol app, users can navigate to the [Governance Tab](https://app.seamlessprotocol.com/#/governance) to delegate their SEAM and active voting power.&#x20;

Once on the Governance Tab and with a wallet connected to the app, users will see the amount of SEAM/esSEAM/stkSEAM in their wallet in the section on the left hand side of the app.&#x20;

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

Users can then click **Delegate** to properly delegate their SEAM/esSEAM/stkSEAM token voting power. In the modal pop up, users can enter a Recipient Address (EVM Wallet) and click **Delegate** and confirm the transaction in their walle&#x74;**.**

<figure><img src="/files/52MKZL53Hhs7mJL4KxbM" alt=""><figcaption></figcaption></figure>

As noted above, users can either self-delegate to their own address or delegate voting power to another address. You can view a list of **Seamless Community Representatives** who are active in the governance community and interested in receiving voting power in the [Seamless Governance Hub](https://seamlessprotocol.discourse.group/t/seamless-community-representatives/42).

At any moment users can **Revoke** delegation or Delegate their voting power to another Delegate.

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

### **How to become a Delegate**

All Base-compatible wallets are eligible to receive delegated voting power. To facilitate introductions among Seamless community members, the Seamless Governance Hub contains a thread named [Seamless Community Representative](https://seamlessprotocol.discourse.group/t/seamless-community-representatives/42) within the “General” section. If you’re interested in sharing why you’d be a reliable delegate, simply reply within the thread using the template provided.

When a token holder decides to delegate their SEAM tokens to your address, you gain their voting power and represent them in Seamless Governance.

**Crafting your Seamless Community Representative Pitch**\
Before creating your reply, it is important to prepare these key items. Please craft your response including the following information:

* A valid ETH Address OR ENS name:
* Discord username:
* Your reasons for wanting to be a delegate:
* Your Web3 interests:
  * Airdrop/Incentive miner (tries many new protocols, seeking rewards)
  * Liquidity Provider (lending, providing liquidity to DEXs, etc)
  * HODLer (long term holder/investor, not actively trading)
  * Speculator (actively trading or exchanging assets)
  * Skeptic (looking for sustainable yield/high concentration of stables)
  * Voter/Governor (active DAO governance participator)
  * Dev/Engineer (technical contributor to project(s))
  * Other
* Your qualifications/skills – Please share details of your involvement in web2 and web3 projects, etc.
* Additional links:
  * GitHub:
  * Twitter:
  * Additional URL or blog:
* Confirmation that you are:
  * Willing and able to participate in governance of the protocol if there is a DAO in the future.
  * Aware that this would be an ongoing role that requires active participation
  * Aware that being a delegate is an unpaid volunteer position
  * Aware that the work of a delegate is a significant commitment

Be sure to format your post clearly and answer all potential questions that members of the Seamless community might have. Do your best to follow the community-created template—keep in mind that you must include the wallet address that will receive the delegated Voting Power.


---

# 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.seamlessprotocol.com/governance/delegation-the-key-to-voting.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.
