# Using xTIDE ## What is $xTIDE? $xTIDE is a non-transferable governance and utility token you receive by swapping (wrapping) your $TIDE tokens. It unlocks access to: * **Revenue sharing** (30% of platform revenue) * **Premium features**, in-game perks (coming soon) * **Governance participation** (via Tally + OpenZeppelin Governor) * **Yield-style redistribution** during exits ## Convert $TIDE to $xTIDE 1. Go to the staking interface. 2. Choose the amount of $TIDE to convert. 3. Confirm the transaction. 4. You now hold $xTIDE in a 1:1 ratio. You’ll start earning: * Revenue share * Governance rights * Airdrop boosts > **Note:** $xTIDE is non-transferable, but supports a whitelist for use in airdrops, vesting contracts, and yield farms. ## Redeem $xTIDE Back to $TIDE (Vesting Exit) When you're ready to exit: 1. **Initiate Withdrawal:** * Select the amount of $xTIDE you wish to redeem. * This starts a vesting period. 2. **Vesting Options\*:** * **Immediate (Cliff Unlock):** 50% of $TIDE is released instantly. * **Linear Vesting:** Remaining 50% unlocks over 180 days (default). * Claimable at any time, based on elapsed time. 3. **Forfeit Early:** * If you claim tokens before full maturity: * 50% of the unvested amount is burned * 50% is redistributed to current $xTIDE holders > :warning: **Important:** > > * Each exit request creates a unique vesting position that can only be claimed once. Remaining tokens after claim are forfeited if not yet matured.
> * Once you request a withdrawal, you’re no longer the owner of those xTIDE, meaning you will be excluded from all benefits of holding xTIDE.
> > **\*At Launch:** > > * All $TIDE to $xTIDE swaps are 1:1 > * No vesting for initial conversions back to $TIDE (will be enabled later) ## Benefit from Redistributed Tokens When other users exit early: * Their forfeited tokens are redistributed to active $xTIDE holders * You must not have requested a withdrawal to receive redistribution > This rewards long-term holders and discourages early exits. ## Governance By holding $xTIDE, you can vote in DAO proposals. > DAO is available at: **Proposal Threshold: 125,000 $xTIDE** * This is the minimum number of $xTIDE votes required to create a proposal. * If a wallet (or group via delegation) doesn’t hold at least 125K $xTIDE in voting power, they cannot submit proposals. * Keeps spam/proposals low-quality ideas out of the system. \ **Quorum Required: 35%** * For a proposal to pass, at least 35% of all $xTIDE supply must vote on it. * It doesn't matter if votes are for or against — quorum is just about participation. * This ensures major decisions aren’t made by a tiny active minority. \ **Proposal Delay: 2 days** * After a proposal is submitted, it enters a 2-day delay before voting starts. * This gives the community time to review, discuss, and prepare to vote. * Useful for transparency and avoiding surprise proposals. \ **Voting Period: 3 days** * Once the delay ends, the community has 3 full days to vote on the proposal. * After this window closes, the votes are tallied and the proposal either passes (if quorum is met and the majority supports it) or fails. \ **Timelock Period: 1 day** * Once a proposal is accepted, it must way 1 day before it can be executed. * After this period ends, anyone can execute the proposal. > The multisig has the canceller role in the beginning and can cancel the execution of the proposal during this period. This is for safety reasons in the early days of the DAO and will be disabled later --- # 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.tideflow.com/tokenomics/using-xtide.md?ask= ``` 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.