> For the complete documentation index, see [llms.txt](https://docs.valantis.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valantis.xyz/stakedhype/stake-accounts.md).

# Understanding stHYPE

The stake accounts stHYPE uses on HyperCore, what each kind earns and gives up, and how withdrawals are served.

## Understanding stHYPE

stHYPE LST is a single unified Staking Protocol that coordinates several Stake Accounts on HyperCore.

**Fast-withdraw Stake Accounts** hold most of the protocol assets, optimized for throughput. These CoreWriter-enabled smart contracts can process up to twenty-five concurrent withdrawals, giving stHYPE higher unstaking throughput than competing LST protocols. Competing LST's five-concurrent-withdrawal limit creates delays between a user’s withdrawal request and the corresponding HyperCore unstake; stHYPE minimizes this delay to bring faster unstake times.

**Deployer Stake Accounts** are built to earn more by supporting Deployers. These Stake Accounts have slow withdrawal capacity, but help stHYPE's system earn higher than native staking yield by supporting deployers. These accounts are under stricter security over-sight (staked assets only moved under timelock); as their operations introduce Deployer Slashing Risk. All Deployer Accounts and associated risks are documented below. Deployer Account withdrawal-times are tracked in the Time-to-Cash Liquidity Waterfall.

**Valantis Prime Stake Accounts** are built to power cheaper trading. When stHYPE holders open a new Trading-Discount account; a new isolated Prime Stake Account is created by the stHYPE Protocol, and an equivalent amount of Native Stake owned by the stHYPE Protocol is moved there. This is what allows Prime to be fully self-custodial, and ensure Traders balances are never mixed or co-mingled with others.

{% hint style="info" %}
**Current status.** The USDe quote-asset module is the only active deployer stake account. The Ethena HyENA HIP-3 allocation is deprecated. The proposed HIP-4 deployer is not live.
{% endhint %}

Every account can only stake to HyperCore. None of them lend or rehypothecate.

### Accounts

* **Fast-withdrawal stake accounts (5)**
  * [Account 1](https://hyperevmscan.io/address/0x591540F231055743A37F691C3ffd50E4E53561ab)
  * [Account 2](https://hyperevmscan.io/address/0x16a4814e8eb502C56CeBD73f9c8AC7fDeE29C042)
  * [Account 3](https://hyperevmscan.io/address/0xf992Aa323eC183733213f874b6322B8bD1Aad625)
  * [Account 4](https://hyperevmscan.io/address/0x06b5659F16110319137220d1efd680053f5e72a2)
  * [Account 5](https://hyperevmscan.io/address/0xE787DD1347a29e6807d164C4Fa43105B64048556)
* **Deployer stake accounts (1)**
  * [Quote Asset Deployer Staking Module](https://hyperevmscan.io/address/0x358E783C32147B344a1168e0984D3350DE4e07cB) (USDe)
* **Prime stake accounts (>250)**

### Withdrawals

There is no fee to withdraw. In normal conditions a withdrawal targets about 7 days, and [the app](https://app.valantis.xyz/staking?tab=withdraw) shows an estimate for your amount before you confirm.

<figure><img src="https://986147118-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1hNJeG4CApeBcE2NlR61%2Fuploads%2Fgit-blob-fc943e1085ff296f837773c60514c0a1a34864f4%2Festimate_unstake_times.png?alt=media" alt="Estimated unstake times in the app for different withdrawal sizes"><figcaption><p>The estimate depends on the amount and on recent deposit flow.</p></figcaption></figure>

In normal conditions withdrawals are paid from two sources:

* **New deposits.** Every new HYPE deposit settles queued withdrawals before anything is staked, and the contracts enforce this. When deposits are flowing, withdrawals can settle faster than native unstaking.
* **The five standard accounts.** HyperCore allows one account five concurrent unstake requests and imposes a 24-hour lock after each re-delegation. Five accounts give stHYPE 25 concurrent unstakes and room to move stake between validators.

<figure><img src="https://986147118-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1hNJeG4CApeBcE2NlR61%2Fuploads%2Fgit-blob-5b354c9d23240e159c57ffe14160eb9d6e0ddc0a%2FGraphic%20B%20_%20Version%201.png?alt=media" alt="Five standard stake accounts running unstakes in parallel"><figcaption><p>Five standard accounts run unstakes in parallel, 25 at a time.</p></figcaption></figure>

### Large unwinds

* **Instant-redemption queue first.** The protocol targets approximately 10,000–50,000 HYPE in its instant-redemption queue, adjusted for market conditions. Actual available liquidity can be lower during withdrawals. [Dynamic Instant-Queue Announcement](https://x.com/stakedhype/status/2102002590586392987?s=20).
* **Fast-withdrawal accounts next.** When the Instant-redemption queue is empty, withdrawals are processed out of the fast-withdrawal accounts at unchanged capacity until those accounts are empty. Incoming deposits can settle queued withdrawals sooner, depending on deposit volume and the requests ahead in the queue.
* **Early recall from deployer accounts.** When fast-withdrawal and Valantis Prime stake accounts hold less than 10% of protocol funds, the protocol begins recalling deployer stake. Early recall prepares for liquidity pressure. Withdrawal timing still depends on available liquidity, queue demand, and each allocation’s release terms.
* **Withdrawals processed from deployer accounts.** When fast-withdrawal stake accounts are empty, remaining withdrawals may depend on stake committed to deployers. The documented recall periods range from 30 to 183 days; actual availability also depends on each allocation’s release conditions and the applicable HyperCore withdrawal process.

{% embed url="<https://986147118-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1hNJeG4CApeBcE2NlR61%2Fuploads%2Fgit-blob-11e0c824311b84e9c5a44a3617ec838833de349b%2Fsthype-withdrawal-times-vs-tvl.mp4?alt=media>" %}

Prolonged withdrawals remain possible if requests exceed what the standard accounts and new deposits can absorb. Restakers share these delegation-related withdrawal constraints with ordinary stHYPE holders, with an additional cooldown before claiming stHYPE.

## Slashing

Slashing is defined on Hyperliquid under validator quorum: [HIP-3 and HIP-4 rules](https://docs.valantis.xyz/stakedhype/restaking/deployer-stake.md) [Quote-Asset rules](https://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/permissionless-spot-quote-assets)

Deployer Stake accounts health is reported quarterly in [stHYPE Health Reports](https://docs.valantis.xyz/stakedhype/transparency-and-risks.md).

Live monitoring of Deployer Stake Accounts can be found at app.valantis.xyz/restaking

Which deployers receive stake, and how much, is decided through the Deployer Curation Process. [Restaked stHYPE](https://docs.valantis.xyz/stakedhype/restaking.md) is designed to be the capital that backs those commitments.
