> For the complete documentation index, see [llms.txt](https://docs.ventuals.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ventuals.com/vhype/points.md).
# Points
## Ventuals vHYPE points
Program start: Thursday October 16, 15:00 UTC
Snapshots: Every Thursday
Distributions: Every Friday
Emissions: 1M points per week
Eligibility: Hold vHYPE, the LST for Ventuals
Ventuals reserves the rights to change the points formulas at any time, or modify past point distributions at its sole discretion.
View your points here: [vhype.ventuals.com/points](https://vhype.ventuals.com/points)
## Points system
TLDR: The earlier you deposit to vHYPE, and the longer you stay in, the more points you will earn.
A fixed number of points per week are allocated to vHYPE depositors.
* 5M points allocated in the first week (Oct 16 – Oct 23)
* 1M points per week allocated in following weeks
During the week, you will earn 1 “stake-hour” per hour that you’ve had 1 HYPE staked.
At the end of the week:
1. The total number of stake-hours accrued that week are calculated
2. Multipliers are applied to stake-hours based on deposit tier
3. Points are distributed proportionally based on multiplier adjusted stake-hours
## Deposit tiers
| Deposit tiers | Stake-hour multiplier |
|---|
| Tier 1: 0-500K HYPE | 10x |
| Tier 2: 500K-600K HYPE | 6x |
| Tier 3: 600K-700K HYPE | 5x |
| Tier 4: 700K-800K HYPE | 4x |
| Tier 5: 800K-900K HYPE | 3x |
| Tier 6: 900K-1M HYPE | 2x |
| General Tier: 1M+ HYPE | 1x |
**Tier bumps:** Deposit tier multipliers incentivize the earliest deposits. When a withdrawal happens, other deposits are bumped up by deposit date, and start earning a higher multiplier.
* E.g. if a depositor in Tier 1 withdraws 10K HYPE, the earliest 10K HYPE deposits in Tier 2 get bumped up to Tier 1, the earliest 10K HYPE deposits in Tier 3 get bumped up to Tier 2, etc.
**Withdrawals:** Withdrawals are applied last-in-first-out (LIFO). This means that a user who has deposits spread across multiple tiers withdraws from the tier balance with the lowest multiplier first.
* E.g. if a depositor has 1,000 HYPE in Tier 1 and 500 HYPE in Tier 4, and they withdraw 250 HYPE, that HYPE will come out of the Tier 4 balance.
Queued withdrawals continue to earn native staking yield, but do not earn points. You may cancel your queued withdrawal at any time before it is processed.
**Transfers:** Transferring vHYPE will bump it down to the lowest available deposit tier. This is important to consider when sending or swapping vHYPE to other wallets, vaults, and AMM pools.
* E.g. if you have vHYPE in Tier 1, and there is currently 750K total HYPE in vHYPE, when you transfer your vHYPE to another wallet or contract, it will be bumped down to Tier 4.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ventuals.com/vhype/points.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.