> For the complete documentation index, see [llms.txt](https://suidex.gitbook.io/suidex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://suidex.gitbook.io/suidex/victory-token/xvictory.md).
# xVictory
### 🔒 How Locking Works
When you lock your **Victory tokens**, you reduce circulating supply and earn rewards based on your lock duration.\
The longer you lock, the higher your APR.
**Available Lock Options:**
* **1 Week:** Great for testing. Earns only **Victory emissions**, no SUI rewards.
* **3 Months:** Dual rewards in Victory and SUI.
* **1 Year:** High APR for committed holders in Victory and SUI.
* **3 Years:** Maximum APR for long-term believers om Victory and SUI.
### ⚙️ Reward Breakdown
**1️⃣ Victory Rewards — Continuous**
Distributed **every second** from the Victory emission schedule.\
These are ongoing and increase over time as more emissions shift toward lockers.
**2️⃣ SUI Rewards — Weekly Revenue Share**
Funded by **40% of all SuiDex farm deposit and withdrawal fees**, converted into SUI and sent to the locker.\
Distributed **weekly** from automated snapshots based on your locked balance and duration.
SUI rewards in lockers **will be eligible from the next epoch after locking**
> *Note:* **1-week locks do not earn SUI rewards**, only Victory emissions.
### 📈 Victory Emission Allocation to xVictory Over Time
Over time a higher percentage of emissions are rewarded to Victory stakers.
| Time Period | Victory Token Locker |
| ------------- | -------------------- |
| Weeks 1–4 | 17.5% |
| Weeks 5–12 | 23.5% |
| Weeks 13–26 | 32.5% |
| Weeks 27–52 | 40.5% |
| Weeks 53–104 | 47.5% |
| Weeks 105–156 | 52.5% |
By the end of the 3-year emission schedule, over half of all emissions flow to lockers.
### **Where do the Rewards Come From?**
The rewards you earn in the Token Locker are paid in **SUI and VICTORY**, sourced directly from Suidex v2 Classic fee structure and Emmision Split mechanics. Specifically, **40% of all deposit and withdrawal fees** from the v2 Classic pools are sold for SUI weekly and sent to the Token Locker. These funds are then distributed to VICTORY stakers based on their lock duration and the amount they’ve staked. The more activity in v2 Classic Farms—deposits, withdrawals, and trading on Suidex—the more SUI flows into the locker, boosting your rewards.
Our master chef contract not only provides SUI rewards but also distributes VICTORY tokens. By utilizing our Emission Split Model, the allocation of VICTORY tokens will increase gradually over time
### 💰 Why Lock Victory?
Locking Victory isn’t just yield — it’s impact.
You earn dual rewards, help stabilize token value, and share directly in platform revenue.
* **Victory rewards** paid per second.
* **SUI rewards** paid weekly.
* **1-week locks** receive Victory only.
* **Longer locks** earn higher APRs and both tokens.
The xVictory locker is where belief meets reward — a core pillar of the SuiDex ecosystem.
---
# 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://suidex.gitbook.io/suidex/victory-token/xvictory.md?ask=&goal=
```
`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.