# About Hyperbeat

Powered by Hyperliquid, Hyperbeat utilizes smart contracts to automate strategies that generate real and sustainable returns through Meta-Yield vaults, Delta-Neutral strategies, HYPE liquid staking, money-markets and onchain payment rails.\
\
We are early Hyperliquid users turned builders, that believe Hyperliquid represents a ground-breaking shift for onchain finance and is the biggest opportunity since Bitcoin and Ethereum.<br>

What Hyperbeat offers:

* [Liquid banking](/liquid-banking), a **modular, permissionless, fully on-chain financial stack**.
* [HYPE liquid staking](https://app.hyperbeat.org/staking/behype) built natively on Hyperliquid, enabling users to stake HYPE and receive [Hyperbeat x Ether.fi HYPE](/hyperbeat-staking/behype) (beHYPE) in return.
* [Earn](https://app.hyperbeat.org/vaults), smart-contract vaults generating real and sustainable returns through two types of vaults, [Meta Vaults](/hyperbeat-earn) that continuously optimize across HyperEVM and HyperCore. The vaults offer higher base yields through greater capital flexibility, manage risk and simplify the yield experience.
* [Mainnet validator node](/hyperbeat-staking), originally launched as a early testnet validator, today operating on mainnet in collaboration with P2P.org with [institutional staking support](/hyperbeat-staking/staking-api).


# Core contributors

Hyperbeat Labs is the core contributor dedicated to driving the growth of Hyperbeat. Our mission is to develop products that solve real problems in the Hyperliquid ecosystem.

\
We invite you to [join our community](https://discord.gg/hyperbeat) to ask questions, share feedback, and be part of the journey.


# Liquid banking

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

**Hyperliquid** pioneered a performant, fully on-chain central limit order book (CLOB) for **spot and perpetuals trading**, closing the gap with CEXs on depth, latency, and user adoption. What it didn’t natively offer was a way to **spend trading proceeds**, **hold yield-bearing balances**, or **off-ramp** directly from the trading environment.

Liquid Banking is custom built to solve exactly that, exclusively on Hyperliquid.

A **modular, permissionless, fully on-chain financial stack** powered by performant smart-contract modules that compose like building blocks to enable finance on-chain. Retain ownership, flexibility and speed as you experience **accounts, payments, credit, savings, trading, and on/off ramps** without middlemen.

Ownership, modularity and performance that makes “banking on-chain” possible, we call it **Liquid Banking.**


# Hyperbeat Pay

Hyperbeat Pay is a crypto-native card and credit product designed for Hyperliquid users. Whether you're earning from trading on Hyperliquid or generating yield in Hyperbeat vaults, Hyperbeat Pay gives you a simple way to:

{% stepper %}
{% step %}
Spend your USDC/T in real life
{% endstep %}

{% step %}
Take **credit** against your portfolio and spend without selling
{% endstep %}

{% step %}
Manage your spending securely — all on-chain
{% endstep %}
{% endstepper %}

Earn and Spend natively, anywhere Visa is accepted.

## How does it work?

Hyperbeat Pay is an integrated **crypto-to-card payment system** for the Hyperliquid ecosystem.

* Sign up
* Connect your wallet
* Configure Direct Pay or Credit mode
* Use your virtual or physical Hyperbeat Pay card anywhere Visa is accepted

## Who is Hyperbeat Pay for?

Hyperbeat Pay is designed for:

* Traders who want to spend trading profits directly
* Savers that want to spend from their yield not their capital
* Holders that want to spend on **credit** without parting from their holdings
* Builders and power users looking for a seamless onchain-to-real world spending experience

## Why Hyperbeat Pay?

* No more off-ramping headaches
* Keep your crypto productive while spending against it
* Fully integrated with your existing Hyperliquid, Unit and Hyperbeat&#x20;
* Crypto-native experience with credit and payments designed for DeFi users

{% hint style="success" %}
[Get started now](https://app.hyperbeat.org/pay)
{% endhint %}


# Liquid banking Architecture

Liquid Banking is built as a **modular, permissionless, fully on-chain financial stack**. Instead of a monolithic app with tightly coupled logic, the system is designed as a set of isolated smart-contract modules that compose like building blocks. These modules recreate the full spectrum of banking: **accounts, payments, credit, savings, trading, and ramps -** entirely on-chain, without requiring a bank, broker, custodian, or centralized exchange.

This modularity is what makes “banking on-chain” possible, we call it **Liquid Banking.**

#### Core Philosophy: Non-Custodial by Design

Unlike traditional crypto cards where you deposit funds into a centralized wallet, Hyperbeat utilizes a ManagementAccount architecture.

* You hold the keys: You are the `Owner` of your smart contract.
* You control the assets: Assets sit in your contract or your personal DeFi positions (e.g., Aave, Morpho).
* Permissioned Settlement: The Hyperbeat backend (`Operator`) is only authorized to settle card transactions up to a limit you define. The Operator **cannot** arbitrarily seize funds or withdraw assets to unauthorized addresses.

#### **2.** Architecture Overview

The system is built on a modular architecture to ensure security, upgradeability, and risk management.

<figure><img src="https://3024562909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSG3x6bYJ5NfrsGbUcU1X%2Fuploads%2FUGiSbrfAFieaIqaeeuvx%2FGraph2.png?alt=media&#x26;token=9a78b132-26b3-476c-9ce7-2f27046429f3" alt=""><figcaption></figcaption></figure>

**Key Components**

| **Component**              | **Description**                                                                                                                   |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| `ManagementAccount`        | The core user wallet. It holds assets, manages permissions, and executes DeFi interactions. Deployed as a UUPS upgradeable proxy. |
| `ManagementAccountFactory` | The central factory that deploys user accounts and enforces global parameters (e.g., protocol fees, timelocks).                   |
| `ServiceRegistry`          | A whitelist of approved DeFi adapters (e.g., Morpho, Aave) that users can interact with safely.                                   |
| `TokenWhitelistRegistry`   | A central registry of approved tokens to prevent interaction with                                                                 |

**2.1 Liquid Bank account: `ManagementAccount`**

At the core is the ManagementAccount, a non-custodial smart contract wallet deployed via the ManagementAccountFactory.

* **Role**: It acts as the user's on-chain identity and asset vault.
* **Modularity**: It does not contain hardcoded logic for specific DeFi protocols. Instead, it relies on a standardized `IService` interface to interact with external modules.
* **Upgradeability**: Built on the UUPS (Universal Upgradeable Proxy Standard) pattern, allowing the contract logic to be improved or patched without forcing users to migrate funds or change their address.

**2.2 Services: `ServiceRegistry`**

To enable "banking" features like savings or credit, the account connects to the ServiceRegistry. This registry acts as an on-chain "App Store" of verified adapters.

* **Function**: It maintains a whitelist of approved protocol adapters (e.g., `MorphoService` for lending/borrowing).
* **Security**: Users must explicitly `approveService` before a module can interact with their funds. This prevents a new, unvetted protocol from draining user assets.
* **Extensibility**: New financial products (e.g., a new yield source or a prediction market) can be added simply by deploying a new Service Adapter and registering it. The core wallet does not need to be upgraded.

**2.3 The Asset Layer: `TokenWhitelistRegistry`**

To protect the banking loop from malicious assets (e.g., spam tokens or "dust" attacks), the system utilizes a TokenWhitelistRegistry.

* **Function**: It defines which assets are valid for deposits, collateral, and settlement.
* **Settlement Token**: It enforces the validity of the specific stablecoin (e.g., `beatUSD` or `USDC`) used for card settlements.

#### 3. Operating Modes

The ManagementAccount adapts to your financial strategy via two distinct operating modes.

**💳 CASH Mode**

In this mode, you hold the settlement token directly in your ManagementAccount.

* Mechanism: Direct cash.
* Flow: When you swipe your card, the Operator calls `settle()` to deduct the specific amount from your account balance.
* Safety: You set a Spending Limit. The Operator cannot withdraw more than this allowance.
* Withdrawal Rules: Withdrawing the *settlement token* requires a cooldown and operator approval (to ensure no pending card swipes are unpaid). All *other tokens* can be withdrawn instantly.

**🏦 CREDIT Mode**

In this mode, you deposit assets into DeFi protocols (like Aave or Morpho) via your account.

* Mechanism: Collateralized Borrowing.
* Flow: When you swipe your card, the Operator is authorized to borrow the settlement token from the DeFi protocol on your behalf.
* Debt Management: You are responsible for managing your health factor and repaying the debt.
* Safety: The Operator acts as a delegate borrower only.
* Withdrawal Rules: Withdrawing *collateral* requires operator approval (to ensure the withdrawal won't cause liquidation or unpaid settlements).

<figure><img src="https://3024562909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSG3x6bYJ5NfrsGbUcU1X%2Fuploads%2Fxhc7u1rB3mH9opYNyXDv%2Fsett2.png?alt=media&#x26;token=6bfc2520-b54e-43b4-bf77-3aac90972403" alt=""><figcaption></figcaption></figure>

#### 4. Security Model

Liquid Banking is engineered around a **dual-control, non-custodial security model** that ensures user funds remain safe, unfreezable, and verifiable at all times. Unlike centralized banking systems where trust is placed in off-chain intermediaries, Liquid Banking enforces **cryptographic guarantees** around spending, borrowing, withdrawals, and mode changes each of which is governed by explicit on-chain rules.

**4.1 Separation of roles**

The core security innovation is the strict separation of powers between the Owner (You) and the Operator (Hyperbeat). The Operator is treated as a service provider, not a custodian.

* **Restricted Authority:** The Operator holds a restricted role (`OPERATOR_ROLE`). It cannot upgrade contracts, change global registries, or seize assets arbitrarily.
* **Settlement Allowance:** The Operator is "firewalled" by a spending limit you define. If you set a limit of $1,000, the Operator’s request to settle $1,001 will revert on-chain. This ensures that even if the Operator key were compromised, the attacker could not drain your entire wallet.
* **Debt Isolation:** In Credit Mode, the Operator acts only as a delegate borrower. It cannot withdraw your collateral to an external address; it can only execute specific `borrow` actions to pay a merchant.

**4.2 Timelocks & Anti-Race Conditions**

Blockchain transactions and real-world card swipes happen at different speeds. To prevent "race conditions" (where a user might try to withdraw funds immediately after swiping a card but before the settlement processes), we enforce mandatory delays for critical actions.

* **Settlement Token Withdrawals:** In Spending Mode, withdrawing the settlement token requires a 2-step process with a cooldown (default: 1 day). This gives the Operator time to verify that all card transactions have settled before releasing the funds.
* **Mode Switching:** Switching from Credit to Spending mode also enforces a timelock. This ensures a user cannot swipe a card using credit and then immediately switch modes to evade settlement.
* **Collateral Safety:** Withdrawals of collateral in Credit Mode require Operator approval to confirm that the withdrawal will not result in bad debt or unpaid card transactions.

**4.3 Registry-Based Safety (Whitelists)**

To protect users from "dust attacks," spam tokens, or malicious protocol interactions, the system utilizes centralized, audited registries.

* Token Whitelisting: The `TokenWhitelistRegistry` ensures that the account can only interact with verified assets. You cannot accidentally interact with a malicious token contract that might try to exploit your wallet.
* Service Vetting: The `ServiceRegistry` acts as a gatekeeper. Users can only connect their accounts to DeFi protocols (like Aave or Morpho) that have been audited and explicitly added to the registry by the protocol admin.

**4.4 Access Control & Upgrades**

The system is built to evolve without breaking security invariants.

* **UUPS Upgradeability:** We use the Universal Upgradeable Proxy Standard (UUPS). This allows us to patch vulnerabilities or add features to the logic contract without moving your funds. However, upgrades are strictly gated by the `UPGRADER_ROLE` and limited to implementations whitelisted by the factory.
* **Role-Based Access Control (RBAC):** Every function is protected by specific roles (`OWNER`, `OPERATOR`, `SERVICE_ADMIN`, `TOKEN_ADMIN`). This granularity ensures that a compromise in one part of the system (e.g., the service registry) does not automatically grant access to user funds

#### 5. Key management

Liquid Banking uses Turnkey to provide secure, non-custodial key management without seed phrases, browser extensions, or custodial wallets. Turnkey generates and protects each user's on-chain signing key, which becomes the Owner of their ManagementAccount. This means users, not Hyperbeat, control the smart contract that holds all assets.

Turnkey never has custody of funds. It enforces policy-based signing, which requires every user signature to follow strict rules. Examples include allowing a key to interact only with the user’s ManagementAccount or preventing token transfers without explicit approval. These policies protect users even if a device or session token is compromised.

For convenience, Turnkey issues session keys. These are short-lived, limited-permission keys that allow users to trade, view balances, or interact with approved services without exposing their main private key. Session keys cannot move assets or change account permissions.

Turnkey also supports secure, non-custodial recovery through passkeys, hardware keys, and social recovery. Users can regain access to their account without involving Hyperbeat or any third party.

In simple terms: Turnkey protects the keys, the ManagementAccount protects the assets, and the Operator can only perform actions that the user has explicitly authorized.

#### 6. Audits

The Liquid bank has undergone multiple audits by leading auditing firms:

* [Zellic](https://github.com/0xhyperbeat/Audits/tree/main/liquid-bank)
* [Nethermind](https://github.com/0xhyperbeat/Audits/tree/main/liquid-bank)


# USD+

USD+ is a yield-generating savings vault built for [Liquid Banking](/liquid-banking) that automatically allocates your stablecoins across actively managed lending markets to generate optimized yields.&#x20;

### How It Works

1. **Deposit** USDC or beatUSD into USD+
2. **Automatic allocation** spreads funds across multiple lending markets
3. **Continuous optimization** rebalances every 15-60 minutes
4. **Earn yields** from organic borrowing demand
5. **Withdraw anytime**

### Safety Features

* **85% utilization cap** prevents liquidity crises
* **Multi-protocol diversification** eliminates single points of failure
* **Balanced allocations** reduce liquidation risk
* **24/7 automated monitoring** responds to market changes

### Yield Sources

All returns come from real borrowing demand - no artificial incentives. Borrowers on Liquid Banking Credit pay interest to use your stablecoins as liquidity, and you earn a share of that interest.

### Key Benefits

* No active management required
* [Audited](/resources/audits)
* Transparent real-time allocations
* Withdraw anytime with maintained liquidity buffers


# Architecture

USD+ is a yield-generating vault token on HyperEVM that allocates stablecoins across multiple lending protocols.

### Core Components

#### User-Facing

* **Depositor**: Accepts USDC/BeatUSD deposits, mints USD+ shares
* **Withdrawal Queue**: Manages queued withdrawals with rate protection, burns USD+ shares

#### Capital Management

* **Deposit Receiver**: Holds idle capital, provides withdrawal liquidity
* **Morpho V2 Orchestrator**: Allocates funds between the two lending markets, handles USDC <> BeatUSD conversions

#### Pricing & Accounting

* **Pricer**: Manages exchange rates between USD+ and underlying assets
* **Exchange Updater**: Calculates NAV from positions across both markets
* **Accountant**: Tracks fees and vault accounting

### Investment Strategy

USD+ deploys capital across multiple lending protocols on HyperEVM to maximize risk-adjusted yield.

#### Morpho Markets (BeatUSD lending)

| Market            | Collateral | Link                                                                                                                              |
| ----------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------- |
| WWHYPE / BeatUSD  | WWHYPE     | [View](https://app.morpho.org/hyperevm/market/0x063ad132f8637cfad29660f8c28a522d63af268bb7bcbbab92c28a28d6b6090e/wwhype-beatusd)  |
| WBEHYPE / BeatUSD | WBEHYPE    | [View](https://app.morpho.org/hyperevm/market/0xda35ec213f5d27609210fd14f148dee5e84bbec87dd79e893df4dca18bf07cac/wbehype-beatusd) |
| WUBTC / BeatUSD   | WUBTC      | [View](https://app.morpho.org/hyperevm/market/0x3614200586f926ce2f712f60ff01270d19cb930369c1f81f3160adf1bdcbcf0d/wubtc-beatusd)   |
| WUETH / BeatUSD   | WUETH      | [View](https://app.morpho.org/hyperevm/market/0x41fc21455f4890fa3d680a5433ab780360f31e6d4a53cdca282a53a3b8cb45d6/wueth-beatusd)   |
| WUSOL / BeatUSD   | WUSOL      | [View](https://app.morpho.org/hyperevm/market/0x520dc6596ad9dc2a5c21bde2f35e38ed48179ee38916e418cc505101a2ceeca5/wusol-beatusd)   |
| WXAUT0 / BeatUSD  | WXAUT0     | [View](https://app.morpho.org/hyperevm/market/0x63c34750ab0b0b204d236f3e103d8477c9737710a065b1a40c8e126ddcd2cbd7/wxaut0-beatusd)  |

#### USDC Lending Protocols

<table><thead><tr><th width="254.79998779296875">Protocol</th><th>Address</th></tr></thead><tbody><tr><td>Hypuur</td><td><code>0x8667f088827a6ae1e2c2a865c675ca4fbc9d2ff0</code></td></tr><tr><td>Hyperlend</td><td><code>0xacBf6aCB842Ed0534ba8eBf06B7C8C9cE7356f9a</code></td></tr><tr><td>Felix Market</td><td><code>0x97395DDA5127ecf7BdBe2Adc1BCC2fb4A5A046FA</code></td></tr></tbody></table>

#### Why multiple markets?

* Diversification across collateral types and protocols reduces concentration risk
* BeatUSD markets earn yield before being lent (double yield layer)
* USDC is deployed across Hypuur, Hyperlend, and Felix for additional yield sources
* Active rebalancing optimizes risk-adjusted returns across all positions

### Access Control

Role-based permissions via MultiRolesAuthority:

* `ALLOCATOR_ROLE`: Deploy funds across markets
* `KEEPER_ROLE`: Update exchange rates
* `SOLVER_ROLE`: Process withdrawals

No single role can access user funds directly.

### Flow Summary

```
Deposit → Deposit Receiver → Orchestrator → Morpho Markets → Yield
Withdraw → Queue (rate-protected) → Solver processes → Assets returned
```


# Frequently Asked Questions

**When do I start earning?** Immediately. As soon as you receive USD+ tokens, you're earning yield from both lending markets.

**Do I need to claim yield?** No. Yield is built into the exchange rate—your USD+ tokens automatically increase in value. You realize gains when you withdraw.

**What APY can I expect?**

* USDC market: 4-6%
* BeatUSD market: 5-10%
* Blended vault APY: typically 5-8%

Rates vary with market conditions.

### Withdrawals

**How long do withdrawals take?**&#x20;

Typically 1 day. Create a request, solver processes within 24 hours, assets sent to your wallet.

**Are there withdrawal fees?**&#x20;

No. Queued withdrawals are completely free.

**What if the rate drops while pending?**&#x20;

You're protected. Your minimum rate is locked at request creation. If rates drop below your minimum, the request is rejected and you get your USD+ back.

### Tokens & Transfers

**Why no instant withdrawals?**&#x20;

To maximize yields (no idle reserves), eliminate fees, and ensure fairness through rate protection.


# Contracts

### Core Contracts

{% hint style="info" %}
[USD+ is fully audited](https://github.com/0xhyperbeat/Audits)
{% endhint %}

| Contract                   | Address                                      | Purpose                        |
| -------------------------- | -------------------------------------------- | ------------------------------ |
| **USD+ Token (masterUSD)** | `0x9065E3153B1393Bb5f76520cdc1e08E49eb04B03` | ERC20 vault share token        |
| **Depositor**              | `0xCa62d749d3Aa4f32445685F7EFaD2AB9451Fc87F` | Accepts deposits, mints shares |
| **WithdrawalQueue**        | `0x6E0b9AFaAe09A3479CFb7e923E15c05a9B23850d` | Manages queued withdrawals     |
| **DepositReceiver**        | `0x3B66712B3CA873C5CC0FdC54357FfcfE583CE896` | Holds idle capital             |

### Asset Management

| Contract                 | Address                                      | Purpose                     |
| ------------------------ | -------------------------------------------- | --------------------------- |
| **MorphoV2Orchestrator** | `0x8600111281e7e203779cAA868da6c4aCb72abad5` | Allocates to Morpho markets |
| **Orchestrator Impl**    | `0x6Ed6944E2FC8becdaCfA4F940f94f117E94a2A95` | Implementation contract     |

### Pricing & Accounting

| Contract                | Address                                      | Purpose                  |
| ----------------------- | -------------------------------------------- | ------------------------ |
| **Pricer**              | `0x5362454e5648C6Ac7F03969E8a62CFc61F99b9D6` | Exchange rate management |
| **ExchangeRateUpdater** | `0x58319A3d74ac0722B7BE0BF168dEc3773d01319f` | NAV calculation          |
| **PriceProvider**       | `0x68E0Dd9433c300D272B9767a3b3208f9f589CaAb` | BeatUSD price feed       |

### Access Control

| Contract                | Address                                      |
| ----------------------- | -------------------------------------------- |
| **MultiRolesAuthority** | `0x1fa2dceBC92B1Af6030C387ab486C34549a4a971` |

### Morpho Market Integrations

| Market                   | Address                                      |
| ------------------------ | -------------------------------------------- |
| **USDC Morpho Vault V2** | `0x818a0ee5165cbb011D6d537578744bC1E90BD433` |
| **BeatUSD Morpho V2**    | `0x29A2A9E2FAB2131A1749B14E1A006E7EeF2B8b41` |

### BeatUSD Lending Markets

All markets use beatUSD (`0x669abe85F96a9e3B34723F7Be9bC6F250aBC0Cc1`) as loan token with 62.5% LLTV.

| Collateral  | Market ID          |
| ----------- | ------------------ |
| **wWHYPE**  | `0x063ad1...6090e` |
| **wbeHYPE** | `0xda35ec...07cac` |
| **wUBTC**   | `0x361420...bcf0d` |
| **wUETH**   | `0x41fc21...b45d6` |
| **wUSOL**   | `0x520dc6...eeca5` |

### Quick Reference

* **Deposits**: `0xCa62d749d3Aa4f32445685F7EFaD2AB9451Fc87F`
* **Withdrawals**: `0x6E0b9AFaAe09A3479CFb7e923E15c05a9B23850d`
* **Core Operations**: `0x8600111281e7e203779cAA868da6c4aCb72abad5`


# Beatpot

The first decentralised raffle system on Hyperliquid with [provable fairness](/beatpot/provable-fairness). BeatPot ensures transparency, fairness, and accessibility, allowing participants to enter and verify the outcomes of raffles entirely onchain.

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

{% hint style="info" %}
[Get started with the BeatPot here](https://app.hyperbeat.org/pay)
{% endhint %}


# How it works

Each BeatPot round follows a predictable cycle:

#### Active Round (24 Hours)

During the active period:

* Players can purchase tickets
* Up to 1,500 players can participate per round
* Backers can deposit or request withdrawals
* The prize pool grows with each ticket purchase

#### Round Execution

When the round timer ends, anyone can trigger the round execution:

{% stepper %}
{% step %}

#### Execute Round

A transaction is sent to end the current round.
{% endstep %}

{% step %}

#### Request Randomness

The contract requests a random number from Pyth Entropy.
{% endstep %}

{% step %}

#### Callback

Pyth Entropy returns the verifiable random number.
{% endstep %}

{% step %}

#### Winner Selection

The random number determines the winning ticket.
{% endstep %}
{% endstepper %}

#### Settlement

After winner selection:

* Winner can claim their prize&#x20;
* Backers' withdrawal requests are processed
* A new round automatically begins

### Winner Selection

The winner is chosen using verifiable randomness from Pyth Entropy.

{% hint style="info" %}
**How winner selection works**

Think of all tickets as numbered entries in a giant list. If 1,000 tickets are sold:

* Ticket 1-100 might belong to Player A (who bought 100 tickets)
* Ticket 101-150 might belong to Player B (who bought 50 tickets)
* And so on...

The random number points to one specific ticket number. Whoever owns that ticket wins.

This means:

* More tickets = better odds
* Every ticket has an equal chance
* The outcome is completely determined by the random number
  {% endhint %}

### Fee Flow

When tickets are purchased, fees are distributed automatically:

* **\~85%** enters the prize pool (available for winner)
* **\~10%** goes to backers as liquidity provider rewards
* **5%** goes to referrer (if a referral link was used)
* **\~1%** goes to the protocol (portion of backer fee)

### The Backer Vault

The backer vault is the heart of BeatPot's prize system:

* **Deposits**: Backers add WHYPE, receive BPLPT shares
* **Prizes**: Winner payouts come from the vault
* **Fees**: Backer fees flow into the vault
* **House Wins**: When no player wins, entries go to the vault

#### Exchange Rate

The BPLPT share price reflects vault performance:

* **Price increases** when: fees accumulate, house wins occur
* **Price decreases** when: large player wins are paid out

This creates a dynamic system where backers share in both the upside and downside of raffle outcomes.

### Withdrawal Queue

Backer withdrawals use a queue system:

{% stepper %}
{% step %}

#### Request

Backer submits withdrawal request.
{% endstep %}

{% step %}

#### Queue

Request is added to the withdrawal queue.
{% endstep %}

{% step %}

#### Round End

When the current round ends, requests are processed.
{% endstep %}

{% step %}

#### Claim

Backer claims their WHYPE at the final exchange rate.
{% endstep %}
{% endstepper %}

This ensures all backers are treated fairly—no one can exit before knowing the round outcome.

### Timing Considerations

| Event            | When                                   |
| ---------------- | -------------------------------------- |
| Round duration   | 24 hours                               |
| Ticket purchases | Anytime during active round            |
| Round execution  | After timer ends (triggered by anyone) |
| Winner selection | Immediately after randomness callback  |
| Prize claim      | Anytime after selection                |
| Withdrawal claim | After round ends                       |

### What Happens If No One Plays?

If a round ends with zero tickets sold:

* No winner is selected
* No prize is paid
* Backers' positions remain unchanged
* A new round begins


# Provable fairness

BeatPot uses verifiable on-chain randomness to ensure every raffle is completely fair. No one can predict or manipulate the outcome.

### What Does "Provably Fair" Mean?

Provably fair means you don't have to trust anyone. The randomness used to select winners can be verified by anyone, and the selection process is transparent and deterministic.

Unlike traditional raffles where you trust the operator, BeatPot's fairness is guaranteed by cryptography and smart contracts.

### How Randomness Works

BeatPot uses [**Pyth Entropy**](https://www.pyth.network/entropy) for verifiable randomness.

#### The Process

{% stepper %}
{% step %}

#### Round Ends

When a round timer expires, execution is triggered.
{% endstep %}

{% step %}

#### Request Randomness

The BeatPot contract requests a random number from Pyth Entropy.
{% endstep %}

{% step %}

#### Generate Random Number

Pyth Entropy generates a verifiable random number.
{% endstep %}

{% step %}

#### Callback

The random number is sent back to the BeatPot contract.
{% endstep %}

{% step %}

#### Select Winner

The random number determines which ticket wins.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**What is Pyth Entropy?**

Pyth Entropy is a decentralized randomness service. It generates random numbers that:

* Cannot be predicted before they're revealed
* Cannot be manipulated by any party
* Can be verified by anyone after the fact

This is achieved through cryptographic commitments—values are committed before the outcome is needed, making manipulation impossible.
{% endhint %}

### Verification

Anyone can verify past raffle results:

#### On-Chain Verification

{% stepper %}
{% step %}

#### Find the round

Find the round you want to verify on HyperEVMScan.
{% endstep %}

{% step %}

#### Look at the event

Look at the `WinnerSelected` event.
{% endstep %}

{% step %}

#### Check the random number

Check the random number used.
{% endstep %}

{% step %}

#### Verify source

Verify that the random number came from Pyth Entropy.
{% endstep %}

{% step %}

#### Confirm selection

Confirm the winner was selected correctly based on that number.
{% endstep %}
{% endstepper %}

#### What You Can Verify

* The random number used for each round
* That the random number came from Pyth Entropy (not generated internally)
* That the winner selection matched the random number
* The total number of entries and who owned each range

### Why This Matters

#### Traditional Raffles

* You trust the operator
* No way to verify the draw
* Operator could theoretically cheat

#### BeatPot

* No trust required
* Every draw is verifiable
* Cheating is mathematically impossible

### Common Questions

<details>

<summary>Can the BeatPot team manipulate results?</summary>

No. The random number comes from Pyth Entropy, which BeatPot cannot control. The selection process is deterministic based on that random number.

</details>

<details>

<summary>Can someone predict the winner before the round ends?</summary>

No. The random number doesn't exist until after the round ends and randomness is requested.

</details>

<details>

<summary>What if there's a bug in the selection code?</summary>

The smart contract code is verified and visible on HyperEVMScan. Anyone can review it to ensure the selection logic is correct.

</details>

<details>

<summary>Can miners/validators manipulate the outcome?</summary>

Pyth Entropy's design prevents this. The randomness is generated through a commit-reveal scheme that makes manipulation impractical.

</details>


# Guaranteed Prizes

We wanted to make every round more exciting for everyone, not just the jackpot winner.

**Guaranteed Prizes** are bonus rewards distributed to multiple players after each round. These prizes come from the BeatPot treasury and are separate from the main jackpot.

Think of it this way:

* **Main Jackpot**: One big winner takes all if there is a winning ticket in that round
* **Guaranteed Prizes**: Multiple players win smaller prizes ever round

This means more chances to win something every round.

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

## How It Works

#### 1. Play a Round

Buy tickets in any BeatPot round as you normally would. Each ticket you purchase increases your chances of winning both the main jackpot AND guaranteed prizes.

#### 2. Round Completes

After the round ends and the main winner is determined, the guaranteed prize distribution begins.

#### 3. Winners Selected

Multiple players are randomly selected to receive guaranteed prizes. The more tickets you hold, the higher your chances of being selected.

#### 4. Prizes Distributed

Winners receive their WHYPE tokens directly to their wallets via an on-chain transaction.

***

### Who Can Win?

To be eligible for guaranteed prizes:

* **Buy tickets** in the round (minimum threshold required)
* **Not be the main jackpot winner** (we spread the love - jackpot winners are excluded from guaranteed prizes)
* **One prize per wallet** per round

#### Fair Selection

Winners are selected using weighted random selection:

* More tickets = higher chance of winning
* But even small ticket holders have a chance
* Selection is provably fair using on-chain randomness

***

### Adaptive Prize Pool

The guaranteed prize pool is **adaptive** - it learns and adjusts based on player activity over time.

#### How It Adapts

* **Higher participation** → Prize pool increases to reward the community
* **Lower participation** → Prize pool adjusts conservatively
* **Learning system** → The algorithm tracks how prizes affect participation and optimizes over time

This means the system automatically finds the sweet spot that maximizes rewards for players while keeping the prize pool sustainable.

#### What This Means For You

* Prize amounts aren't fixed - they grow with the community
* More players = bigger prize pools
* The system rewards active rounds with better prizes

***

### Why Guaranteed Prizes?

#### For Players

* **More winners every round** - Even if you don't hit the jackpot, you could still win
* **Better odds** - Multiple prize slots means more chances
* **Instant payouts** - Prizes sent directly to your wallet

#### For the Ecosystem

* **Increased engagement** - More reasons to participate
* **Community rewards** - Spreads value across more players
* **Sustainable growth** - Funded from protocol treasury

***

### Frequently Asked Questions

#### How often are guaranteed prizes distributed?

After every completed BeatPot round. If you participated, you're automatically eligible.

#### Do I need to claim my prize?

No! Prizes are automatically sent to your wallet. Just make sure you're playing with the wallet where you want to receive prizes.

#### Can I win the main jackpot AND a guaranteed prize?

No. To keep things fair and spread rewards across more players, jackpot winners are excluded from guaranteed prizes in that round.

#### How are winners selected?

Using weighted random selection based on ticket holdings. More tickets = higher probability, but everyone with tickets has a chance.

#### What token are prizes paid in?

WHYPE - the native token on Hyperliquid EVM.

#### Is there a minimum to participate?

Even 1 ticket makes you eligible for guaranteed prizes!

#### How do I see if I won?

Check your wallet for incoming WHYPE transactions after round completion. Winners are also announced in our community channels.

***

### Get Started

Ready to try your luck? Head to [BeatPot](https://app.hyperbeat.org/beatpot) and join the next round. Buy tickets, enjoy the excitement, and you might just be one of our guaranteed prize winners!


# How to play

{% stepper %}
{% step %}

#### Connect Your Wallet

Visit the BeatPot app and click **Connect Wallet**. Make sure you're on the HyperEVM network.
{% endstep %}

{% step %}

#### Approve WHYPE (First Time Only)

If this is your first time playing, you'll need to approve BeatPot to use your WHYPE tokens. This is a one-time transaction that allows the smart contract to accept your ticket purchases.
{% endstep %}

{% step %}

#### Buy Tickets

* Choose how many tickets you want to buy
* Each ticket costs **0.1 WHYPE**
* Confirm the transaction in your wallet

You can buy multiple tickets to increase your chances of winning. There's no limit on how many tickets you can purchase per round.
{% endstep %}

{% step %}

#### Wait for the Round to End

Each round lasts **24 hours**. You can see the countdown timer on the app showing when the current round ends.

During this time:

* View your entries for the current round
* See how many total tickets have been sold
* Check the current prize pool size
  {% endstep %}

{% step %}

#### Winner Selection

When the round ends:

* Anyone can trigger the round execution
* The smart contract requests randomness from Pyth Entropy
* A winner is selected based on the random number
* The more tickets you have, the better your odds

{% hint style="info" %}
**How winner selection works**

Think of it like a raffle where each ticket is a numbered entry. The random number determines which ticket number wins. If you bought 10 tickets out of 100 total, you have a 10% chance of winning.

All randomness is verifiable on-chain, so no one can manipulate the outcome.
{% endhint %}
{% endstep %}

{% step %}

#### Claim Your Prize

If you win:

1. You'll see a notification in the app
2. Click **Claim Prize** to withdraw your winnings
3. Confirm the transaction
4. Your prize is sent to your wallet
   {% endstep %}
   {% endstepper %}

### Tips for Players

* **Buy more tickets** to improve your odds
* **Use a referral link** if someone shared one with you—it doesn't cost you anything extra
* **Check past rounds** to see previous winners and prize amounts
* **Verify fairness** anytime by checking the on-chain randomness

### Fee Breakdown

When you buy a ticket for 0.1 WHYPE:

* **85%** goes to the prize pool
* **10%** goes to backers (liquidity providers)
* **5%** goes to the referrer (if you used a referral link)


# How to provide liquidity

Backers are the liquidity providers who fund BeatPot's prize pool. By depositing WHYPE, you earn a share of ticket fees while supporting the raffle ecosystem.

### What is a Backer?

A backer is someone who deposits WHYPE into the BeatPot vault. Your deposit:

* Funds the prize pool for player winnings
* Earns you approximately **10% of all ticket fees**
* Is represented by **BPLPT shares** (BeatPot Liquidity Provider Token)

### How It Works

When you deposit WHYPE, you receive BPLPT shares representing your portion of the vault. The value of these shares changes based on raffle outcomes:

* **When the house wins** (no player wins): Your shares increase in value because player entries flow into the vault
* **When a player wins**: Your shares decrease in value because the prize is paid from the vault

Over time, the fee income from ticket sales is designed to offset player wins and generate returns for backers.

{% hint style="info" %}
**Understanding share value**

Think of it like owning a percentage of a pool. If the pool grows (from fees and house wins), your percentage is worth more. If the pool shrinks (from paying out winners), your percentage is worth less.

The exchange rate between WHYPE and BPLPT reflects this—it goes up when the vault profits and down when it pays out prizes.
{% endhint %}

### Step-by-Step Guide

{% stepper %}
{% step %}

#### Connect Your Wallet

Visit the BeatPot app and connect your wallet to HyperEVM.
{% endstep %}

{% step %}

#### Navigate to the Backer Section

Find the "Provide Liquidity" or "Backer" section in the app.
{% endstep %}

{% step %}

#### Approve WHYPE (first time only)

If this is your first deposit, approve BeatPot to use your WHYPE tokens.
{% endstep %}

{% step %}

#### Deposit WHYPE

Follow the deposit steps to receive BPLPT shares.

{% stepper %}
{% step %}

#### Enter amount

Enter the amount of WHYPE you want to deposit.
{% endstep %}

{% step %}

#### Review exchange rate and shares

Review the current exchange rate and shares you'll receive.
{% endstep %}

{% step %}

#### Confirm transaction

Confirm the transaction in your wallet.
{% endstep %}

{% step %}

#### Receive BPLPT

Receive BPLPT shares in your wallet.
{% endstep %}
{% endstepper %}
{% endstep %}

{% step %}

#### Track Your Position

After depositing, you can:

* View your BPLPT balance
* Check the current exchange rate
* See your estimated WHYPE value
* Monitor vault performance
  {% endstep %}
  {% endstepper %}

### Withdrawing Your Funds

{% hint style="warning" %}
**Important:** Withdrawals are not instant. You must request a withdrawal and wait for the current round to end before claiming.
{% endhint %}

#### How the Withdrawal Queue Works

{% stepper %}
{% step %}

#### Request Withdrawal

Submit a withdrawal request for some or all of your BPLPT shares.
{% endstep %}

{% step %}

#### Wait for Round End

Your request is queued until the current round completes.
{% endstep %}

{% step %}

#### Claim Your WHYPE

After the round ends, claim your WHYPE based on the final exchange rate.
{% endstep %}
{% endstepper %}

This process ensures fair treatment of all backers and prevents withdrawal front-running before winner selection.

#### Withdrawal Steps

{% stepper %}
{% step %}

#### Go to withdrawal section

Go to the withdrawal section in the app.
{% endstep %}

{% step %}

#### Enter shares to withdraw

Enter how many BPLPT shares to withdraw.
{% endstep %}

{% step %}

#### Confirm request

Confirm the withdrawal request.
{% endstep %}

{% step %}

#### Wait for round end

Wait for the current round to end.
{% endstep %}

{% step %}

#### Claim WHYPE

Return to claim your WHYPE after the round completes.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Why the withdrawal delay?**

The delay protects all backers from unfair behavior. Without it, someone could:

* Deposit right before a likely house win
* Withdraw right before a likely player win

By requiring withdrawals to process after the round ends, everyone shares equally in the outcome.
{% endhint %}

### Earnings

As a backer, you earn from:

* **Ticket fees**: Approximately 10% of every ticket sold goes to backers proportional to their share of the vault
* **House wins**: When no player wins, their entry amounts stay in the vault

Your earnings compound automatically—they're reflected in the increasing exchange rate of your BPLPT shares.

### Risks

Providing liquidity carries risks. Please read the [Risks page](https://hyperbeat.gitbook.io/hyperbeat-pay-docs/liquid-banking/beatpot/broken-reference) to understand:

* Exchange rate can decrease if players win large prizes
* Smart contract risk
* Withdrawal timing considerations


# Beatpot smart contract

BeatPot runs entirely on smart contracts deployed on HyperEVM. This page provides technical details for those who want to interact directly with the contracts or verify the code.

{% hint style="info" %}
[BeatPot is audited by Zellic](https://github.com/0xhyperbeat/Audits/blob/main/BeatPotV2%20-%20Zellic%20Audit%20Report.pdf)
{% endhint %}

### Contract Addresses

| Contract            | Address                                                                                                                    | Purpose                            |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
| **BeatPot**         | [`0x53f9715c91642da22ebdf6eaa45e86d5e94c8425`](https://hyperevmscan.io/address/0x53f9715c91642da22ebdf6eaa45e86d5e94c8425) | Main raffle contract               |
| **WithdrawalQueue** | [`0x7E89acFFAC47435778dd158Aa622A150de045e10`](https://hyperevmscan.io/address/0x7E89acFFAC47435778dd158Aa622A150de045e10) | Handles backer withdrawal requests |

### Key Functions

#### For Players

**purchaseEntries**

Purchase raffle tickets for the current round.

* Input: Number of entries to purchase, optional referrer address
* Cost: 0.1 WHYPE per entry
* Requires: WHYPE approval to the contract

#### For Backers

**backerDeposit**

Deposit WHYPE into the vault to become a liquidity provider.

* Input: Amount of WHYPE to deposit
* Returns: BPLPT shares based on current exchange rate
* Requires: WHYPE approval to the contract

**requestWithdrawal**

Request to withdraw your BPLPT shares.

* Input: Amount of BPLPT shares to withdraw
* Effect: Adds request to withdrawal queue
* Note: Withdrawal processes after current round ends

**claimWithdrawal**

Claim your WHYPE after withdrawal request is processed.

* Requires: Previous withdrawal request that has been processed
* Returns: WHYPE based on exchange rate at round end

#### For Referrers

**claimReferralFees**

Claim accumulated referral rewards.

* Returns: WHYPE referral fees to your wallet

### Share Token

* Name: BeatPot Liquidity Provider Token
* Symbol: BPLPT
* Type: ERC-20 compatible
* Purpose: Represents your share of the backer vault

### Verifying the Contract

{% stepper %}
{% step %}

#### Visit the contract page

Go to the contract address links above.
{% endstep %}

{% step %}

#### View verified source

Open the "Contract" tab to see verified source code.
{% endstep %}

{% step %}

#### Inspect interactions

Check the "Transactions" tab to see all interactions.
{% endstep %}

{% step %}

#### Review events

Review "Events" to see deposits, withdrawals, and winner selections.
{% endstep %}
{% endstepper %}

### Reading Contract State

Useful read functions:

| Function              | Returns                           |
| --------------------- | --------------------------------- |
| `getCurrentRound`     | Current round number and details  |
| `getEntries`          | Your entries for a specific round |
| `exchangeRate`        | Current WHYPE per BPLPT share     |
| `totalBackerDeposits` | Total WHYPE in backer vault       |

### Events

The contract emits events for all major actions:

* `EntryPurchased` - When tickets are bought
* `WinnerSelected` - When a winner is chosen
* `PrizeClaimed` - When a winner claims their prize
* `BackerDeposit` - When liquidity is added
* `WithdrawalRequested` - When a withdrawal is queued
* `WithdrawalClaimed` - When a withdrawal is completed

### Security

The BeatPot contracts:

* Are deployed on HyperEVM mainnet
* Use Pyth Entropy for verifiable randomness
* Implement withdrawal queuing to prevent front-running
* Have no admin functions that can steal funds

{% hint style="info" %}
**For developers**

If you're building integrations or want to interact programmatically:

1. Use the contract addresses above
2. Import the ABI from HyperEVMScan
3. Ensure WHYPE approval before deposits/purchases
4. Monitor events for real-time updates

The contracts follow standard Solidity patterns and should be familiar to anyone experienced with DeFi protocols.
{% endhint %}


# FAQs

### General

<details>

<summary>What is BeatPot?</summary>

BeatPot is a decentralized daily raffle built on HyperEVM. Players buy tickets for a chance to win prizes from a community-backed pool, while liquidity providers (backers) earn fees from ticket sales.

</details>

<details>

<summary>How much does a ticket cost?</summary>

Each ticket costs **0.1 WHYPE**.

</details>

<details>

<summary>How long does each round last?</summary>

Each round lasts **24 hours**. When the timer ends, a winner is selected using verifiable randomness.

</details>

<details>

<summary>How many players can participate per round?</summary>

Up to **1,500 players** can participate in each round.

</details>

### Playing

<details>

<summary>How do I buy tickets?</summary>

* Connect your wallet to the Beatpot
* Approve WHYPE spending (first time only)
* Choose how many tickets to buy
* Confirm the transaction

</details>

<details>

<summary>Can I buy multiple tickets?</summary>

Yes. You can buy as many tickets as you want. More tickets = better odds of winning.

</details>

<details>

<summary>How are winners chosen?</summary>

Winners are selected using [Pyth Entropy](https://www.pyth.network/entropy), a verifiable randomness service. The random number determines which ticket wins. Every ticket has an equal chance, and anyone can verify the fairness on-chain.

</details>

<details>

<summary>When can I claim my prize?</summary>

If you win, you can claim your prize anytime after the winner is announced. There's no time limit.

</details>

<details>

<summary>What happens to my money if I don't win?</summary>

Your ticket fees are distributed as follows:

* \~85% goes to the prize pool
* \~10% goes to backers
* 5% goes to referrers
* \~1% goes to the protocol

</details>

### Backing (Providing Liquidity)

<details>

<summary>What is a backer?</summary>

A backer is someone who deposits WHYPE into the vault to fund the prize pool. Backers earn approximately 10% of all ticket fees.

</details>

<details>

<summary>What is BPLPT?</summary>

BPLPT (BeatPot Liquidity Provider Token) represents your share of the backer vault. When you deposit WHYPE, you receive BPLPT shares.

</details>

<details>

<summary>How do I earn as a backer?</summary>

You earn from:

* Ticket fees (\~10% of all tickets sold)
* House wins (when no player wins, entries go to the vault)

Your earnings are reflected in the increasing value of your BPLPT shares.

</details>

<details>

<summary>Can I lose money as a backer?</summary>

Yes. When players win large prizes, the vault value decreases, which reduces your share value. Over time, fees are designed to offset player wins, but individual rounds can result in losses.

</details>

<details>

<summary>How do I withdraw my funds?</summary>

* Request a withdrawal for your BPLPT shares
* Wait for the current round to end
* Claim your WHYPE

You cannot withdraw instantly—withdrawals process after the round ends.

</details>

<details>

<summary>Why can't I withdraw immediately?</summary>

The withdrawal queue protects all backers from unfair behavior. Without it, someone could withdraw right before a player wins to avoid losses.

</details>

### Fees

<details>

<summary>What are the total fees?</summary>

Total fees are **15%** of ticket purchases:

* \~10% to backers (liquidity providers)
* 5% to referrers
* \~1% to protocol (portion of backer fee)

</details>

<details>

<summary>Do I pay more if I use a referral link?</summary>

No. The referral fee comes from the existing fee structure, not from your ticket price.

</details>

### Referrals

<details>

<summary>How do referrals work?</summary>

* Get your unique referral link from the app
* Share it with others
* Earn 5% of their ticket purchases
* Claim your rewards anytime

</details>

<details>

<summary>Is there a minimum to claim referral rewards?</summary>

No. You can claim any amount of accumulated referral fees.

</details>


# Hyperbeat Staking

{% hint style="success" %}
[Liquid stake HYPE with beHYPE](/hyperbeat-staking/behype)
{% endhint %}

{% hint style="success" %}
[Vanilla stake HYPE with Hyperbeat X P2P X Hypio](/hyperbeat-staking/vanilla-staking)
{% endhint %}


# beHYPE

When you stake HYPE, you receive beHYPE in return, allowing you to keep earning staking rewards while still using your beHYPE in DeFi.

Introducing beHYPE - the fully onchain HYPE Liquid Staking Token that lets you participate in validator governance. A modular HYPE money lego for:

* HYPE liquid staking.
* Validator driven governance.
* Slashable HYPE security.

{% hint style="success" %}
[Mint beHYPE here](https://app.hyperbeat.org/staking)
{% endhint %}

## Key benefits&#x20;

Liquid staking HYPE into beHYPE gives you the best of both worlds: you continue earning rewards on your staked tokens while unlocking liquidity to pursue new trading opportunities.

* **Network contribution:** Strengthens decentralization and helps secure the Hyperliquid network by delegating HYPE equally to all active validators in the set.
* **Unlocked liquidity:** Enables you to use beHYPE across HyperEVM in other DeFi strategies and trading opportunities.
* **Composability:** Serves as a building block for other protocols and applications (e.g., as collateral in lending markets, the spot let in [dnTokens](/delta-neutral-tokens-dntokens) or collateral on Hyperbeat Pay).&#x20;

## How to liquid stake HYPE for beHYPE

{% @arcade/embed flowId="RvpNJGZkaeeiN8gzrQLI" url="<https://app.arcade.software/share/RvpNJGZkaeeiN8gzrQLI>" %}

## Is beHYPE audited?

Yes, beHYPE has been audited by three independent auditors:

* [Nethermind](https://github.com/0xhyperbeat/Audits/blob/main/beHYPE/Nethermind.pdf)
* [Certora](https://github.com/0xhyperbeat/Audits/blob/main/beHYPE/Certora.pdf)&#x20;
* Pashov

<br>


# Architecture

## Interactions with HyperCore.

beHYPE leverages CoreWriter for all interactions with HyperCore including delegation management.

When a user stakes/unstakes with beHYPE, CoreWriter transfers their HYPE to/from the contract’s staking balance, interacting with HyperCore in a completely non-custodial way to transfer HYPE between HyperEVM and HyperCore.

This eliminates the need for a “middleman” account to hold custody of funds. All of the logic is fully implemented on-chain and therefore verifiable.

As Hyperliquid is still a young chain and slashing is not yet live, based on auditor feedback a keeper is in place to audit abnormal unstaking requests e.g. if slashing occurs, unstake requests trying to front run withdrawal pre-slashing can be slashed. This safety measure does not change redemption logic. The entire redemption logic remains transparent, auditable, and enforced by code.

## Stake delegation

Hyperliquid staking rewards are distributed once a day, Once HYPE is delegated, it starts earning block rewards, which are paid daily and compounded into the delegated position. To reflect this growth, the protocol needs to regularly update its record of total assets.

beHYPE uses CoreWriter for stake delegation, delegating once every 6 hours to maximise staking rewards.

Users are able to stake to the validator of their choice when staking. Particularly relevant for users eager to participate in governance via LSTs.

To do this users select one validator from the beHYPE active set to delegate their HYPE to using the UI. This adds a bytestring containing the name of their chosen validator in their mint transaction. Users choice is captured on-chain and stake is verifiably routed to their desired community validator using CoreWriter.

If a user does not want to choose their validator, their stake is delegated equally amongst all validators in the beHYPE active set.

## Exchange rate&#x20;

beHYPE state is updated through L1 Precompiles, with exchange rates are computed dependencies on off-chain data are eliminated.

A keeper runs twice a day, beHYPE calls the staking delegation Precompile so whenever anyone wants to know the protocol’s total assets they can call the read function “exchange rate” on the beHYPE contract to get its real-time exchange rate.

The call supplies an input equal to the staking rewards accrued since the previous rebase. How that reward figure is produced is verifiable on-chain, These metrics include the rewards earned, although slashing isn't live, the same mechanism is designed to handle any slashing events.

The state is updated twice a day, since rewards are distributed once a day this programmatically ensures the exchange rate reflects rewards and slashing in real time even if the reward distribution mechanism updates.

<br>


# Validator set

The beHYPE validator set is made up of all **active set** validators **excluding** the Hyperliquid Foundation nodes.&#x20;

{% @arcade/embed flowId="mFexuU8yB1uzFG4UeaT8" url="<https://app.arcade.software/share/mFexuU8yB1uzFG4UeaT8>" %}

{% hint style="success" %}
[View the beHYPE validator set here](https://app.hyperbeat.org/staking)
{% endhint %}

All validators in the beHYPE validator set are continuously audited to monitor, performance, reliability, engagement and more. If any community validator does not hit the benchmarks they will be removed from the beHYPE set with stake redistributed equally amongst the remaining validators in the set.

## How is stake split between validators in the set?&#x20;

beHYPE uses CoreWriter for stake delegation to delegate HYPE equally amongst all community validators in the beHYPE active set by default.&#x20;

## How often is stake rebalanced?

Delegations are rebalanced every 6-hours.&#x20;


# Builder codes

A comprehensive guide for developers looking to integrate beHYPE staking and unstaking functionality into their applications.

### Overview

beHYPE is a liquid staking token that represents staked HYPE tokens. Users can stake HYPE to receive beHYPE tokens, which continue to earn staking rewards while remaining liquid and transferable.

### Contract Addresses

```solidity
BeHYPE: 0xd8FC8F0b03eBA61F64D08B0bef69d80916E5DdA9
WithdrawManager: 0x9d0B0877b9f2204CF414Ca7862E4f03506822538
StakingCore: 0xCeaD893b162D38e714D82d06a7fe0b0dc3c38E0b
RoleRegistry: 0x90102473a816A01A9fB0809F2289438B2e294F76
BeHYPETimelock: 0xA24aF73EaDD17997EeEdbEd36672e996544D2DE4
L1Read: 0xb7467E0524Afba7006957701d1F06A59000d15A2
beHYPEBatchWithdrawalClaim: 0xA86b7a6942A1861E90BAf713ad70308545BeF966
```

### Minting (Staking)

Send a transaction to the StakingCore contract with the function signature `stake(string communityCode)`. The `communityCode` is the validator name you want those tokens to be designated to. The amount minted will be the amount of HYPE included in the value of the transaction. If you do not have a specific validator to stake to, you can pass an empty string ("") for automatic distribution across validators.

This will mint beHYPE tokens to the caller's address.

```solidity
function Stake() public {
    address user = address(0x1234);
    vm.deal(user, 10 ether);

    vm.startPrank(user); // using the private key of the user
    
    // Stake 10 HYPE to a specific validator
    stakingCore.stake{value: 10 ether}("validator_name");
    
    // Stake another 10 HYPE with automatic validator distribution
    stakingCore.stake{value: 10 ether}("");
}
```

### Burning (Unstaking)

Burning is a multistep process that depends on the amount of free (unstaked) tokens available in the protocol. There will typically always be a small float of the total supply unstaked to instantly fulfill burns, but for large amounts or high outflow volume, it becomes a two-step process.

**Step 1:** Approve the WithdrawManager contract with the amount of beHYPE tokens you want to unstake.

**Step 2:** Call `withdraw(uint256 beHypeAmount, bool instant, uint256 minAmountOut)` to burn `beHypeAmount` of tokens. The redeemed HYPE will be processed based on the `instant` parameter:

* `instant = false`: Normal withdrawal (7-day processing, no fee)
* `instant = true`: Instant withdrawal (0.5% fee applied)

The `minAmountOut` parameter provides slippage protection. This function returns a `withdrawalId` which will be used to claim the withdrawal once processed.

**Step 3:** For normal withdrawals, wait for processing time, then call `claimWithdrawal(uint256 withdrawalId)` to receive your HYPE tokens.

```solidity
function Burn() public {
    uint256 decimals = 10 ** 18;
    address user = address(0x1234); // set up with a balance of 10 beHYPE
    vm.startPrank(user);
    
    // 1. Approve 10 beHYPE (18 decimals)
    behype.approve(withdrawManager, 10 * decimals); 

    // 2. Normal withdrawal (7-day processing, no fee)
    uint256 minAmountOut = 9.9 ether; // 1% slippage tolerance
    uint256 withdrawalId = withdrawManager.withdraw(10 * decimals, false, minAmountOut);
    
    // 3. Wait for processing time (7 days)
    // ...
    
    // 4. Claim the withdrawal
    withdrawManager.claimWithdrawal(withdrawalId);
    require(user.balance >= 9.9 ether, "user should have received HYPE");
}
```

### Instant Redemption

For immediate access to HYPE, you can use instant redemption with a 0.5% fee:

```solidity
function InstantBurn() public {
    uint256 decimals = 10 ** 18;
    address user = address(0x1234); // set up with a balance of 10 beHYPE
    vm.startPrank(user);
    
    // 1. Approve 10 beHYPE
    behype.approve(withdrawManager, 10 * decimals);
    
    // 2. Instant withdrawal (immediate, 0.5% fee)
    uint256 minAmountOut = 9.4 ether; // accounting for 0.5% fee + slippage
    withdrawManager.withdraw(10 * decimals, true, minAmountOut);
    
    // Tokens are received immediately
    require(user.balance >= 9.4 ether, "user should have received HYPE instantly");
}
```

### API Endpoints

#### Base URL

```
https://api.hyperbeat.org/api/v1/behype/
```

#### Available Endpoints

1. **Get beHYPE Balance**
   * `GET /balance/{user_address}`
   * Returns user's beHYPE balance
2. **Get Exchange Ratio Updates**
   * `GET /exchange-ratio-update`
   * Returns latest exchange ratio between beHYPE and HYPE
3. **Get TVL Data**
   * `GET /tvl`
   * Returns total value locked, exchange ratio, and price information

### Function Signatures

#### StakingCore Contract

```solidity
// Stake HYPE to receive beHYPE
function stake(string calldata communityCode) external payable;
```

#### WithdrawManager Contract

```solidity
// Withdraw beHYPE for HYPE (returns withdrawal ID)
function withdraw(uint256 beHypeAmount, bool instant, uint256 minAmountOut) 
    external returns (uint256 withdrawalId);

// Claim completed withdrawal
function claimWithdrawal(uint256 withdrawalId) external;
```

#### BeHYPE Token Contract (ERC20)

```solidity
// Standard ERC20 functions
function balanceOf(address account) external view returns (uint256);
function approve(address spender, uint256 amount) external returns (bool);
function allowance(address owner, address spender) external view returns (uint256);
```

### Support

For additional support or questions about beHYPE integration, ask us on [discord](https://discord.gg/hyperbeat) or contact the development team.


# Staking API

<figure><img src="/files/5UD9yrcwBrKn3rOsB547" alt=""><figcaption></figcaption></figure>

Hyperbeat offers institutional clients a robust HYPE staking product via its validator on Hyperliquid, powered by the P2P.org Staking API. Built for funds, custodians, and fintechs, this solution delivers secure, scalable staking infrastructure without the constraints of frontend integrations.

**Already the most robust and widely used institutional staking solution supporting billions of dollars of institutional stake**, **now on Hyperliquid.**

## Key Benefits

1. Seamless Backend Integration and fast integration speed&#x20;

Stake HYPE programmatically using the Staking API — ideal for exchanges, fintech platforms, and custodians. Full UX & brand ownership — We manage the backend; you own the frontend, the customer relationship, and the value capture.

2. Revenue share

Powered by [Hyperbeat Builder Codes](https://docs.hyperbeat.org/hyperbeat-builder-codes). Integrators programatically earn revenue share on stake routed through the API.

3. Liquid Stake HYPE

Liquid stake HYPE directly via the staking API. Purpose built to be compliant with institutional grad custodial support, the integration handles all reporting and data flows on your behalf. Speed of execution and agility, on demand.

4. Institutional-Grade Performance - proven to handle billions of dollars of stake.

Built on P2P.org’s globally ranked validator infrastructure with industry-leading uptime, performance, and responsiveness.

5. Dedicated Support

Priority integration and support channel for onboarding, custom validator requests, and technical troubleshooting.

6. On-chain incentives

Earn Hyperbeat Hearts, Hypio Points (Hyperliquid’s leading NFT ecosystem), and future airdrops for staking HYPE via the API.

**Integration Architecture**

Clients connect directly to Hyperbeat’s validator node through P2P.org’s Staking API:

* Programmatic initiation of staking flows
* Real-time validator performance and status endpoints
* Withdrawal request support
* Secure handling of validator keys<br>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfZqWbolPjCLrkNXLpEeAS6KQyk8lkBMRq6kZlwj3OyTz5LTwUaIyXSZqDzpAtKw4USSoXW3qbcrwR3o-OnZjlo5PLiJQLDKlP_kh0Qyf-5akqB3AjDxeeA_XpX8wpqse51cLq7WA?key=abx1B7LaswEuGWjF-4RNKQ" alt=""><figcaption></figcaption></figure>

Get started

For onboarding, validator configuration, and custom deployments: <institutional@hyperbeat.org>

<br>


# Getting started

Staking in the Hyperliquid network using the Staking API consists of several main steps:

1. Transfer HYPE from spot balance to staking balance.
2. Create a delegate transaction.
3. Sign it and send it to the network.

[Get an authentication token](https://docs.p2p.org/docs/authentication) to start using Staking API.

We provide two distinct endpoints for testing and production environments.

* PRODUCTION: [https://api.p2p.org](https://api.p2p.org/)
* TESTING: [https://api-test.p2p.org](https://api-test.p2p.org/)

For Hyperliquid, there are two networks available:

* `mainnet` — the production network.
* `testnet` — Hyperliquid testnet.

Staking on Hyperliquid happens within HyperCore, and HYPE is required to be in the staking balance. Just like USDC can be transferred between perps and spot accounts, HYPE can be transferred between spot and staking accounts.

## 1. \[Optional] Transfer HYPE from Spot to Staking balance

Send a POST request to `/api/v1/hyperliquid/{network}/staking/transfer` [endpoint](https://docs.p2p.org/reference/hyperliquid-transfer).

Use `unsignedTransaction` returned in the response, then [sign and send](https://docs.p2p.org/docs/signing-transaction-hyperliquid) the transaction to Hyperliquid network. After this transaction has been successfully executed, the delegator staking balance can use this balance to delegate to the P2P validator. Transfers from spot account to staking account are instant.

## 2. Delegate Transaction

Send a POST request to `/api/v1/hyperliquid/{network}/staking/delegate` [endpoint](https://docs.p2p.org/reference/hyperliquid-delegate).

Use `unsignedTransaction` returned in the response, then [sign and send](https://docs.p2p.org/docs/signing-transaction-hyperliquid) the transaction to Hyperliquid network. After this transaction has been successfully executed, the delegator is actively participating in staking through the P2P validator. Be aware that delegations have a lockup duration of 1 day, which means that only after this period, delegations can be partially or fully undelegated.

Rewards are accrued every minute and distributed to stakers every day. Rewards are redelegated automatically to the staked validator, i.e. compounded.

### 3. Sign and Send Transaction

The requests to [transfer hype from spot to staking balance](https://docs.p2p.org/reference/hyperliquid-transfer), [delegate](https://docs.p2p.org/reference/hyperliquid-delegate), [undelegate](https://docs.p2p.org/reference/hyperliquid-undelegate) and [withdraw](https://docs.p2p.org/reference/hyperliquid-withdraw) return an `unsignedTransaction` that needs to be signed and broadcasted using the [send transaction endpoint](https://docs.p2p.org/reference/hyperliquid-send).

### 4. Check delegator staking balances

To check the delegator active balances for HYPE spot balance, stake balance, active delegations and pending withdrawals, use the [get delegator staking information endpoint](https://docs.p2p.org/reference/hyperliquid-info).


# Withdrawal

To withdraw delegated HYPE, the first step is to undelegate from the Hyperbeat X P2P validator. This will remove the HYPE from being actively delegated back to the staking balance.

1. Create an [undelegate request](https://docs.p2p.org/reference/hyperliquid-undelegate), [sign it and send it ](https://docs.p2p.org/docs/signing-transaction-hyperliquid)to the network.
   1. Undelegated balance will immediately be reflected in the staking account balance
2. Create a [withdrawal request](https://docs.p2p.org/reference/hyperliquid-withdraw), [sign it and send it](https://docs.p2p.org/docs/signing-transaction-hyperliquid) to the network.
   1. Transfers from spot to staking balance have a 7 day unstaking queue, which means that the tokens will be locked up during this period. You can check the pending withdrawals using the [get delegator balances](https://docs.p2p.org/reference/hyperliquid-info) endpoint.


# Sign and Broadcast Transaction

To sign and broadcast a transaction to the Hyperliquid network, follow these steps:

1. Retrieve an unsigned transaction (`unsignedTransaction`) from of one of the following requests responses: [transfer hype from spot to staking balance](https://docs.p2p.org/reference/hyperliquid-transfer), [delegate](https://docs.p2p.org/reference/hyperliquid-delegate), [undelegate](https://docs.p2p.org/reference/hyperliquid-undelegate) and [withdraw](https://docs.p2p.org/reference/hyperliquid-withdraw).
2. Sign the transaction using the following code:

```javascript
import { signUserSignedAction, userSignedActionEip712Types, isValidPrivateKey } from "@nktkas/hyperliquid/signing";

async function signTransaction(privateKey, unsignedTransaction) {
  const action = unsignedTransaction.action;

  return Buffer.from(
    JSON.stringify({
      ...unsignedTransaction,
      signature: await signUserSignedAction({
        wallet: privateKey,
        action: action,
        types: userSignedActionEip712Types[action.type],
      }),
    })
  ).toString("base64");
}

(async () => {
  const [, , rawTransaction, privateKey] = process.argv;

  if (!rawTransaction || typeof rawTransaction !== "string") {
    console.error("Invalid raw transaction. It should be a base64-encoded string.");
    process.exit(1);
  }

  if (!privateKey || typeof privateKey !== "string" || !isValidPrivateKey(privateKey)) {
    console.error("Invalid private key.");
    process.exit(1);
  }

  const unsignedTransaction = JSON.parse(Buffer.from(rawTransaction, "base64").toString("utf-8"));

  if (
    !("action" in unsignedTransaction) ||
    !("type" in unsignedTransaction.action) ||
    !["cDeposit", "tokenDelegate", "cWithdraw"].includes(unsignedTransaction.action.type)
  ) {
    console.error("Invalid unsigned transaction.");
    process.exit(1);
  }

  console.log(await signTransaction(privateKey.startsWith("0x") ? privateKey : `0x${privateKey}`, unsignedTransaction));
})();

/**
 *  To run with env variables:
 *
 *  $ export RAW_TX= 'rawtxhere'
 *  $ export PRIVATE_KEY= 'privatekeyhere'
 *  $ npx --yes -p @nktkas/hyperliquid@0.23.1 node hyperliquid-signer.js $RAW_TX $PRIVATE_KEY
 **/
```

3. Send the signed transaction using the [Send a transaction to the network](https://docs.p2p.org/reference/hyperliquid-send) endpoint.<br>


# Transfer HYPE tokens from SPOT to STAKING balance

## Transfer HYPE tokens from SPOT to STAKING balance

> Transfer HYPE tokens from SPOT to STAKING balance on the Hyperliquid network. Required to delegate HYPE tokens for staking rewards.

```json
{"openapi":"3.0.0","info":{"title":"Staking API","version":"1.0.0"},"servers":[{"url":"https://api.p2p.org","description":"Staking API"},{"url":"https://api-test.p2p.org","description":"Testnet Staking API"}],"security":[{"bearer":[]}],"components":{"securitySchemes":{"bearer":{"scheme":"bearer","bearerFormat":"JWT","type":"http"}},"schemas":{"HyperLiquidStakingTransferRequestDto":{"type":"object","properties":{"amount":{"type":"number","description":"HYPE amount to transfer","minimum":0.1,"maximum":9007199254740991},"delegatorAddress":{"type":"string","description":"Delegator Hyperliquid address"}},"required":["amount","delegatorAddress"]},"SuccessResponse":{"type":"object","properties":{"error":{"type":"object","nullable":true,"default":null},"result":{"type":"object"}},"required":["error","result"]},"HyperLiquidStakingTransferResponseDto":{"type":"object","properties":{"amount":{"type":"string","description":"Transaction amount"},"unsignedTransaction":{"type":"string","description":"Unsigned transaction data"},"createdAt":{"format":"date-time","type":"string","description":"Creation timestamp"}},"required":["amount","unsignedTransaction","createdAt"]},"ExceptionResponse":{"type":"object","properties":{"error":{"type":"object"},"result":{"type":"object","nullable":true,"default":null}},"required":["error","result"]},"ValidationException":{"type":"object","properties":{"code":{"type":"number","default":100101},"message":{"type":"string","default":"The data provided is not valid. Please check the request parameters and try again."},"name":{"type":"string","default":"ValidationException"},"errors":{"type":"array","items":{"$ref":"#/components/schemas/ValidationErrorResponse"}}},"required":["code","message","name","errors"]},"ValidationErrorResponse":{"type":"object","properties":{"property":{"type":"string"},"constraints":{"additionalProperties":{"type":"string"},"type":"array","items":{"type":"object"}}},"required":["property","constraints"]},"NotEnoughSpotBalanceException":{"type":"object","properties":{"code":{"type":"number","default":129108},"message":{"type":"string","default":"Not enough spot balance. Current balance: 100, required amount: 500."},"name":{"type":"string","default":"NotEnoughSpotBalanceException"}},"required":["code","message","name"]},"NoTokenException":{"type":"object","properties":{"code":{"type":"number","default":101111},"message":{"type":"string","default":"No Bearer token has been provided. To obtain an authentication token, follow the instructions at https://docs.p2p.org/docs/authentication."},"name":{"type":"string","default":"NoTokenException"}},"required":["code","message","name"]},"WrongTokenException":{"type":"object","properties":{"code":{"type":"number","default":101109},"message":{"type":"string","default":"An invalid Bearer token has been provided. Please specify the correct authentication token."},"name":{"type":"string","default":"WrongTokenException"}},"required":["code","message","name"]},"TokenGuardException":{"type":"object","properties":{"code":{"type":"number","default":101110},"message":{"type":"string","default":"The request could not be performed because the server authorization error occurred."},"name":{"type":"string","default":"TokenGuardException"}},"required":["code","message","name"]},"TransferSpotToStakingUnexpectedException":{"type":"object","properties":{"code":{"type":"number","default":129107},"message":{"type":"string","default":"The transfer spot to staking operation could not be completed because an unexpected error occurred."},"name":{"type":"string","default":"TransferSpotToStakingUnexpectedException"}},"required":["code","message","name"]}}},"paths":{"/api/v1/hyperliquid/{network}/staking/transfer":{"post":{"operationId":"hyperliquid-transfer","summary":"Transfer HYPE tokens from SPOT to STAKING balance","description":"Transfer HYPE tokens from SPOT to STAKING balance on the Hyperliquid network. Required to delegate HYPE tokens for staking rewards.","parameters":[{"name":"network","required":true,"in":"path","description":"The Hyperliquid network to use","schema":{"enum":["mainnet","testnet"],"type":"string"}}],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/HyperLiquidStakingTransferRequestDto"}}}},"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/SuccessResponse"}],"properties":{"result":{"oneOf":[{"$ref":"#/components/schemas/HyperLiquidStakingTransferResponseDto"}]}}}}}},"400":{"description":"Bad request","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/ValidationException"},{"$ref":"#/components/schemas/NotEnoughSpotBalanceException"}]}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/NoTokenException"},{"$ref":"#/components/schemas/WrongTokenException"}]}}}}}},"500":{"description":"Internal server error","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/TokenGuardException"},{"$ref":"#/components/schemas/TransferSpotToStakingUnexpectedException"}]}}}}}}},"tags":["Hyperliquid"]}}}}
```


# Delegate HYPE tokens to Hyperbeat validator

## Delegate HYPE tokens to P2P validator

> Delegate HYPE tokens to P2P validator for staking rewards

```json
{"openapi":"3.0.0","info":{"title":"Staking API","version":"1.0.0"},"servers":[{"url":"https://api.p2p.org","description":"Staking API"},{"url":"https://api-test.p2p.org","description":"Testnet Staking API"}],"security":[{"bearer":[]}],"components":{"securitySchemes":{"bearer":{"scheme":"bearer","bearerFormat":"JWT","type":"http"}},"schemas":{"HyperLiquidStakingDelegateRequestDto":{"type":"object","properties":{"amount":{"type":"number","description":"HYPE amount to delegate","minimum":0.1,"maximum":9007199254740991},"delegatorAddress":{"type":"string","description":"Delegator Hyperliquid address"}},"required":["amount","delegatorAddress"]},"SuccessResponse":{"type":"object","properties":{"error":{"type":"object","nullable":true,"default":null},"result":{"type":"object"}},"required":["error","result"]},"HyperLiquidStakingDelegateResponseDto":{"type":"object","properties":{"amount":{"type":"string","description":"Transaction amount"},"unsignedTransaction":{"type":"string","description":"Unsigned transaction data"},"createdAt":{"format":"date-time","type":"string","description":"Creation timestamp"}},"required":["amount","unsignedTransaction","createdAt"]},"ExceptionResponse":{"type":"object","properties":{"error":{"type":"object"},"result":{"type":"object","nullable":true,"default":null}},"required":["error","result"]},"NotEnoughStakingBalanceException":{"type":"object","properties":{"code":{"type":"number","default":129109},"message":{"type":"string","default":"Not enough staking balance. Current balance: 100, required amount: 500."},"name":{"type":"string","default":"NotEnoughStakingBalanceException"}},"required":["code","message","name"]},"ValidationException":{"type":"object","properties":{"code":{"type":"number","default":100101},"message":{"type":"string","default":"The data provided is not valid. Please check the request parameters and try again."},"name":{"type":"string","default":"ValidationException"},"errors":{"type":"array","items":{"$ref":"#/components/schemas/ValidationErrorResponse"}}},"required":["code","message","name","errors"]},"ValidationErrorResponse":{"type":"object","properties":{"property":{"type":"string"},"constraints":{"additionalProperties":{"type":"string"},"type":"array","items":{"type":"object"}}},"required":["property","constraints"]},"NoTokenException":{"type":"object","properties":{"code":{"type":"number","default":101111},"message":{"type":"string","default":"No Bearer token has been provided. To obtain an authentication token, follow the instructions at https://docs.p2p.org/docs/authentication."},"name":{"type":"string","default":"NoTokenException"}},"required":["code","message","name"]},"WrongTokenException":{"type":"object","properties":{"code":{"type":"number","default":101109},"message":{"type":"string","default":"An invalid Bearer token has been provided. Please specify the correct authentication token."},"name":{"type":"string","default":"WrongTokenException"}},"required":["code","message","name"]},"DelegateUnexpectedException":{"type":"object","properties":{"code":{"type":"number","default":129104},"message":{"type":"string","default":"The delegate operation could not be completed because an unexpected error occurred."},"name":{"type":"string","default":"DelegateUnexpectedException"}},"required":["code","message","name"]},"TokenGuardException":{"type":"object","properties":{"code":{"type":"number","default":101110},"message":{"type":"string","default":"The request could not be performed because the server authorization error occurred."},"name":{"type":"string","default":"TokenGuardException"}},"required":["code","message","name"]}}},"paths":{"/api/v1/hyperliquid/{network}/staking/delegate":{"post":{"operationId":"hyperliquid-delegate","summary":"Delegate HYPE tokens to P2P validator","description":"Delegate HYPE tokens to P2P validator for staking rewards","parameters":[{"name":"network","required":true,"in":"path","description":"The Hyperliquid network to use","schema":{"enum":["mainnet","testnet"],"type":"string"}}],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/HyperLiquidStakingDelegateRequestDto"}}}},"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/SuccessResponse"}],"properties":{"result":{"oneOf":[{"$ref":"#/components/schemas/HyperLiquidStakingDelegateResponseDto"}]}}}}}},"400":{"description":"Bad request","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/NotEnoughStakingBalanceException"},{"$ref":"#/components/schemas/ValidationException"}]}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/NoTokenException"},{"$ref":"#/components/schemas/WrongTokenException"}]}}}}}},"500":{"description":"Internal server error","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/DelegateUnexpectedException"},{"$ref":"#/components/schemas/TokenGuardException"}]}}}}}}},"tags":["Hyperliquid"]}}}}
```


# Undelegate HYPE tokens from Hyperbeat validator

## Undelegate HYPE tokens from P2P validator

> Undelegate HYPE tokens from P2P validator to stop earning staking rewards

```json
{"openapi":"3.0.0","info":{"title":"Staking API","version":"1.0.0"},"servers":[{"url":"https://api.p2p.org","description":"Staking API"},{"url":"https://api-test.p2p.org","description":"Testnet Staking API"}],"security":[{"bearer":[]}],"components":{"securitySchemes":{"bearer":{"scheme":"bearer","bearerFormat":"JWT","type":"http"}},"schemas":{"HyperLiquidStakingUndelegateRequestDto":{"type":"object","properties":{"amount":{"type":"number","description":"HYPE amount to undelegate","minimum":0.1,"maximum":9007199254740991},"delegatorAddress":{"type":"string","description":"Delegator Hyperliquid address"}},"required":["amount","delegatorAddress"]},"SuccessResponse":{"type":"object","properties":{"error":{"type":"object","nullable":true,"default":null},"result":{"type":"object"}},"required":["error","result"]},"HyperLiquidStakingUndelegateResponseDto":{"type":"object","properties":{"amount":{"type":"string","description":"Transaction amount"},"unsignedTransaction":{"type":"string","description":"Unsigned transaction data"},"createdAt":{"format":"date-time","type":"string","description":"Creation timestamp"}},"required":["amount","unsignedTransaction","createdAt"]},"ExceptionResponse":{"type":"object","properties":{"error":{"type":"object"},"result":{"type":"object","nullable":true,"default":null}},"required":["error","result"]},"DelegationLockedException":{"type":"object","properties":{"code":{"type":"number","default":129110},"message":{"type":"string","default":"Delegation is locked. Total locked balance: 12."},"name":{"type":"string","default":"DelegationLockedException"}},"required":["code","message","name"]},"NotEnoughDelegatedBalanceException":{"type":"object","properties":{"code":{"type":"number","default":129111},"message":{"type":"string","default":"Not enough delegated balance. Current balance: 100, required amount: 500."},"name":{"type":"string","default":"NotEnoughDelegatedBalanceException"}},"required":["code","message","name"]},"ValidationException":{"type":"object","properties":{"code":{"type":"number","default":100101},"message":{"type":"string","default":"The data provided is not valid. Please check the request parameters and try again."},"name":{"type":"string","default":"ValidationException"},"errors":{"type":"array","items":{"$ref":"#/components/schemas/ValidationErrorResponse"}}},"required":["code","message","name","errors"]},"ValidationErrorResponse":{"type":"object","properties":{"property":{"type":"string"},"constraints":{"additionalProperties":{"type":"string"},"type":"array","items":{"type":"object"}}},"required":["property","constraints"]},"NoTokenException":{"type":"object","properties":{"code":{"type":"number","default":101111},"message":{"type":"string","default":"No Bearer token has been provided. To obtain an authentication token, follow the instructions at https://docs.p2p.org/docs/authentication."},"name":{"type":"string","default":"NoTokenException"}},"required":["code","message","name"]},"WrongTokenException":{"type":"object","properties":{"code":{"type":"number","default":101109},"message":{"type":"string","default":"An invalid Bearer token has been provided. Please specify the correct authentication token."},"name":{"type":"string","default":"WrongTokenException"}},"required":["code","message","name"]},"UndelegateUnexpectedException":{"type":"object","properties":{"code":{"type":"number","default":129105},"message":{"type":"string","default":"The undelegate operation could not be completed because an unexpected error occurred."},"name":{"type":"string","default":"UndelegateUnexpectedException"}},"required":["code","message","name"]},"TokenGuardException":{"type":"object","properties":{"code":{"type":"number","default":101110},"message":{"type":"string","default":"The request could not be performed because the server authorization error occurred."},"name":{"type":"string","default":"TokenGuardException"}},"required":["code","message","name"]}}},"paths":{"/api/v1/hyperliquid/{network}/staking/undelegate":{"post":{"operationId":"hyperliquid-undelegate","summary":"Undelegate HYPE tokens from P2P validator","description":"Undelegate HYPE tokens from P2P validator to stop earning staking rewards","parameters":[{"name":"network","required":true,"in":"path","description":"The Hyperliquid network to use","schema":{"enum":["mainnet","testnet"],"type":"string"}}],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/HyperLiquidStakingUndelegateRequestDto"}}}},"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/SuccessResponse"}],"properties":{"result":{"oneOf":[{"$ref":"#/components/schemas/HyperLiquidStakingUndelegateResponseDto"}]}}}}}},"400":{"description":"Bad request","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/DelegationLockedException"},{"$ref":"#/components/schemas/NotEnoughDelegatedBalanceException"},{"$ref":"#/components/schemas/ValidationException"}]}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/NoTokenException"},{"$ref":"#/components/schemas/WrongTokenException"}]}}}}}},"500":{"description":"Internal server error","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/UndelegateUnexpectedException"},{"$ref":"#/components/schemas/TokenGuardException"}]}}}}}}},"tags":["Hyperliquid"]}}}}
```


# Withdraw undelegated HYPE tokens to SPOT balance

## Withdraw undelegated HYPE tokens to SPOT balance

> Withdraw accumulated staking rewards from delegated HYPE tokens

```json
{"openapi":"3.0.0","info":{"title":"Staking API","version":"1.0.0"},"servers":[{"url":"https://api.p2p.org","description":"Staking API"},{"url":"https://api-test.p2p.org","description":"Testnet Staking API"}],"security":[{"bearer":[]}],"components":{"securitySchemes":{"bearer":{"scheme":"bearer","bearerFormat":"JWT","type":"http"}},"schemas":{"HyperLiquidStakingWithdrawRequestDto":{"type":"object","properties":{"amount":{"type":"number","description":"HYPE amount to withdraw","minimum":0.1,"maximum":9007199254740991},"delegatorAddress":{"type":"string","description":"Delegator Hyperliquid address"}},"required":["amount","delegatorAddress"]},"SuccessResponse":{"type":"object","properties":{"error":{"type":"object","nullable":true,"default":null},"result":{"type":"object"}},"required":["error","result"]},"HyperLiquidStakingWithdrawResponseDto":{"type":"object","properties":{"amount":{"type":"string","description":"Transaction amount"},"unsignedTransaction":{"type":"string","description":"Unsigned transaction data"},"createdAt":{"format":"date-time","type":"string","description":"Creation timestamp"}},"required":["amount","unsignedTransaction","createdAt"]},"ExceptionResponse":{"type":"object","properties":{"error":{"type":"object"},"result":{"type":"object","nullable":true,"default":null}},"required":["error","result"]},"NotEnoughStakingBalanceException":{"type":"object","properties":{"code":{"type":"number","default":129109},"message":{"type":"string","default":"Not enough staking balance. Current balance: 100, required amount: 500."},"name":{"type":"string","default":"NotEnoughStakingBalanceException"}},"required":["code","message","name"]},"ValidationException":{"type":"object","properties":{"code":{"type":"number","default":100101},"message":{"type":"string","default":"The data provided is not valid. Please check the request parameters and try again."},"name":{"type":"string","default":"ValidationException"},"errors":{"type":"array","items":{"$ref":"#/components/schemas/ValidationErrorResponse"}}},"required":["code","message","name","errors"]},"ValidationErrorResponse":{"type":"object","properties":{"property":{"type":"string"},"constraints":{"additionalProperties":{"type":"string"},"type":"array","items":{"type":"object"}}},"required":["property","constraints"]},"NoTokenException":{"type":"object","properties":{"code":{"type":"number","default":101111},"message":{"type":"string","default":"No Bearer token has been provided. To obtain an authentication token, follow the instructions at https://docs.p2p.org/docs/authentication."},"name":{"type":"string","default":"NoTokenException"}},"required":["code","message","name"]},"WrongTokenException":{"type":"object","properties":{"code":{"type":"number","default":101109},"message":{"type":"string","default":"An invalid Bearer token has been provided. Please specify the correct authentication token."},"name":{"type":"string","default":"WrongTokenException"}},"required":["code","message","name"]},"WithdrawUnexpectedException":{"type":"object","properties":{"code":{"type":"number","default":129106},"message":{"type":"string","default":"The withdraw operation could not be completed because an unexpected error occurred."},"name":{"type":"string","default":"WithdrawUnexpectedException"}},"required":["code","message","name"]},"TokenGuardException":{"type":"object","properties":{"code":{"type":"number","default":101110},"message":{"type":"string","default":"The request could not be performed because the server authorization error occurred."},"name":{"type":"string","default":"TokenGuardException"}},"required":["code","message","name"]}}},"paths":{"/api/v1/hyperliquid/{network}/staking/withdraw":{"post":{"operationId":"hyperliquid-withdraw","summary":"Withdraw undelegated HYPE tokens to SPOT balance","description":"Withdraw accumulated staking rewards from delegated HYPE tokens","parameters":[{"name":"network","required":true,"in":"path","description":"The Hyperliquid network to use","schema":{"enum":["mainnet","testnet"],"type":"string"}}],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/HyperLiquidStakingWithdrawRequestDto"}}}},"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/SuccessResponse"}],"properties":{"result":{"oneOf":[{"$ref":"#/components/schemas/HyperLiquidStakingWithdrawResponseDto"}]}}}}}},"400":{"description":"Bad request","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/NotEnoughStakingBalanceException"},{"$ref":"#/components/schemas/ValidationException"}]}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/NoTokenException"},{"$ref":"#/components/schemas/WrongTokenException"}]}}}}}},"500":{"description":"Internal server error","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/WithdrawUnexpectedException"},{"$ref":"#/components/schemas/TokenGuardException"}]}}}}}}},"tags":["Hyperliquid"]}}}}
```


# Get Hyperliquid staking information for delegator

## Get Hyperliquid staking information for delegator

> Retrieve detailed staking information including spot balance, stake balance, delegations, and pending withdrawals for a given delegator address

```json
{"openapi":"3.0.0","info":{"title":"Staking API","version":"1.0.0"},"servers":[{"url":"https://api.p2p.org","description":"Staking API"},{"url":"https://api-test.p2p.org","description":"Testnet Staking API"}],"security":[{"bearer":[]}],"components":{"securitySchemes":{"bearer":{"scheme":"bearer","bearerFormat":"JWT","type":"http"}},"schemas":{"HyperLiquidStakingInfoRequestDto":{"type":"object","properties":{"delegatorAddress":{"type":"string","description":"Delegator Hyperliquid address"}},"required":["delegatorAddress"]},"SuccessResponse":{"type":"object","properties":{"error":{"type":"object","nullable":true,"default":null},"result":{"type":"object"}},"required":["error","result"]},"HyperLiquidStakingInfoResponseDto":{"type":"object","properties":{"spotBalance":{"type":"number","description":"HYPE balance that is possible to transfer to staking balance"},"stakeBalance":{"type":"number","description":"HYPE balance that is available to delegate"},"delegations":{"description":"Array of all the delegations per delegator","type":"array","items":{"$ref":"#/components/schemas/HyperLiquidStakingDelegationDto"}},"pendingWithdrawal":{"type":"number","description":"Amount of HYPE that was withdrawn but not yet available (7 days unstaking queue)"}},"required":["spotBalance","stakeBalance","delegations","pendingWithdrawal"]},"HyperLiquidStakingDelegationDto":{"type":"object","properties":{"amount":{"type":"number","description":"Amount of HYPE delegated"},"validator":{"type":"string","description":"Validator address"},"lockedUntil":{"type":"string","description":"Timestamp when the delegation is locked until (ISO 8601)","nullable":true}},"required":["amount","validator","lockedUntil"]},"ExceptionResponse":{"type":"object","properties":{"error":{"type":"object"},"result":{"type":"object","nullable":true,"default":null}},"required":["error","result"]},"ValidationException":{"type":"object","properties":{"code":{"type":"number","default":100101},"message":{"type":"string","default":"The data provided is not valid. Please check the request parameters and try again."},"name":{"type":"string","default":"ValidationException"},"errors":{"type":"array","items":{"$ref":"#/components/schemas/ValidationErrorResponse"}}},"required":["code","message","name","errors"]},"ValidationErrorResponse":{"type":"object","properties":{"property":{"type":"string"},"constraints":{"additionalProperties":{"type":"string"},"type":"array","items":{"type":"object"}}},"required":["property","constraints"]},"NoTokenException":{"type":"object","properties":{"code":{"type":"number","default":101111},"message":{"type":"string","default":"No Bearer token has been provided. To obtain an authentication token, follow the instructions at https://docs.p2p.org/docs/authentication."},"name":{"type":"string","default":"NoTokenException"}},"required":["code","message","name"]},"WrongTokenException":{"type":"object","properties":{"code":{"type":"number","default":101109},"message":{"type":"string","default":"An invalid Bearer token has been provided. Please specify the correct authentication token."},"name":{"type":"string","default":"WrongTokenException"}},"required":["code","message","name"]},"GetStakingInfoUnexpectedException":{"type":"object","properties":{"code":{"type":"number","default":129112},"message":{"type":"string","default":"The get staking info operation could not be completed because an unexpected error occurred."},"name":{"type":"string","default":"GetStakingInfoUnexpectedException"}},"required":["code","message","name"]},"TokenGuardException":{"type":"object","properties":{"code":{"type":"number","default":101110},"message":{"type":"string","default":"The request could not be performed because the server authorization error occurred."},"name":{"type":"string","default":"TokenGuardException"}},"required":["code","message","name"]}}},"paths":{"/api/v1/hyperliquid/{network}/staking/info":{"get":{"operationId":"hyperliquid-info","summary":"Get Hyperliquid staking information for delegator","description":"Retrieve detailed staking information including spot balance, stake balance, delegations, and pending withdrawals for a given delegator address","parameters":[{"name":"network","required":true,"in":"path","description":"The Hyperliquid network to use","schema":{"enum":["mainnet","testnet"],"type":"string"}}],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/HyperLiquidStakingInfoRequestDto"}}}},"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/SuccessResponse"}],"properties":{"result":{"oneOf":[{"$ref":"#/components/schemas/HyperLiquidStakingInfoResponseDto"}]}}}}}},"400":{"description":"Bad request","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/ValidationException"}]}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/NoTokenException"},{"$ref":"#/components/schemas/WrongTokenException"}]}}}}}},"500":{"description":"Internal server error","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/GetStakingInfoUnexpectedException"},{"$ref":"#/components/schemas/TokenGuardException"}]}}}}}}},"tags":["Hyperliquid"]}}}}
```


# Send a transaction to the network

## Send a transaction to the network

> This endpoint allows you to send a transaction to the network

```json
{"openapi":"3.0.0","info":{"title":"Staking API","version":"1.0.0"},"servers":[{"url":"https://api.p2p.org","description":"Staking API"},{"url":"https://api-test.p2p.org","description":"Testnet Staking API"}],"security":[{"bearer":[]}],"components":{"securitySchemes":{"bearer":{"scheme":"bearer","bearerFormat":"JWT","type":"http"}},"schemas":{"HyperLiquidStakingSendRequestDto":{"type":"object","properties":{"signedTransaction":{"type":"string","description":"Signed transaction data"}},"required":["signedTransaction"]},"SuccessResponse":{"type":"object","properties":{"error":{"type":"object","nullable":true,"default":null},"result":{"type":"object"}},"required":["error","result"]},"HyperLiquidStakingSendResponseDto":{"type":"object","properties":{"createdAt":{"format":"date-time","type":"string","description":"Transaction creation timestamp"},"network":{"type":"string","description":"Network name","enum":["mainnet","testnet"]}},"required":["createdAt","network"]},"ExceptionResponse":{"type":"object","properties":{"error":{"type":"object"},"result":{"type":"object","nullable":true,"default":null}},"required":["error","result"]},"InvalidSignedTransactionException":{"type":"object","properties":{"code":{"type":"number","default":129113},"message":{"type":"string","default":"The signed transaction is invalid and cannot be processed. "},"name":{"type":"string","default":"InvalidSignedTransactionException"}},"required":["code","message","name"]},"ValidationException":{"type":"object","properties":{"code":{"type":"number","default":100101},"message":{"type":"string","default":"The data provided is not valid. Please check the request parameters and try again."},"name":{"type":"string","default":"ValidationException"},"errors":{"type":"array","items":{"$ref":"#/components/schemas/ValidationErrorResponse"}}},"required":["code","message","name","errors"]},"ValidationErrorResponse":{"type":"object","properties":{"property":{"type":"string"},"constraints":{"additionalProperties":{"type":"string"},"type":"array","items":{"type":"object"}}},"required":["property","constraints"]},"NoTokenException":{"type":"object","properties":{"code":{"type":"number","default":101111},"message":{"type":"string","default":"No Bearer token has been provided. To obtain an authentication token, follow the instructions at https://docs.p2p.org/docs/authentication."},"name":{"type":"string","default":"NoTokenException"}},"required":["code","message","name"]},"WrongTokenException":{"type":"object","properties":{"code":{"type":"number","default":101109},"message":{"type":"string","default":"An invalid Bearer token has been provided. Please specify the correct authentication token."},"name":{"type":"string","default":"WrongTokenException"}},"required":["code","message","name"]},"UnexpectedSendingTransactionException":{"type":"object","properties":{"code":{"type":"number","default":129103},"message":{"type":"string","default":"The transaction could not be sent because an unexpected error occurred."},"name":{"type":"string","default":"UnexpectedSendingTransactionException"}},"required":["code","message","name"]},"TokenGuardException":{"type":"object","properties":{"code":{"type":"number","default":101110},"message":{"type":"string","default":"The request could not be performed because the server authorization error occurred."},"name":{"type":"string","default":"TokenGuardException"}},"required":["code","message","name"]}}},"paths":{"/api/v1/hyperliquid/{network}/transaction/send":{"post":{"operationId":"hyperliquid-send","summary":"Send a transaction to the network","description":"This endpoint allows you to send a transaction to the network","parameters":[{"name":"network","required":true,"in":"path","description":"The Hyperliquid network to use","schema":{"enum":["mainnet","testnet"],"type":"string"}}],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/HyperLiquidStakingSendRequestDto"}}}},"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/SuccessResponse"}],"properties":{"result":{"oneOf":[{"$ref":"#/components/schemas/HyperLiquidStakingSendResponseDto"}]}}}}}},"400":{"description":"Bad request","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/InvalidSignedTransactionException"},{"$ref":"#/components/schemas/ValidationException"}]}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/NoTokenException"},{"$ref":"#/components/schemas/WrongTokenException"}]}}}}}},"500":{"description":"Internal server error","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExceptionResponse"}],"properties":{"error":{"allOf":[{"$ref":"#/components/schemas/UnexpectedSendingTransactionException"},{"$ref":"#/components/schemas/TokenGuardException"}]}}}}}}},"tags":["Hyperliquid"]}}}}
```


# Vanilla staking

Hyperbeat runs a high-performant bare metal node in[ collaboration](https://x.com/0xHyperBeat/status/1879529840698962414) with[ P2P](https://www.p2p.org/) and[ Hypio](https://opensea.io/collection/hypio). The node offers:

* Best-in-class uptime and block production&#x20;
* Institutional grade node operations, security and infrastructure
* Additional rewards beyond block rewards through various Hyperbeat initiatives

{% hint style="success" %}
[Vanilla Stake with Hyperbeat X P2P X Hypio now](https://app.hyperliquid.xyz/staking)
{% endhint %}

## How to Vanilla stake

{% @arcade/embed flowId="nscRvImaKDq6xJTkZikp" url="<https://app.arcade.software/share/nscRvImaKDq6xJTkZikp>" %}


# Hyperbeat Public RPC Node

Hyperbeat runs a public RPC node for the benefit of the Hyperliquid ecosystem.&#x20;

{% hint style="success" %}
[Access the Public RPC here](https://hl-mainnet.rpc.p2p.world/evm)
{% endhint %}


# Hyperbeat Earn

Hyperbeat Vaults are designed to unlock yield opportunities on HyperEVM, offering higher base yields, optimized liquidity, and greater capital flexibility. The vaults cover a wide spectrum of risk tranches and automate DeFi strategies on HyperEVM to simplify user experience and maximise capital efficiency.&#x20;


# HYPE Vault

The best risk-adjusted return on your HYPE, dynamically allocating capital through strategies typically exclusive to institutions now democratised for all.

{% hint style="success" %}
[Deposit into the Hyperbeat Ultra HYPE vault now](https://app.hyperbeat.org/vaults/hype)
{% endhint %}

## Partners

* Hyperlend
* Hypurrfi
* Timeswap
* Hyperswap
* Upshift
* Silhouette&#x20;

## Strategist

[Edge UltraYield ](https://edgecapital.xyz/)capital is the strategist for the HYPE vault.&#x20;

## Infrastructure

[August](https://docs.augustdigital.io/) is the infrastructure provider.

## Vault Address

[hbHYPE](https://purrsec.com/address/0x96c6cbb6251ee1c257b2162ca0f39aa5fa44b1fb)

## Performance fee

15%

## Proof of solvency

[hbHYPE proof of solvency ](https://accountable.hyperbeat.org/hbHYPE)

## FAQs

### What is the Hyperbeat Ultra HYPE vault?

The Hyperbeat Ultra HYPE vault is an automated DeFi strategy vault that provides users a simple access point to use their HYPE in the HyperEVM ecosystem. Assets are deployed to generate real yield and earn exclusive incentives from partners.

### What happens to deposited assets?

Deposited assets are deployed into HyperEVM protocols to generate real yield and earn exclusive incentives.

### Can I withdraw from the Hyperbeat Ultra HYPE vault?

Assets are subject to a three working day withdrawal period.

### Is the Hyperbeat Ultra HYPE vault audited?

Yes, the vault is audited by [Zelic](https://content.gitbook.com/content/LaS0wfc7geC7DaOTDEn7/blobs/3UeT78zGv53RD0ugoPeg/22.03.18%20-%20Fractal%20Final%20Report.pdf), [Sigma Prime](https://2798104377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLaS0wfc7geC7DaOTDEn7%2Fuploads%2FsHxOMBpM7X3DSqcRNG82%2F24.08.09%20-%20SigmaPrime%20-%20Audit%20Report.pdf?alt=media\&token=5ebfa56d-9b3f-4e6f-9ec0-037b8d8af1b4) and [ChainSecurity.](https://2798104377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLaS0wfc7geC7DaOTDEn7%2Fuploads%2Fgf7igXLiz7gpv0FctQW8%2F25.01.21%20-%20ChainSecurity%20Audit.pdf?alt=media\&token=c696298c-e3e8-49a2-baf5-745a99c62eac)

### What are the risks involved?

Liquid vaults carry smart contract risks along with varying levels of economic risk. This particular vault engages in liquidity provision, which may lead to impermanent loss.

### Who is the strategy manager?&#x20;

[UltraYield](https://edgecapital.xyz/) (part of the Edge Capital Group) is a team of experienced strategy curators focused on market-neutral trades. The team has an extensive track record in crypto spanning from 2020, on top of years in TradFi achieving double digit APY in USD terms. The selected trades are undergoing an extensive DD with picking the best ones with relevant risk/return profile. The list of opportunities is constantly updated with any directional exposure being completely hedged.

\
\
\
\ <br>


# UBTC Vault

The best risk-adjusted return on your UBTC, dynamically allocating capital through strategies typically exclusive to institutions now democratised for all.

{% hint style="success" %}
[Deposit into the Hyperbeat Ultra UBTC vault now](https://app.hyperbeat.org/vaults/ubtc)
{% endhint %}

## Partners

* Unit Protocol
* Hyperlend
* Hypurrfi
* Hyperswap
* Upshift
* Harmonix
* Silhouette&#x20;

## Strategist

[Edge UltraYield ](https://edgecapital.xyz/)capital is the strategist for the UBTC vault.&#x20;

## Infrastructure

[August](https://docs.augustdigital.io/) is the infrastructure provider.

## Vault Address

[hbBTC](https://purrsec.com/address/0xc061d38903b99ac12713b550c2cb44b221674f94)

## Performance fee

15%

## Proof of solvency

[hbBTC proof of solvency](https://accountable.hyperbeat.org/hbBTC)

## FAQs

## What is the Hyperbeat Ultra UBTC vault?

The Hyperbeat Ultra UBTC vault is an automated DeFi strategy vault that provides users a simple access point to use their HYPE in the HyperEVM ecosystem. Assets are deployed to generate real yield and earn exclusive incentives from partners.

## What happens to deposited assets?

Deposited assets are deployed into HyperEVM protocols to generate real yield and earn exclusive incentives.

## Does hbBTC have directional exposure to UBTC?

Yes, the vault maintains directional exposure to UBTC while earning yield in various strategies.

## Can I withdraw from the Hyperbeat Ultra UBTC vault?

Assets are subject to a withdrawal period of 3 working days.

## Is the Hyperbeat Ultra UBTC vault audited?

Yes, the vault is audited by [Zelic](https://content.gitbook.com/content/LaS0wfc7geC7DaOTDEn7/blobs/3UeT78zGv53RD0ugoPeg/22.03.18%20-%20Fractal%20Final%20Report.pdf), [Sigma Prime](https://2798104377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLaS0wfc7geC7DaOTDEn7%2Fuploads%2FsHxOMBpM7X3DSqcRNG82%2F24.08.09%20-%20SigmaPrime%20-%20Audit%20Report.pdf?alt=media\&token=5ebfa56d-9b3f-4e6f-9ec0-037b8d8af1b4) and [ChainSecurity.](https://2798104377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLaS0wfc7geC7DaOTDEn7%2Fuploads%2Fgf7igXLiz7gpv0FctQW8%2F25.01.21%20-%20ChainSecurity%20Audit.pdf?alt=media\&token=c696298c-e3e8-49a2-baf5-745a99c62eac)

## Will I be charged fees while in the vault?

Zero platform fee for the first 30-days, thereafter a 1.5% platform fee will be charged annually on your deposited amount and prorated based on the duration your funds remain in the vault.

## What are the risks involved?

Liquid vaults carry smart contract risks along with varying levels of economic risk. This particular vault engages in liquidity provision, which may lead to impermanent loss.

## Who is the strategy manager?&#x20;

[UltraYield](https://edgecapital.xyz/) (part of the Edge Capital Group) is a team of experienced strategy curators focused on market-neutral trades. The team has an extensive track record in crypto spanning from 2020, on top of years in TradFi achieving double digit APY in USD terms. The selected trades are undergoing an extensive DD with picking the best ones with relevant risk/return profile. The list of opportunities is constantly updated with any directional exposure being completely hedged.

\
\
\
\ <br>

\
\
\
\ <br>


# USDT Vault

The best risk-adjusted return on your USDT, dynamically allocating capital through strategies typically exclusive to institutions now democratised for all.

{% hint style="success" %}
[Deposit into the Hyperbeat USDT vault now](https://app.hyperbeat.org/vaults/usdt)
{% endhint %}

## Strategist

Hyperbeat core is the strategist for the USDT vault.&#x20;

## Risk Oversight

[RockawayX](https://rockawayx.com/)

## Infrastructure

[Hyperbeat Core](https://hyperbeat.org/) is the infrastructure provider.

## Vault Address

[hbUSDT](https://purrsec.com/address/0x5e105266db42f78fa814322bce7f388b4c2e61eb)

## Performance fee

20%

## Proof of solvency

[hbUSDT proof of solvency](https://accountable.hyperbeat.org/hbUSDT)

## FAQs

## What is the Hyperbeat USDT vault?

The Hyperbeat USDT vault is an automated DeFi strategy vault that provides users a simple access point to use their USDT in the HyperEVM ecosystem. Assets are deployed to generate real yield and earn exclusive incentives from partners.

## What happens to deposited assets?

Deposited assets are deployed into HyperEVM protocols to generate real yield and earn exclusive incentives,

## Can I withdraw from the Hyperbeat USDT vault?

Yes, you can withdraw from the Hyperbeat USDT vault. There are two withdrawal options available: Instant Redemption and Classic Redemption. Instant Redemption allows for immediate withdrawals when there is sufficient liquidity, but incurs a 0.5% early withdrawal fee. Alternatively, users can select the Classic Redemption option, which processes the withdrawal within two days without slippage or fees.

## Why do withdrawals take two days?&#x20;

Assets are used in on-chain strategies that need time to unwind safely. The two day withdrawal period helps avoid slippage and ensures efficient exits.

## Is the Hyperbeat USDT vault audited?

Yes, three times, twice by Hacken ([1](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F1wxK6TgqaRsSgt3ixVMx%2FMidas_SC%20Audit%20Report_25092023_%5BSA-1833%5D%20-%20POST%20REMEDIATION.pdf?alt=media\&token=cdcf6533-7366-42db-9d3b-224efac85b9a), [2](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F38N1bo36K8FLriRrPDXb%2FHacken_Midas_%5BSCA%5D%20Midas_Vault_Dec2023_P-2023-076_1_20240118%2016_22.pdf?alt=media\&token=2c58f6f7-889e-4c64-ac84-35bad59eb51a)) and once by [Sherlock](https://audits.sherlock.xyz/contests/332).

## Will I be charged fees while in the vault?

A 20% performance fee is charged, prorated based on how long your funds remain in the vault.

## What are the risks involved?

Liquid vaults carry smart contract risks along with varying levels of economic risk. This particular vault engages in liquidity provision, which may lead to impermanent loss.

## Who provides risk oversight?&#x20;

[RockawayX](https://rockawayx.com/) offers an institutional-grade approach to managing DeFi vaults, providing secure, risk-managed access to market-neutral strategies. Drawing on experience across decentralized finance and private credit, the strategist focuses on delivering consistent returns with controlled volatility. Over four years of operation, the strategy has maintained a strong track record with no defaults, bad debt, or liquidations, reflecting a disciplined approach to risk management in digital asset credit markets.

\
\
\
\ <br>

\
\
\
\ <br>

\
\
\
\ <br>


# USDC Vault

The best risk-adjusted return on your USDC, dynamically allocating capital through strategies typically exclusive to institutions now democratised for all.

{% hint style="success" %}
[Deposit into the Hyperbeat USDC vault now](https://app.hyperbeat.org/vaults/usdc)
{% endhint %}

## Strategist

Hyperbeat core is the strategist for the USDC vault.&#x20;

## Risk Oversight

[RockawayX](https://rockawayx.com/)

## Infrastructure

[Hyperbeat Core](https://hyperbeat.org/) is the infrastructure provider.

## Vault Address

[hbUSDC](https://hyperevmscan.io/address/0x057ced81348D57Aad579A672d521d7b4396E8a61)

## Performance fee

20%

## Proof of solvency

[hbUSDC proof of solvency](https://accountable.hyperbeat.org/hbUSDC)

## FAQs

## What is the Hyperbeat USDC vault?

The Hyperbeat USDC vault is an automated DeFi strategy vault that provides users a simple access point to use their USDC in the HyperEVM ecosystem. Assets are deployed to generate real yield and earn exclusive incentives from partners.

## What happens to deposited assets?

Deposited assets are deployed into HyperEVM protocols to generate real yield and earn exclusive incentives. Assets are also used to run basis-trades on HyperCore via allocations to [dnTokens](https://docs.hyperbeat.org/delta-neutral-tokens-dntokens).

## What do I withdraw my accrued yield?

Your yield earned is directly derived from; and attributed to the growth in the exchange rate of hbUSDC. For example: If I my entry point was 1 hbUSDC = 1.0000 USDC and I deposited $100, and now the exchange rate shows 1 hbUSDC = 1.027293 USDC, your yield earned is (100 \* 0.027293 = $2.7293). You can realise this accrued yield by withdrawing it from the vault.

## Can I withdraw from the Hyperbeat USDC vault?

Yes, you can withdraw from the Hyperbeat USDC vault. There are two withdrawal options available: Instant Redemption and Classic Redemption. Instant Redemption allows for immediate withdrawals when there is sufficient liquidity, but incurs a 0.5% early withdrawal fee. Alternatively, users can select the Classic Redemption option, which processes the withdrawal within 2 days without slippage or fees.

## Why do withdrawals take three working days?&#x20;

Assets are used in on-chain strategies that need time to unwind safely. The three working day withdrawal period helps avoid slippage and ensures efficient exits.

## Is the Hyperbeat USDC vault audited?

Yes, three times, twice by Hacken ([1](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F1wxK6TgqaRsSgt3ixVMx%2FMidas_SC%20Audit%20Report_25092023_%5BSA-1833%5D%20-%20POST%20REMEDIATION.pdf?alt=media\&token=cdcf6533-7366-42db-9d3b-224efac85b9a), [2](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F38N1bo36K8FLriRrPDXb%2FHacken_Midas_%5BSCA%5D%20Midas_Vault_Dec2023_P-2023-076_1_20240118%2016_22.pdf?alt=media\&token=2c58f6f7-889e-4c64-ac84-35bad59eb51a)) and once by [Sherlock](https://audits.sherlock.xyz/contests/332).

## Will I be charged fees while in the vault?

A 20% performance fee will apply, prorated based on how long your funds remain in the vault.

## What are the risks involved?

Liquid vaults carry smart contract risks along with varying levels of economic risk. This particular vault engages in liquidity provision, which may lead to impermanent loss.

## Who provides risk oversight?&#x20;

[RockawayX](https://rockawayx.com/) offers an institutional-grade approach to managing DeFi vaults, providing secure, risk-managed access to market-neutral strategies. Drawing on experience across decentralized finance and private credit, the strategist focuses on delivering consistent returns with controlled volatility. Over four years of operation, the strategy has maintained a strong track record with no defaults, bad debt, or liquidations, reflecting a disciplined approach to risk management in digital asset credit markets.

\
\
\
\ <br>

\
\
\
\ <br>

\
\
\
\ <br>


# Ventuals (HIP-3) VLP Vault

The de facto source of liquidity for Ventuals.

The Ventuals (HIP-3) Liquidity Provider (VLP) vault executes market making strategies on Ventuals and receives a portion of trading fees. The community can provide liquidity for the vault to share its pnl. This vault is hosted in partnership with the Ventuals team as the de facto source of liquidity for Ventuals HIP-3 Exchange. This vault uses caps, with cap increases in the future at the request of Ventuals.

{% hint style="success" %}
[Deposit into the Ventuals (HIP-3) VLP Vault here](https://app.hyperbeat.org/vaults/wvlp)
{% endhint %}

## What is Ventuals?

[Ventuals](https://testnet.ventuals.com/) focusses on making private markets public by enabling perps trading for the most innovative private companies in the world, unlocking access to a multi-trillion dollar asset class that normal investors have historically been locked out of.&#x20;

On Ventuals, you can:

* Long or short private companies like Cursor, OpenAI, and SpaceX.
* Trade with up to 10x leverage.
* Deposit stablecoins to provide liquidity into the Ventuals Liquidity Provider Vault by Hyperbeat to earn. This vaults role is similar to that of HLP for Hyperliquid.

Ventuals is built on Hyperliquid's proven perps orderbook infrastructure, using the [HIP-3](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-3-builder-deployed-perpetuals) standard.

## What happens to deposited assets?

Deposited assets will be allocated to market-making strategies on Ventuals once HIP-3 is live. Until then, as the HIP-3 launch date is still to be confirmed, assets will be put to work in [hbUSDT](https://app.hyperbeat.org/vaults/usdt) to generate a competitive yield as requested by Ventuals.

## Proof of solvency

[wVLP proof of solvency](https://accountable.hyperbeat.org/wVLP)

## Can I withdraw from the Hyperbeat (HIP3) VLP vault?

Yes, migration or instant withdrawals are available as the vault is being unwound.&#x20;

##

## Is the Hyperbeat (HIP3) VLP vault audited?

Yes, three times, twice by Hacken ([1](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F1wxK6TgqaRsSgt3ixVMx%2FMidas_SC%20Audit%20Report_25092023_%5BSA-1833%5D%20-%20POST%20REMEDIATION.pdf?alt=media\&token=cdcf6533-7366-42db-9d3b-224efac85b9a), [2](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F38N1bo36K8FLriRrPDXb%2FHacken_Midas_%5BSCA%5D%20Midas_Vault_Dec2023_P-2023-076_1_20240118%2016_22.pdf?alt=media\&token=2c58f6f7-889e-4c64-ac84-35bad59eb51a)) and once by [Sherlock](https://audits.sherlock.xyz/contests/332).

## Will I be charged fees while in the vault?

No fees will be charged on Hyperbeat VLP until HIP-3 goes live. In the meantime, assets will be deposited into [hbUSDT](https://app.hyperbeat.org/vaults/usdt) to generate a base yield. All hbUSDT APYs are shown net of fees and are public [here](https://app.hyperbeat.org/vaults/usdt). Until HIP-3 goes live VLP vault depositor will earn the same rewards as deposits into hbUSDT do, as well as any additional VLP vault specific rewards.

## What are the risks involved?

Liquid vaults carry smart contract risks along with varying levels of economic risk.


# Nunchi (HIP-3) nLP Vault

The de facto source of liquidity for Nunchi.

The Nunchi nLP Vault lets anyone deposit stablecoin liquidity for use as the de facto source of liquidity to market make on Nunchi HIP-3 Exchange. Prior to Nunchi’s launch, funds are deployed into Hyperliquid native yield venues to generate the best risk-adjusted return. Depositors mint nLP shares and participate pro‑rata in vault performance. The vault is designed to power and bootstrap liquidity for Nunchi’s Markets (nCLOB and HIP‑3).

{% hint style="success" %}
[Deposit into the Nunchi (HIP-3) nLP Vault here ](https://app.hyperbeat.org/vaults/nlp)
{% endhint %}

## **What is Nunchi**

A HIP-3 perpetuals exchange for yield.

## What happens to deposited assets?

USDT and USDC deposits are routed to Hyperliquid native yield venues, where capital is put to work via Hyperbeat’s strategy engine. Returns flow back as an increase in the nLP share price.

## Proof of solvency

[wNLP proof of solvency](https://accountable.hyperbeat.org/wNLP)

## What do I get for depositing into the Nunchi (HIP-3) nLP Vault?

You get yield, Nunchi points (cHIPs) and Hearts.&#x20;

## Can I withdraw from the Nunchi (HIP-3) nLP Vault

Yes, you can withdraw from the Nunchi nLP vault. There are two withdrawal options available: Instant Redemption and Classic Redemption. Instant Redemption allows for immediate withdrawals when there is sufficient liquidity, but incurs a 0.5% early withdrawal fee. Alternatively, users can select the Classic Redemption option, which processes the withdrawal within 2 days without slippage or fees.

## Why do withdrawals take two days?&#x20;

Assets are used in on-chain strategies that need time to unwind safely. The two day withdrawal period helps avoid slippage and ensures efficient exits.

## Is the Nunchi (HIP3) nLP vault audited?

Yes, the vault is audited by [Nethermind security](https://github.com/0xhyperbeat/Audits/tree/main/Vault-Infra) and [Certora](https://github.com/0xhyperbeat/Audits/tree/main/Vault-Infra).

## Strategist

[Hyperbeat Core](https://hyperbeat.org/)  is the strategist for the lstHYPE vault.&#x20;

## Risk Oversight

[RockawayX](https://rockawayx.com/)

## Infrastructure

[Hyperbeat Core](https://hyperbeat.org/) is the infrastructure provider.

## What are the risks involved?

Liquid vaults carry smart contract risks along with varying levels of economic risk.


# LST Vault

An automated, non custodial DeFi strategy for your preferred liquid staked HYPE token (i.e. kHYPE or stHYPE). The vault automates allocation of your LST across HyperEVM ecosystem to earn yield and points.

{% hint style="success" %}
[Deposit into the Hyperbeat LST vault now](https://app.hyperbeat.org/vaults/lsthype)
{% endhint %}

## Strategist

Hyperbeat core is the strategist for the lstHYPE vault.&#x20;

## Risk Oversight

[RockawayX](https://rockawayx.com/)

## Infrastructure

[Hyperbeat Core](https://hyperbeat.org/) is the infrastructure provider.

## Vault Address

[lstHYPE](https://hyperevmscan.io/token/0x81e064d0eB539de7c3170EDF38C1A42CBd752A76)

## Performance fee

20%

## Proof of solvency

[lstHYPE proof of solvency](https://accountable.hyperbeat.org/lstHYPE)

## FAQs

## What is the Hyperbeat LST vault?

The Hyperbeat LST vault is an automated DeFi strategy for your preferred liquid staked HYPE token (i.e. kHYPE or stHYPE). The vault provides users a simple access point to use their LST in the HyperEVM ecosystem to earn yield and points.

## What happens to deposited assets?

Deposited assets are deployed into HyperEVM protocols to generate real yield and earn exclusive incentives.

## What is the difference between the lstHYPE vault and hbhYPE vault vault?

The lstHYPE vault gives users the ability to automate yield generation on their preferred **liquid staking token** while the hbhYPE vault only allows for WHYPE deposits.&#x20;

## Can I withdraw from the Hyperbeat LST vault?

Yes, you can withdraw from the Hyperbeat LST vault. However, please note that withdrawals are subject to a processing period and may take up to two days to complete.

## Why do withdrawals take two days?&#x20;

Assets are used in on-chain strategies that need time to unwind safely. The two day withdrawal period helps avoid slippage and ensures efficient exits.

## Is the Hyperbeat LST vault audited?

Yes, three times, twice by Hacken ([1](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F1wxK6TgqaRsSgt3ixVMx%2FMidas_SC%20Audit%20Report_25092023_%5BSA-1833%5D%20-%20POST%20REMEDIATION.pdf?alt=media\&token=cdcf6533-7366-42db-9d3b-224efac85b9a), [2](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F38N1bo36K8FLriRrPDXb%2FHacken_Midas_%5BSCA%5D%20Midas_Vault_Dec2023_P-2023-076_1_20240118%2016_22.pdf?alt=media\&token=2c58f6f7-889e-4c64-ac84-35bad59eb51a)) and once by [Sherlock](https://audits.sherlock.xyz/contests/332).

## Will I be charged fees while in the vault?

A 20% performance fee will apply, prorated based on how long your funds remain in the vault.

## What are the risks involved?

Liquid vaults carry smart contract risks along with varying levels of economic risk. This particular vault engages in liquidity provision, which may lead to impermanent loss.

## Who provides risk oversight?&#x20;

[RockawayX](https://rockawayx.com/) offers an institutional-grade approach to managing DeFi vaults, providing secure, risk-managed access to market-neutral strategies. Drawing on experience across decentralized finance and private credit, the strategist focuses on delivering consistent returns with controlled volatility. Over four years of operation, the strategy has maintained a strong track record with no defaults, bad debt, or liquidations, reflecting a disciplined approach to risk management in digital asset credit markets.


# liquidHYPE vault

An automated, non custodial DeFi strategy for your beHYPE. The vault automates allocation of your beHYPE across HyperEVM ecosystem to earn yield and points.

{% hint style="success" %}
[Deposit into the liquidHYPE vault now](https://app.hyperbeat.org/vaults/liquidhype)
{% endhint %}

## Strategist

Hyperbeat core is the strategist for the liquidHYPE vault.&#x20;

## Risk Oversight

[RockawayX](https://rockawayx.com/)

## Infrastructure

[Hyperbeat Core](https://hyperbeat.org/) is the infrastructure provider.

## Vault Address

[liquidHYPE](https://hyperevmscan.io/address/0x441794D6a8F9A3739F5D4E98a728937b33489D29)

## Performance fee

0%

## Proof of solvency

[liquidHYPE proof of solvency](https://accountable.hyperbeat.org/liquidHYPE)

## FAQs

## What is the liquidHYPE vault?

The liquidHYPE vault is an automated DeFi strategy vault that provides users a simple access point to use their beHYPE in the HyperEVM ecosystem. Assets are deployed to generate real yield and earn exclusive incentives from partners.

## What happens to deposited assets?

Deposited assets are deployed into HyperEVM protocols to generate real yield and earn exclusive incentives.

## How do I withdraw my yield earned on liquidHYPE?

Your yield earned is directly derived from; and attributed to the growth in the exchange rate of liquidHYPE. For example: If I my entry point was 1 liquidHYPE = 1.0000 WHYPE and I deposited 100 WHYPE, and now the exchange rate shows 1 liquidHYPE = 1.027293 WHYPE, your yield earned is (100 \* 0.027293 = 2.7293 WHYPE ). You can realise this accrued yield by withdrawing it from the vault.

## Can I withdraw from the liquidHYPE vault?

Yes, you can withdraw from the liquidHYPE vault. There are two withdrawal options available: Instant Redemption and Classic Redemption. Instant Redemption allows for immediate withdrawals when there is sufficient liquidity, but incurs a 0.5% early withdrawal fee. Alternatively, users can select the Classic Redemption option, which processes the withdrawal within 2 days without slippage or fees.

## Why do withdrawals take two days?&#x20;

Assets are used in on-chain strategies that need time to unwind safely. The two day withdrawal period helps avoid slippage and ensures efficient exits.

## Is the liquidHYPE vault audited?

Yes, three times, twice by Hacken ([1](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F1wxK6TgqaRsSgt3ixVMx%2FMidas_SC%20Audit%20Report_25092023_%5BSA-1833%5D%20-%20POST%20REMEDIATION.pdf?alt=media\&token=cdcf6533-7366-42db-9d3b-224efac85b9a), [2](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F38N1bo36K8FLriRrPDXb%2FHacken_Midas_%5BSCA%5D%20Midas_Vault_Dec2023_P-2023-076_1_20240118%2016_22.pdf?alt=media\&token=2c58f6f7-889e-4c64-ac84-35bad59eb51a)) and once by [Sherlock](https://audits.sherlock.xyz/contests/332).

## Will I be charged fees while in the vault?

The performance fee is not currently live on the liquidHYPE vault.

## What are the risks involved?

Liquid vaults carry smart contract risks along with varying levels of economic risk. This particular vault engages in liquidity provision, which may lead to impermanent loss.

## Who provides risk oversight?&#x20;

[RockawayX](https://rockawayx.com/) offers an institutional-grade approach to managing DeFi vaults, providing secure, risk-managed access to market-neutral strategies. Drawing on experience across decentralized finance and private credit, the strategist focuses on delivering consistent returns with controlled volatility. Over four years of operation, the strategy has maintained a strong track record with no defaults, bad debt, or liquidations, reflecting a disciplined approach to risk management in digital asset credit markets.


# XAUt (Gold) Vault

The best risk-adjusted return on your XAUt, dynamically allocating capital through strategies typically exclusive to institutions now democratised for all.

{% hint style="success" %}
[Deposit into the Hyperbeat XAUt vault now](https://app.hyperbeat.org/vaults/xaut)
{% endhint %}

## Strategist

Hyperbeat core is the strategist for the XAUt vault.&#x20;

## Risk Oversight

[RockawayX](https://rockawayx.com/)

## Infrastructure

[Hyperbeat Core](https://hyperbeat.org/) is the infrastructure provider.

## Vault Address

[hbXAUt](https://purrsec.com/address/0x6EB6724D8D3D4FF9E24d872E8c38403169dC05f8)

## Performance fee

10%

## Proof of solvency

[hbXAUt proof of solvency](https://accountable.hyperbeat.org/hbXAUT)

## FAQs

## What is the Hyperbeat XAUt (Gold) vault?

The Hyperbeat XAUt (Gold) vault is an automated DeFi strategy vault that provides users a simple access point to use their XAUt in the HyperEVM ecosystem. Assets are deployed to generate real yield and earn exclusive incentives from partners.

## What happens to deposited assets?

Deposited assets are deployed into HyperEVM protocols to generate real yield and earn incentives.

## Can I withdraw from the Hyperbeat XAUt (Gold) vault?

Yes, you can withdraw from the Hyperbeat XAUt vault. However, please note that withdrawals are subject to a processing period and may take up to two days to complete.

## Why do withdrawals take two days?&#x20;

Assets are used in on-chain strategies that need time to unwind safely. The two day withdrawal period helps avoid slippage and ensures efficient exits.

## Is the Hyperbeat XAUt vault audited?

Yes, three times, twice by Hacken ([1](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F1wxK6TgqaRsSgt3ixVMx%2FMidas_SC%20Audit%20Report_25092023_%5BSA-1833%5D%20-%20POST%20REMEDIATION.pdf?alt=media\&token=cdcf6533-7366-42db-9d3b-224efac85b9a), [2](https://2732961456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsPjk0ggBxEJCCnVFFkDR%2Fuploads%2F38N1bo36K8FLriRrPDXb%2FHacken_Midas_%5BSCA%5D%20Midas_Vault_Dec2023_P-2023-076_1_20240118%2016_22.pdf?alt=media\&token=2c58f6f7-889e-4c64-ac84-35bad59eb51a)) and once by [Sherlock](https://audits.sherlock.xyz/contests/332).

## Will I be charged fees while in the vault?

A 10% performance fee will apply, prorated based on how long your funds remain in the vault.

## What are the risks involved?

Liquid vaults carry smart contract risks along with varying levels of economic risk.

## Who provides risk oversight?&#x20;

[RockawayX](https://rockawayx.com/) offers an institutional-grade approach to managing DeFi vaults, providing secure, risk-managed access to market-neutral strategies. Drawing on experience across decentralized finance and private credit, the strategist focuses on delivering consistent returns with controlled volatility. Over four years of operation, the strategy has maintained a strong track record with no defaults, bad debt, or liquidations, reflecting a disciplined approach to risk management in digital asset credit markets.

\
\
\
\ <br>

\
\
\
\ <br>

\
\
\
\ <br>

\
\
\
\ <br>


# Delta-Neutral Tokens (dnTokens)

Earn real, market‑neutral yield from perpetual funding payments on Hyperliquid.

Designed for efficiency and performance over the long term, these tokens automatically earn real yield from funding rates paid by leverage traders on Hyperliquid while limiting market exposure. Built for users, protocols and institutions.

<figure><img src="/files/7IZIL6XPzSDpJlqcHKq4" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
[Deposit into dnTokens here](https://app.hyperbeat.org/vaults/dnhype)
{% endhint %}

## How it works

{% stepper %}
{% step %}

### Deposit stablecoins

i.e. USDT0, with USDC and other deposit assets coming soon.
{% endstep %}

{% step %}

### A delta-neutral position is opened on HyperCore

The execution engine opens an optimized delta-neutral position e.g. spot leg holding Unit assets or yield bearing assets, and a matched perpetual short on Hyperliquid, so net delta ≈ 0 limiting market exposure. With each dnToken operating a single asset strategy e.g. dnHYPE and HYPE.

{% hint style="info" %}
*Funding can flip negative, see* [*risks*](#risks) *for more info.*
{% endhint %}
{% endstep %}

{% step %}

### Capture yield

Earn from perpetual funding payments, paid by leverage traders on Hyperliquid and yield from the spot leg (when yield bearing e.g. beHYPE).

{% hint style="info" %}
*Funding APY changes frequently, is short‑lived and compresses with inflows; frequent deposits and withdrawals compound spread/fee drag. dnTokens are designed for long term real yield on your stablecoins.*
{% endhint %}
{% endstep %}

{% step %}

### Rebalance and protect

Our dedicated execution engine rebalances, manages margin, and proactively reduces exposure near liquidation thresholds. If needed, it closes and reopens positions to maintain neutrality.
{% endstep %}

{% step %}

### Automated, set and forget

dnTokens automatically accrue yield into the token price, without any user action needed.
{% endstep %}

{% step %}

### Utilize in defi

All dnTokens are fungible ERC20 tokens, they can be used across DeFi with multiple integrations coming across the Hyperliquid ecosystem and then beyond.&#x20;
{% endstep %}
{% endstepper %}

## Architecture

* **Purpose‑built execution:** The Hyperbeat execution stack dynamically hedges, monitors, and automates rebalancing to maintain neutralisty.
* **Long term, stablecoin yield:** dnTokens prioritize funding yield on stables. Automating spot and perp based strategies, minimizing directional risk to generate cash‑denominated returns from funding payments.
* **Unit expansion:** Uses Unit assets to broaden asset coverage, including spot‑only yield pathways where appropriate.
* **Native to Hyperliquid:** dnTokens integrate directly with HyperCore for real‑time spot/perp execution and data feeds.
* **Sourced from Hyperliquid:** APY net of all fees updates directly via the Hyperliquid API to reflect current funding conditions.
* **Fees aligned with users:** 10% performance fee charged only on PnL and net of all execution costs (e.g. Hyperliquid trading fees).
* **Open Access:** Open to all users, strategies previously available to the few, now available to all. No Min or Max deposit. Asset‑level TVL caps are in place to start, scaling dynamically over time.
* **Composable:** Strategies are tokenised to plug into DeFi enabling lending use cases such as yield tokenisation and onchain leverage.

## FAQs

### What is delta‑neutral?

Balancing long spot and short perp (equal size) so net delta ≈ 0, isolating funding payment yield from from price movements.

### What happens to the deposited assets?

They are deployed on HyperCore to run an automated delta‑neutral strategy, holding Unit/yield-bearing assets for the spot-leg and shorting the corresponding perpetual market on Hyperliquid to create a delta-netural position. Each dnToken runs a single strategy on one asset e.g. dnHYPE and HYPE.

### Where does yield come from?

This strategy captures yield from [perpetual funding payments](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/funding), paid by long traders on Hyperliquid, yield bearing spot assets (when applicable) and any additional incentives.

### How long do withdrawals take?

During the bootstrapping phase, withdrawals are processed in 1-3 days. As safeguards taper, withdrawals will be processed in real-time. A withdrawal closes both spot and perp legs and incurs HL trading, spread, and potential slippage costs. Safe unwinds depend on orderbook liquidity and volatility; aggressive exits can incur execution costs that eat into yield, hence the staged approach.

The vault mandate is to maximize yield for depositors. Users always maintain the right to withdraw their capital and have direct flow through to strategy deposits.

{% hint style="info" %}
Exiting during calmer periods can reduce execution drag, at times positive spreads slightly improve exit value.
{% endhint %}

### How are fees charged?

10% Performance fee, charged only on yield. If the strategy does not earn i.e. when funding is negative, fees are not charged. No hidden fees. Hyperbeat applies its referral code automatically for a trading‑fee discount and trading fee rebate.

### What are the risks?

Market risk is managed through design, monitoring, and active rebalancing to maintain neutrality. However, unexpected events such as sudden volatility spikes, Hyperliquid downtimes, shallow market depth, latency issues, or sharp funding rate reversals can temporarily disrupt the balance between spot and perp positions, reducing or even negating expected yields. APY can swing more than diversified vaults that smooth returns with other yield sources. Funding spikes are short‑lived and compress with inflows; frequent switching compounds spread/fee drag, these tokens are designed for long term yield.

### How is risk managed?

Through dynamic rebalancing, liquidation avoidance, and real‑time performance monitoring. Several mechanisms are maintained to preserve capital integrity such as a real-time execution engine for dynamic rebalancing, liquidation avoidance, real-time performance monitoring. Users always retain the right to withdraw; strategy flows are directly connected to vault deposits.

## Risks

While delta‑neutral structures reduce market direction risk, they are not risk‑free.

### Potential risk factors

* Market & funding dynamics: Sudden volatility or funding reversals can dampen or negate expected yield; neutrality is maintained but returns vary.
* Infrastructure dependency: If Hyperliquid experiences downtime or maintenance, execution and (temporarily) withdrawals may be affected.
* Stablecoin issuer risk: Depeg/issuer events can impact deposits.
* Execution frictions: Depth/latency/slippage, particularly on volatile/illiquid assets, can add costs.
* Volatility spikes that momentarily unbalance spot/perp legs.
* Exchange/infra events (e.g., Hyperliquid downtime), market depth limits, or latency.
* Funding reversals or sharp changes that can reduce/negate expected yield.
* Institutional delegation: Understand Agent permissions and avoid manual sub‑account actions.

### Risk controls

* Low‑leverage design; proactive rebalancing and liquidation avoidance
* Real‑time monitoring and safety caps; always‑on withdrawal access with market‑aware safeguards.
* Real‑time execution engine for fast, dynamic rebalancing.
* Liquidation avoidance parameters, monitoring, proactive and reactive defenses.
* 24/7 performance & risk telemetry with active controls.

***

Disclosures

This page is for informational purposes only and does not constitute investment advice. Yields are variable and not guaranteed. Capital is at risk.<br>


# dnHYPE

This yield-bearing token represents a pooled delta-neutral position on $HYPE. Earn real yield from funding payments paid by leverage traders on Hyperliquid and yield from the spot leg where applicable. dnTokens (ERC-20) are fully composable with DeFi.

{% hint style="success" %}
[Deposit into dnHYPE now](https://app.hyperbeat.org/vaults/dnhype)
{% endhint %}


# dnPUMP

This yield-bearing token represents a pooled delta-neutral position on $PUMP. Earn real yield from funding payments paid by leverage traders on Hyperliquid and yield from the spot leg where applicable. dnTokens (ERC-20) are fully composable with DeFi.

{% hint style="success" %}
[Deposit into dnPUMP now](https://app.hyperbeat.org/vaults/dnpump)
{% endhint %}


# dnBTC

Coming soon.


# dnETH

Coming soon.


# dnFART

Coming soon.


# dnSOL

Coming soon.


# dnXPL

Coming soon.


# Morphobeat

Hyperliquid native money market, powered by Morpho.\
\
Each market is isolated (meaning risks are contained within each individual market), immutable (cannot be changed after deployment), and will persist as long as the blockchain it deployed on is live.

{% hint style="success" %}
[Start using Morphobeat here](https://app.hyperbeat.org/morphobeat)
{% endhint %}


# Supply Vaults

A Morpho Vault is a vault that lets you deposit a single asset (like HYPE or USDT0) and automatically spreads your funds across multiple **lending markets** to earn yield. You don’t have to manage risk or pick markets yourself—the vault does it for you, using automated risk management and expert curation. You can withdraw your funds at any time, as long as there’s enough liquidity.

{% hint style="success" %}
[Use Morphobeat here](https://app.hyperbeat.org/morphobeat)
{% endhint %}

## Key points

* Deposit once, earn yield from multiple markets.
* Automated risk management managed by Curators —no need to pick or monitor markets yourself.
* Withdraw anytime (subject to available liquidity).
* Built on the Morpho protocol, using the ERC-4626 vault standard.

## FAQs

### **What is a Morpho Vault?**

A Morpho Vault is a permissionless lending vault that lets users deposit a single asset and automatically allocates those funds across multiple Morpho Markets to earn yield. Vaults manage risk and optimize returns on your behalf.

### **How do Morpho Vaults manage risk?**

Vaults use automated risk management, with [curators](broken://pages/TFao9DqCsVARouE4l6y7) selecting which markets to allocate funds to based on risk profiles. Allocators can rebalance funds as needed, and all changes are subject to timelocks for transparency and user protection.

### **What are curators?**

A **Curator** is an entity who aims to optimize the risk-adjusted returns for depositors based on a given strategy. Curators are specifically responsible for the strategic curation of vaults, making key decisions about which markets to include, how capital is allocated, and how risk is curated within the vault structure. Their expertise directly impacts vault performance and security.

### **Which Curators does Hyperbeat work with?**

Hyperbeat works with [Gauntlet](https://www.gauntlet.xyz/) and [MEV Capital](https://mevcapital.com/) as curators, two of the largest and most experiences risk managers in the industry.&#x20;

### **Can I withdraw my funds at any time?**

Yes, users can withdraw their liquidity at any time, as long as there is sufficient liquidity available in the vault and underlying markets.

### **What assets can I deposit into a Morpho Vault?**

Each vault supports a single loan asset (e.g., USDC, ETH). The supported asset is determined at vault creation.

### **What are the main risks of using Morpho Vaults?**

Risks include smart contract vulnerabilities, oracle risk, counterparty risk, liquidation risk, and liquidity risk. Users should review the risk documentation before depositing.

### **Are Morpho Vaults audited?**

Yes, Morpho Vaults and the underlying protocol have undergone [multiple audits](https://docs.morpho.org/getting-started/resources/audits/) and follow industry-leading security practices, including formal verification and bug bounty programs.<br>


# HYPE

The HYPE Vaults will whitelist a selection of liquid collateral markets and allocate across them to optimize risk-adjusted yield.&#x20;

## Curators

* [MEV Capital](/morphobeat/supply-vaults/hype/mev-capital-hype)
* [Gauntlet](/morphobeat/supply-vaults/hype/gauntlet-hype)
* [Hyperithm](/morphobeat/supply-vaults/hype/hyperithm-hype)
* [Re7](/morphobeat/supply-vaults/hype/re7-hype)


# MEV Capital HYPE

The HYPE Vault will whitelist a selection of liquid collateral markets and allocate across them to optimize risk-adjusted yield.

{% hint style="success" %}
[Deposit into the MEV WHYPE vault here ](https://app.hyperbeat.org/earn/0xd19e3d00f8547f7d108abfd4bbb015486437b487)
{% endhint %}

## Curator

[MEV Capital](https://mevcapital.com/)

## Underlying Markets

Individual Morpho Markets that the HYPE vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>wstHYPE/wHYPE</td><td><a href="https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9">https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9</a></td><td>91.5%</td></tr><tr><td>hbHYPE/wHYPE</td><td><a href="https://purrsec.com/address/0x96C6cBB6251Ee1c257b2162ca0f39AA5Fa44B1FB">https://purrsec.com/address/0x96C6cBB6251Ee1c257b2162ca0f39AA5Fa44B1FB</a></td><td>91.5%</td></tr><tr><td></td><td></td><td></td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0xb830b8b1a41c38603dbc6e4b562ff599edb415c4)
* [Timelock/Guardian](https://purrsec.com/address/0xaab003e68b80a721a90235132a8da1da0a9ef383)
* [Vault contract](https://purrsec.com/address/0xd19e3d00f8547f7d108abfd4bbb015486437b487)


# Re7 HYPE

The Re7 HYPE vault curated by Re7 Labs is intended to seamlessly allocate HYPE liquidity to various Morpho markets.

{% hint style="success" %}
[Deposit into the RE7 HYPE Vault here ](https://app.hyperbeat.org/morphobeat/vault/0x182b318A8F1c7C92a7884e469442a610B0e69ed2)
{% endhint %}

## Curator

[Re7](https://re7.capital/)

## Underlying Markets

Individual Morpho Markets that the HYPE vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>wstHYPE</td><td><a href="https://purrsec.com/address/0xF92cCE636920d3835b135EA1D58bead4E2D62B15">https://purrsec.com/address/0xF92cCE636920d3835b135EA1D58bead4E2D62B15</a></td><td>91.50%</td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0x036845F9BE6DF938Da01Abe33e056D3CcaA836a2)
* [Timelock/Guardian](https://hyperevmscan.io/address/0x0000000000000000000000000000000000000000)
* [Vault contract](https://purrsec.com/address/0x3bcc0a5a66bb5bdceef5dd8a659a4ec75f3834d8)


# Gauntlet HYPE

The Gauntlet wHYPE Vault will whitelist a selection of liquid collateral markets and allocate across them to optimize risk-adjusted yield. The Vault's risk strategy will follow the CORE framework, where Gauntlet curates deposits to balance security and yield to provide a moderate risk profile and competitive APY for wHYPE suppliers.

{% hint style="success" %}
[Deposit into the Gauntlet HYPE Vault here ](https://app.hyperbeat.org/morphobeat/vault/0x264a06Fd7A7C9E0Bfe75163b475E2A3cc1856578)
{% endhint %}

## Curator

[Gauntlet](https://www.gauntlet.xyz/)

## Underlying Markets

Individual Morpho Markets that the HYPE vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>hbHYPE</td><td><a href="https://purrsec.com//address/0x4001c9187623793C20e59b692C159B72DaB48A51">https://purrsec.com//address/0x4001c9187623793C20e59b692C159B72DaB48A51</a></td><td>91.50%</td></tr><tr><td>wstHYPE</td><td><a href="https://purrsec.com//address/0xF92cCE636920d3835b135EA1D58bead4E2D62B15">https://purrsec.com//address/0xF92cCE636920d3835b135EA1D58bead4E2D62B15</a></td><td>91.50%</td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0x09346F40e324458A8E211C5317981C78FAcDEc57)
* [Timelock/Guardian](https://purrsec.com/address/0x0685bf23B2f8EA5Fb762427ea0427Eb7fc065E8f)
* [Vault contract](https://purrsec.com/address/0x264a06Fd7A7C9E0Bfe75163b475E2A3cc1856578)


# Hyperithm HYPE

Hyperithm HYPE vault maximizes yield by actively integrating unique collaterals, offering borrowers high-return opportunities through dynamic optimization, all while maintaining strong risk management.

{% hint style="success" %}
[Deposit into the Hyperithm HYPE Vault here ](https://app.hyperbeat.org/morphobeat/vault/0x92B518e1cD76dD70D3E20624AEdd7D107F332Cff)
{% endhint %}

## Curator

[Hyperithm](https://www.hyperithm.com/)

## Underlying Markets

Individual Morpho Markets that the HYPE vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>hbHYPE</td><td><a href="https://purrsec.com/address/0x4001c9187623793C20e59b692C159B72DaB48A51">https://purrsec.com/address/0x4001c9187623793C20e59b692C159B72DaB48A51</a></td><td>91.50%</td></tr><tr><td>wstHYPE</td><td><a href="https://purrsec.com/address/0xF92cCE636920d3835b135EA1D58bead4E2D62B15">https://purrsec.com/address/0xF92cCE636920d3835b135EA1D58bead4E2D62B15</a></td><td>91.50%</td></tr><tr><td>kHYPE</td><td><a href="https://purrsec.com/address/0xdc55D8D3276ce1224122196B3D75E7074B6e32D6">https://purrsec.com/address/0xdc55D8D3276ce1224122196B3D75E7074B6e32D6</a></td><td>91.5%</td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0x35e42A5cA87A4E4Fb235585B36d7c978eA72B290)
* [Timelock/Guardian](https://purrsec.com/address/0x92B518e1cD76dD70D3E20624AEdd7D107F332Cff) (none??)
* [Vault contract](https://purrsec.com/address/0x3bcc0a5a66bb5bdceef5dd8a659a4ec75f3834d8)


# USDT0

The USDT0 Vaults will whitelist a selection of liquid collateral markets and allocate across them to optimize risk-adjusted yield.&#x20;

## Curators

* [MEV Capital](/morphobeat/supply-vaults/usdt0/mev-capital-usdt0)
* [Gauntlet](/morphobeat/supply-vaults/usdt0/gauntlet-usdt0)
* [Hyperithm](/morphobeat/supply-vaults/usdt0/hyperithm-usdt0)
* [Re7](/morphobeat/supply-vaults/usdt0/re7-usdt0)


# MEV Capital USDT0

The MEV Capital USDT0 vault provides a set of liquid collateral markets with an optimized risk-adjusted return through an active rebalancing strategy

{% hint style="success" %}
[Deposit into the MEV Capital USDT0 Vault here ](https://app.hyperbeat.org/earn/0x3bcc0a5a66bb5bdceef5dd8a659a4ec75f3834d8)
{% endhint %}

## Curator

[MEV Capital](https://www.mevcapital.com/)

## Underlying Markets

Individual Morpho Markets that the USDT vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>hbUSDT/USDT0</td><td><a href="https://purrsec.com/address/0x5e105266db42f78FA814322Bce7f388B4C2e61eb">https://purrsec.com/address/0x5e105266db42f78FA814322Bce7f388B4C2e61eb</a></td><td>91.50%</td></tr><tr><td>Pendle PT-hbUSDT 18DEC2025</td><td><a href="https://purrsec.com/address/0xCb87A2524cEd4E4c23ddB1CDE5E620530E328f9A">https://purrsec.com/address/0xCb87A2524cEd4E4c23ddB1CDE5E620530E328f9A</a></td><td>91.50%</td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0xb830B8B1A41c38603dBC6E4b562Ff599eDB415C4)
* [Timelock/Guardian](https://purrsec.com/address/0xaaB003e68b80a721A90235132A8dA1DA0A9ef383)
* [Vault contract](https://purrsec.com/address/0x3bcc0a5a66bb5bdceef5dd8a659a4ec75f3834d8)


# Gauntlet USDT0

The Gauntlet USDT0 Vault will whitelist a selection of liquid collateral markets and allocate across them to optimize risk-adjusted yield. The Vault's risk strategy will follow the CORE framework, where Gauntlet curates deposits to balance security and yield to provide a moderate risk profile and competitive APY for USDT0 suppliers.

{% hint style="success" %}
[Deposit into the Gauntlet USDT0 Vault here ](https://app.hyperbeat.org/morphobeat/vault/0x53A333e51E96FE288bC9aDd7cdC4B1EAD2CD2FfA)
{% endhint %}

## Curator

[Gauntlet](https://www.gauntlet.xyz/)

## Underlying Markets

Individual Morpho Markets that the USDT vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>wHYPE/USDT0</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/HYPE/">https://app.redstone.finance/app/feeds/hyperevm/HYPE/</a></td><td>77%</td></tr><tr><td>wstHYPE/USDT0</td><td><a href="https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9">https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9</a></td><td>77%</td></tr><tr><td>UBTC/USDT0</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/btc/">https://app.redstone.finance/app/feeds/hyperevm/btc/</a></td><td>86%</td></tr><tr><td>UETH/USDT0</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/eth/">https://app.redstone.finance/app/feeds/hyperevm/eth/</a></td><td>86%</td></tr><tr><td>sUSDe/USDT0</td><td><a href="https://purrsec.com/address/0x29d295409d5a20b2c851df18054d32a442791346/contract">https://purrsec.com/address/0x29d295409d5a20b2c851df18054d32a442791346/contract</a></td><td>91.5%</td></tr><tr><td>USR/USDT0</td><td><a href="https://purrsec.com/address/0x29d2fEC890B037B2d34f061F9a50f76F85ddBcAE">https://purrsec.com/address/0x29d2fEC890B037B2d34f061F9a50f76F85ddBcAE</a></td><td>91.5%</td></tr><tr><td>kHYPE/USDT0</td><td><a href="https://purrsec.com/address/0xfD739d4e423301CE9385c1fb8850539D657C296D">https://purrsec.com/address/0xfD739d4e423301CE9385c1fb8850539D657C296D</a></td><td>77.00%</td></tr><tr><td>hbUSDT/USDT0</td><td><a href="https://purrsec.com/address/0x5e105266db42f78FA814322Bce7f388B4C2e61eb">https://purrsec.com/address/0x5e105266db42f78FA814322Bce7f388B4C2e61eb</a></td><td>86.00%</td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0x09346f40e324458a8e211c5317981c78facdec57)
* [Timelock/Guardian](https://purrsec.com/address/0x0685bf23b2f8ea5fb762427ea0427eb7fc065e8f)
* [Vault contract](https://purrsec.com/address/0x53a333e51e96fe288bc9add7cdc4b1ead2cd2ffa)


# Hyperithm USDT0

The Hyperithm USDT0 Vault quickly integrates unique, secure collateral assets to maximize yield, offering borrowers high-return opportunities through proactive optimization while maintaining robust risk management.

{% hint style="success" %}
[Deposit into the Hyperithm USDT0 Vault here ](https://app.hyperbeat.org/morphobeat/vault/0xe5ADd96840F0B908ddeB3Bd144C0283Ac5ca7cA0)
{% endhint %}

## Curator

[Hyperithm](https://www.hyperithm.com/)

## Underlying Markets

Individual Morpho Markets that the USDT vault allocates deposited assets to in order to generate yield.

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>wHYPE/USDT0</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/HYPE/">https://app.redstone.finance/app/feeds/hyperevm/HYPE/</a></td><td>77%</td></tr><tr><td>wstHYPE/USDT0</td><td><a href="https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9">https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9</a></td><td>77%</td></tr><tr><td>UBTC/USDT0</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/btc/">https://app.redstone.finance/app/feeds/hyperevm/btc/</a></td><td>86%</td></tr><tr><td>UETH/USDT0</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/eth/">https://app.redstone.finance/app/feeds/hyperevm/eth/</a></td><td>86%</td></tr><tr><td>sUSDe/USDT0</td><td><a href="https://purrsec.com/address/0x29d295409d5a20b2c851df18054d32a442791346/contract">https://purrsec.com/address/0x29d295409d5a20b2c851df18054d32a442791346/contract</a></td><td>91.5%</td></tr><tr><td>hbUSDT/USDT0</td><td><a href="https://purrsec.com/address/0x5e105266db42f78FA814322Bce7f388B4C2e61eb">https://purrsec.com/address/0x5e105266db42f78FA814322Bce7f388B4C2e61eb</a></td><td>86.00%</td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0x35e42A5cA87A4E4Fb235585B36d7c978eA72B290)
* [Timelock/Guardian](https://purrsec.com/address/0x0000000000000000000000000000000000000000)
* [Vault contract](https://purrsec.com/address/0xe5add96840f0b908ddeb3bd144c0283ac5ca7ca0)


# Re7 USDT0

The Re7 USDT0 vault curated by Re7 Labs is intended to seamlessly allocate USDT0 liquidity to various Morpho markets.

{% hint style="success" %}
[Deposit into the Re7 Capital USDT0 Vault here ](https://app.hyperbeat.org/morphobeat/vault/0x51F64488d03D8B210294dA2BF70D5db0Bc621B0c)
{% endhint %}

## Curator

[Re7](https://re7.capital/)

## Underlying Markets

Individual Morpho Markets that the USDT vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>UBTC</td><td><a href="https://purrsec.com/address/0xf4693c969b2c619A9B468cD1078bc51084EAd96e">https://purrsec.com/address/0xf4693c969b2c619A9B468cD1078bc51084EAd96e</a></td><td>91.50%</td></tr><tr><td>WHYPE</td><td><a href="https://purrsec.com/address/0xBa7263Ed5d7E825B5cd991705f39eCDA281b2C58">https://purrsec.com/address/0xBa7263Ed5d7E825B5cd991705f39eCDA281b2C58</a></td><td>91.50%</td></tr><tr><td>UETH</td><td><a href="https://purrsec.com/address/0x06dAfb8aBe56F9fCeBfac3b71Cf004312261FD95">https://purrsec.com/address/0x06dAfb8aBe56F9fCeBfac3b71Cf004312261FD95</a></td><td>86.00%</td></tr><tr><td>USDe</td><td><a href="https://purrsec.com/address/0x11dCf08f1260b30015ec85b58c9f7d1D47dCF27C">https://purrsec.com/address/0x11dCf08f1260b30015ec85b58c9f7d1D47dCF27C</a></td><td>86.00%</td></tr><tr><td>wstHYPE</td><td><a href="https://purrsec.com/address/0x3A459D5ec6C576d56D40Dd58aE6ba337ED8D6752">https://purrsec.com/address/0x3A459D5ec6C576d56D40Dd58aE6ba337ED8D6752</a></td><td>77.00%</td></tr><tr><td>hbUSDT</td><td><a href="https://purrsec.com/address/0x79eD085F7E43acF66f91e9B9375555d1b0B91a69">https://purrsec.com/address/0x79eD085F7E43acF66f91e9B9375555d1b0B91a69</a></td><td>91.50%</td></tr><tr><td>Idle</td><td></td><td></td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0x036845F9BE6DF938Da01Abe33e056D3CcaA836a2)
* [Timelock/Guardian](https://purrsec.com/address/0xaaB003e68b80a721A90235132A8dA1DA0A9ef383) (update once we have)
* [Vault contract](https://purrsec.com/address/0x51F64488d03D8B210294dA2BF70D5db0Bc621B0c)


# USDe

The USDe Vault will whitelist a selection of liquid collateral markets and allocate across them to optimize risk-adjusted yield.

{% hint style="success" %}
[Deposit into the Gauntlet USDe Vault here ](https://app.hyperbeat.org/earn/0x5eec795d919fa97688fb9844eeb0072e6b846f9d)
{% endhint %}

## Curator

[Gauntlet](https://www.gauntlet.xyz/)

## Underlying Markets

Individual Morpho Markets that the HYPE vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>wHYPE/USDe</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/HYPE/">https://app.redstone.finance/app/feeds/hyperevm/HYPE/</a></td><td>77%</td></tr><tr><td>wstHYPE/USDe</td><td><a href="https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9">https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9</a></td><td>77%</td></tr><tr><td>UBTC/USDe</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/btc/">https://app.redstone.finance/app/feeds/hyperevm/btc/</a></td><td>86%</td></tr><tr><td>UETH/USDe</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/eth/">https://app.redstone.finance/app/feeds/hyperevm/eth/</a></td><td>86%</td></tr><tr><td>sUSDe/USDe</td><td><a href="https://purrsec.com/address/0x29d295409d5a20b2c851df18054d32a442791346/contract">https://purrsec.com/address/0x29d295409d5a20b2c851df18054d32a442791346/contract</a></td><td>91.5%</td></tr><tr><td>USR/USDe</td><td><a href="https://purrsec.com/address/0x29d2fEC890B037B2d34f061F9a50f76F85ddBcAE">https://purrsec.com/address/0x29d2fEC890B037B2d34f061F9a50f76F85ddBcAE</a></td><td>91.5%</td></tr><tr><td>hbUSDT/USDe</td><td><a href="https://purrsec.com/address/0x5e105266db42f78FA814322Bce7f388B4C2e61eb">https://purrsec.com/address/0x5e105266db42f78FA814322Bce7f388B4C2e61eb</a></td><td>86.00%</td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0x09346f40e324458a8e211c5317981c78facdec57)
* [Timelock/Guardian](https://purrsec.com/address/0x0685bf23b2f8ea5fb762427ea0427eb7fc065e8f)
* [Vault contract](https://purrsec.com/address/0x5eec795d919fa97688fb9844eeb0072e6b846f9d)


# UETH

The UETH Vault will whitelist a selection of liquid collateral markets and allocate across them to optimize risk-adjusted yield.

{% hint style="success" %}
[Deposit into the Gauntlet UETH Vault here ](https://app.hyperbeat.org/earn/0x0571362ba5ea9784a97605f57483f865a37dbeaa)
{% endhint %}

## Curator

[Gauntlet](https://www.gauntlet.xyz/)

## Underlying Markets

Individual Morpho Markets that the UETH vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>UBTC/UETH</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/btc/">https://app.redstone.finance/app/feeds/hyperevm/btc/</a></td><td>86%</td></tr><tr><td>cmETH/UETH</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/eth/">https://app.redstone.finance/app/feeds/hyperevm/eth/</a></td><td>91.5%</td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0x09346f40e324458a8e211c5317981c78facdec57)
* [Timelock/Guardian](https://purrsec.com/address/0x0685bf23b2f8ea5fb762427ea0427eb7fc065e8f)
* [Vault contract](https://purrsec.com/address/0x0571362ba5ea9784a97605f57483f865a37dbeaa)


# rUSDC

The Relend Network Vault on HyperEVM enables users to supply rUSDC to a diversified set of blue chip lending markets. rUSDC is a stablecoin that can be minted by depositing USDC on Ethereum via [app.relend.network](https://app.relend.network/), and then bridged to HyperEVM. This cross-chain mechanism allows Relend Network to supply stablecoin liquidity across ecosystems. Learn more about rUSDC and associated risks in the [official documentation](https://docs.relend.network/relend.docs/rusdc-mechanism-and-risk-disclosure).

{% hint style="success" %}
[Deposit into the Relend Network rUSDC vault here ](https://app.hyperbeat.org/earn/0x4346c98e690c17efbb999ae8e1da96b089be320b)
{% endhint %}

## Curator

[Relend](https://relend.network/)

## Underlying Markets

Individual Morpho Markets that the rUSDC vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>wHYPE/rUSDC</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/HYPE/">https://app.redstone.finance/app/feeds/hyperevm/HYPE/</a></td><td>77%</td></tr><tr><td>wstHYPE/rUSDC</td><td><a href="https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9">https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9</a></td><td>77%</td></tr><tr><td>UBTC/rUSDC</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/btc/">https://app.redstone.finance/app/feeds/hyperevm/btc/</a></td><td>86%</td></tr><tr><td>UETH/rUSDC</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/eth/">https://app.redstone.finance/app/feeds/hyperevm/eth/</a></td><td>86%</td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0x09346f40e324458a8e211c5317981c78facdec57)
* [Timelock/Guardian](https://purrsec.com/address/0x0685bf23b2f8ea5fb762427ea0427eb7fc065e8f)
* [Vault contract](https://purrsec.com/address/0x53a333e51e96fe288bc9add7cdc4b1ead2cd2ffa)


# USR

The MEV Capital Usual USR provides a set of liquid collateral markets with an optimized risk-adjusted return through an active rebalancing strategy.

{% hint style="success" %}
[Deposit into the MEV Capital USR Vault here ](https://app.hyperbeat.org/earn/0xd3a9cb7312b9c29113290758f5adfe12304cd16a)
{% endhint %}

## Curator

[MEV Capital](https://www.mevcapital.com/)

## Underlying Markets

Individual MEV Capital markets that the USR vault allocates deposited assets to in order to generate yield.&#x20;

<table><thead><tr><th>Asset</th><th data-type="content-ref">Oracle</th><th>LLTV</th></tr></thead><tbody><tr><td>hbUSDT/USDT0</td><td><a href="https://purrsec.com/address/0x5e105266db42f78FA814322Bce7f388B4C2e61eb">https://purrsec.com/address/0x5e105266db42f78FA814322Bce7f388B4C2e61eb</a></td><td>91.50%</td></tr></tbody></table>

## Risk

* [Owner](https://purrsec.com/address/0xb830B8B1A41c38603dBC6E4b562Ff599eDB415C4)
* [Timelock/Guardian](https://purrsec.com/address/0x0000000000000000000000000000000000000000)
* [Vault contract](https://purrsec.com/address/0xd3a9cb7312b9c29113290758f5adfe12304cd16a)


# Collateral Assets

Supported assets that you can use as collateral to borrow liquidity.

<table><thead><tr><th>Collateral Asset</th><th width="223.69921875">Borrow Assets</th><th width="278.58984375" data-type="content-ref">Oracle</th></tr></thead><tbody><tr><td>HYPE</td><td>USDT0</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/hype/">https://app.redstone.finance/app/feeds/hyperevm/hype/</a></td></tr><tr><td>wstHYPE</td><td>WHYPE, USDT0, USDE</td><td><a href="https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9">https://purrsec.com/address/0xe6e8badbb469d16e2060e1ebeb60f92b2a1250a9</a></td></tr><tr><td>UBTC</td><td>USDT0, USDE, UETH</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/ubtc/">https://app.redstone.finance/app/feeds/hyperevm/ubtc/</a></td></tr><tr><td>UETH</td><td>USDT0, USDE</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/eth/">https://app.redstone.finance/app/feeds/hyperevm/eth/</a></td></tr><tr><td>sUDEe</td><td>USDT0, USDE</td><td><a href="https://purrsec.com/address/0x29d295409d5a20b2c851df18054d32a442791346/contract">https://purrsec.com/address/0x29d295409d5a20b2c851df18054d32a442791346/contract</a></td></tr><tr><td>mETH</td><td>UETH</td><td><a href="https://purrsec.com/address/0x5C4c8d6f6Bf79B718F3e8399AaBdFEd01cB7e48f">https://purrsec.com/address/0x5C4c8d6f6Bf79B718F3e8399AaBdFEd01cB7e48f</a></td></tr><tr><td>hbUSDT</td><td>USDTO, USDE, USR</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/hbusdt_fundamental/">https://app.redstone.finance/app/feeds/hyperevm/hbusdt_fundamental/</a></td></tr><tr><td>Pendle PT-hbUSDT 18DEC2025</td><td>USDT0</td><td><a href="https://purrsec.com/address/0xCb87A2524cEd4E4c23ddB1CDE5E620530E328f9A">https://purrsec.com/address/0xCb87A2524cEd4E4c23ddB1CDE5E620530E328f9A</a></td></tr><tr><td>RLP</td><td>USR</td><td><a href="https://purrsec.com/address/0xd6156F8177aA1a6E0c5278CE437A9BDB32F203ef">https://purrsec.com/address/0xd6156F8177aA1a6E0c5278CE437A9BDB32F203ef</a></td></tr></tbody></table>


# MasterSwap

MasterSwap is an aggregator of DEX aggregators, we query the price in leading aggregators on HyperEVM and then offer you the best price among all of them.

## What is MasterSwap? <a href="#what-is-masterswap" id="what-is-masterswap"></a>

MasterSwap is a tool that compares **DEX aggregators** on **HyperEVM** and let you chooses the **best price with optimized gas fees**.

Instead of checking multiple platforms yourself, MasterSwap does it in one click with **zero fees**.

{% @arcade/embed flowId="ysUvcrbqrTaQcXALHHmD" url="<https://app.arcade.software/share/ysUvcrbqrTaQcXALHHmD>" %}

{% hint style="success" %}
[Start using Masterswap now](https://app.hyperbeat.org/masterswap)
{% endhint %}

## How it works <a href="#how-it-works" id="how-it-works"></a>

1. **Price comparison** – queries multiple aggregators at once
2. **Smart selection** – lets you pick the route with the highest net return (after fees)
3. **Automatic approvals** – if needed, MasterSwap asks for token approval (you can allow once or unlimited)
4. **Secure execution** – swaps are done directly via the official aggregator contracts
5. **Instant updates** – your balance and transaction status refresh automatically

### Supported aggregators

Here is the list of currently supported DEX aggregators on HyperEVM:

* Liqd
* LI.FI
* OpenOcean
* GlueX
* Hyperbloom
* KyberSwap
* OogaBooga
* Eisen Aggregator
* Hyperflow

{% hint style="success" %}
If you would like your aggregator to be integrated to MasterSwap, [please fill in this form](https://docs.google.com/forms/d/e/1FAIpQLSdsIMT32EsB95n9NcKL6vMtamU5MkkL1RQul2Zo_FK3mK-fJw/viewform?usp=header).
{% endhint %}

## FAQ

### Is MasterSwap safe?

MasterSwap uses the router contract of each aggregator, we don't use any contracts developed by us. Thus you inherit the same security you'd get by swapping directly from their UI instead of ours.

### Does Hyperbeat take fees on swap?

Hyperbeat does not currently charge any fees on swaps.

### Will I get an airdrop if I swap through MasterSwap?

We execute swaps directly against the router of each aggregator, so there's no difference between a swap executed directly from their UI and a swap executed from MasterSwap. Thus, if any of the aggregators we integrate does an airdrop in the future, all swaps made through them would be eligible for their airdrop.


# Hyperbeat Builder Codes

**Builder Codes** allow developers to earn fee revenue by building on top of the Hyperbeat ecosystem—across vaults, liquid staking, and vanilla staking—while leveraging the **Hyperfolio API** for real-time portfolio tracking and data integration.

Builders can route user activity into:

* **Vaults** (HYPE, USDT, BTC, wVLP, dnHYPE and XAUt)
* **Liquid staking** (e.g. beHYPE minting)
* **Vanilla staking** (Direct delegation to the Hyperbeat validator)

Every eligible transaction can include a Builder Code, enabling transparent attribution and revenue sharing. Combined with the Hyperfolio API, builders can create custom frontends, bots, dashboards, and structured products—while tracking user balances, rewards, and performance. This is how you build on yield—and get paid for it.

## How to get started <a href="#how-to-get-started" id="how-to-get-started"></a>

To get started, you’ll need to register a builder address with Hyperbeat:

1. Apply by [filling in this form](https://docs.google.com/forms/d/e/1FAIpQLSd0UdtBSwnweUCFJnuXDe1UoX_ho6jAutdK-6eiTXhJemCBUQ/viewform)
2. Once approved, your builder address will be whitelisted and you’ll be eligible for fee revenue.
3. Start building

### &#x20; <a href="#how-to-get-started" id="how-to-get-started"></a>


# Vaults

Builders can route deposits into any Hyperbeat vault using Hyperbeat builder codes. Each vault has unique characteristics, underlying strategies, and eligible fee logic. Below are vault-specific guidelines.

**Note:** Hyperbeat vaults are built on two different architectures—one used for the **HYPE and UBTC** vaults, and a separate one for the **USDT** vault.

**Vaults integrations :**

* [Hyperbeat Ultra HYPE](/hyperbeat-builder-codes/vaults/hyperbeat-ultra-hype)
* [Hyperbeat Ultra UBTC](/hyperbeat-builder-codes/vaults/hyperbeat-ultra-ubtc)
* [Hyperbeat USDT](/hyperbeat-builder-codes/vaults/hyperbeat-usdt)

[<br>](https://hyperbeat.gitbook.io/hyperbeat-builder-codes)


# Hyperbeat Ultra HYPE

This doc provides the necessary information to integrate the Hyperbeat Ultra HYPE (hbHYPE) vault into your applications.

### General Vault Information

* **Vault Name:** Hyperbeat Ultra HYPE
* **Vault Token Symbol:** hbHYPE
* **Chain:** hyperevm
* **Chain ID:** 999
* **Vault Contract Address:** `0x96C6cBB6251Ee1c257b2162ca0f39AA5Fa44B1FB`
* **Vault Token Decimals (hbHYPE):** 18
* **Main Deposit Token:** WHYPE
  * **Address:** `0x5555555555555555555555555555555555555555`&#x20;
  * **Decimals:** 18

#### Useful Link

* **Contract on explorer:**  [View on hyperscan](https://www.hyperscan.com/address/0x96C6cBB6251Ee1c257b2162ca0f39AA5Fa44B1FB?tab=index)
* **WHYPE Token on explorer:**  [View on hyperscan](https://www.hyperscan.com/token/0x5555555555555555555555555555555555555555)
* **Vault Logo:**  [Brand kit](https://www.hyperbeat.org/brand)

{% file src="/files/Z8Gqf1HvuMOkL87aB4DH" %}
Here is the complete ABI of the contract for reference - OPTIONAL
{% endfile %}

***

## Actions:

### Depositing Tokens

To deposit WHYPE tokens into the hbHYPE vault

**Steps:**

1. **Check Allowance:**\
   Before depositing, check if the vault contract is authorized to spend the user's WHYPE tokens.
   * Call the `allowance(address owner, address spender)` function on the **WHYPE token contract.**
     * `owner`: User's address.
     * `spender`: hbHYPE vault contract address.
2. **Approve Spending if necessary:**\
   If the allowance is less than the amount to deposit, the user must approve the vault contract.
   * Call the `approve(address spender, uint256 value)` function on the **WHYPE token contract.**
     * `spender`: hbHYPE vault contract address.
     * `value`: Amount of WHYPE to approve (in atomic units, e.g., `amount * 10**18`).
3. **Perform Deposit:**\
   Once sufficient approval is granted, call the `deposit(uint256 assets, address receiver)` function on the **hbHYPE vault contract.**
   * `assets`: Amount of WHYPE to deposit (in atomic units, e.g., `amount * 10**18`).
   * `receiver`: Address that will receive the hbHYPE tokens (usually the user's address).

### Requesting Withdrawal of Tokens (hbHYPE)

To withdraw underlying assets from the vault in exchange for hbHYPE tokens:

**Steps:**

1. **Request Redeem:**\
   Call the `requestRedeem(uint256 shares, address receiverAddr, address holderAddr)` function on the **hbHYPE vault contract.**
   * `shares`: Amount of hbHYPE tokens to withdraw (in atomic units, e.g., `amount * 10**18`).
   * `receiverAddr`: Address that will receive the underlying assets (usually the user's address).
   * `holderAddr`: Owner of the hbHYPE tokens (usually the user's address).
   * **Note:** It is recommended to simulate this transaction using `contract.requestRedeem.staticCall(...)` or the `previewRedeem(shares)` function before sending it to check for potential errors and estimate the received assets.

### Previewing Amounts (Optional but recommended)

The vault contract provides useful preview functions:

* **`previewDeposit(uint256 assets) returns (uint256 shares)`**:\
  Returns the number of vault shares that would be received for a given amount of assets.
* **`previewRedeem(uint256 shares) returns (uint256 assets)`**:\
  Returns the amount of assets that would be received for a given number of vault shares.

### Additional Information

* **Token Balance (BalanceOf):**
  * To get a user's **WHYPE token** balance, call `balanceOf(address account)` on the WHYPE contract.
  * To get a user's **hbHYPE token** (vault shares) balance, call `balanceOf(address account)` on the hbHYPE vault contract.
* **Withdrawal Processing Period:** Please note that withdrawals (after `requestRedeem`) can take up to 2 days to be processed. Once processed, the assets are automatically sent to the `receiverAddr` specified during the `requestRedeem` call. There is no separate manual claim step required by the user after the processing period.
* **Checking Withdrawal Status:**\
  To check the amount of assets that are claimable (or have been claimed) for a specific date for a given receiver, you can use the `getClaimableAmountByReceiver` function on the vault contract.

  * Function: `getClaimableAmountByReceiver(uint256 year, uint256 month, uint256 day, address receiverAddr) view returns (uint256)`
    * `year`: The year of the withdrawal request.
    * `month`: The month of the withdrawal request.
    * `day`: The day of the withdrawal request.
    * `receiverAddr`: The address of the receiver of the withdrawal.

  This function returns the amount of assets (in atomic units) that are claimable for that specific date and receiver. If a withdrawal has been processed for that date, it will reflect the amount. If no withdrawal was scheduled or processed for that date for the receiver, it will return 0.

\
\ <br>


# Hyperbeat Ultra UBTC

This document provides the necessary information to integrate the Hyperbeat Ultra UBTC (hbBTC) vault into your applications.

### General Vault Information

* **Vault Name:** Hyperbeat Ultra UBTC
* **Vault Token Symbol:** hbBTC
* **Chain:** hyperevm
* **Chain ID:** 999
* **Vault Contract Address:** `0xc061d38903b99aC12713B550C2CB44B221674F94`
* **Vault Token Decimals (hbBTC):** 8
* **Main Deposit Token:** UBTC
  * **Address:** `0x9FDBdA0A5e284c32744D2f17Ee5c74B284993463`
  * **Decimals:** 8

#### Useful Link

* **Contract on explorer:**  [View on hyperscan](https://www.hyperscan.com/address/0xc061d38903b99aC12713B550C2CB44B221674F94?tab=index)
* **UBTC Token on explorer:** [View on hyperscan](https://www.hyperscan.com/token/0x9FDBdA0A5e284c32744D2f17Ee5c74B284993463)
* **Vault Logo:**  [Brand kit](https://www.hyperbeat.org/brand)

{% file src="/files/hHVAdNSP709Bv8cpfQ6g" %}
Here is the complete ABI of the contract for reference - OPTIONAL
{% endfile %}

## Actions:

### Depositing Tokens

To deposit UBTC tokens into the hbBTC vault.

**Steps:**

1. **Check Allowance:**
   * Before depositing, check if the vault contract is authorized to spend the user's UBTC tokens.
   * Call the `allowance(address owner, address spender)` function on the UBTC token contract.
     * `owner`: User's address.
     * `spender`: hbBTC vault contract address.
2. **Approve Spending if necessary:**
   * If the allowance is less than the amount to deposit, the user must approve the vault contract.
   * Call the `approve(address spender, uint256 value)` function on the UBTC token contract.
     * `spender`: hbBTC vault contract address.
     * `value`: Amount of UBTC to approve (in atomic units, e.g., `amount * 10**8`).
3. **Perform Deposit:**
   * Once sufficient approval is granted, call the `deposit(uint256 assets, address receiver)` function on the hbBTC vault contract.
     * `assets`: Amount of UBTC to deposit (in atomic units, e.g., `amount * 10**8`).
     * `receiver`: Address that will receive the hbBTC tokens (usually the user's address).

### Requesting Withdrawal of Tokens (hbBTC)

To withdraw underlying assets from the vault in exchange for hbBTC tokens.

**Steps:**

1. **Request Redeem:**
   * Call the `requestRedeem(uint256 shares, address receiverAddr, address holderAddr)` function on the hbBTC vault contract.
     * `shares`: Amount of hbBTC tokens to withdraw (in atomic units, e.g., `amount * 10**8`).
     * `receiverAddr`: Address that will receive the underlying assets (usually the user's address).
     * `holderAddr`: Owner of the hbBTC tokens (usually the user's address).
   * **Note:** It is recommended to simulate this transaction using `contract.requestRedeem.staticCall(...)` or the `previewRedeem(shares)` function before sending it to check for potential errors and estimate the received assets.

#### Previewing Amounts (Optional but recommended)

The vault contract provides useful preview functions:

* `previewDeposit(uint256 assets) returns (uint256 shares)`: Returns the number of vault shares that would be received for a given amount of assets.
* `previewRedeem(uint256 shares) returns (uint256 assets)`: Returns the amount of assets that would be received for a given number of vault shares.

### Additional Information

* **Token Balance (BalanceOf):**
  * To get a user's UBTC token balance, call `balanceOf(address account)` on the UBTC contract.
  * To get a user's hbBTC token (vault shares) balance, call `balanceOf(address account)` on the hbBTC vault contract.
* **Withdrawal Processing Period:** Please note that withdrawals (after `requestRedeem`) can take up to 2 days to be processed. Once processed, the assets are automatically sent to the `receiverAddr` specified during the `requestRedeem` call. There is no separate manual claim step required by the user after the processing period.
* **Checking Withdrawal Status:**
  * To check the amount of assets that are claimable (or have been claimed) for a specific date for a given receiver, you can use the `getClaimableAmountByReceiver` function on the vault contract.
  * `getClaimableAmountByReceiver(uint256 year, uint256 month, uint256 day, address receiverAddr) view returns (uint256)`
    * `year`: The year of the withdrawal request.
    * `month`: The month of the withdrawal request (1-12).
    * `day`: The day of the withdrawal request.
    * `receiverAddr`: The address of the receiver of the withdrawal.
  * This function returns the amount of assets (in atomic units) that are claimable for that specific date and receiver. If a withdrawal has been processed for that date, it will reflect the amount. If no withdrawal was scheduled or processed for that date for the receiver, it will return 0.


# Hyperbeat USDT

This document provides the necessary information to integrate the Hyperbeat USDT (hbUSDT) vault, powered by Midas, into your applications.

### General Vault Information

* **Vault Name:** Hyperbeat USDT
* **Vault Token Symbol:** hbUSDT
* **Chain:** hyperevm
* **Chain ID:** 999
* **Vault Token (hbUSDT):** `0x5e105266db42f78FA814322Bce7f388B4C2e61eb`
* **Decimals:** 18
* **Insurance Contract (for Deposits):** `0xbE8A4f1a312b94A712F8E5367B02ae6E378E6F19`
* **Redemption Contract (for Withdrawals):** `0xC898a5cbDb81F260bd5306D9F9B9A893D0FdF042`

#### Token Information

* **Accepted Tokens:**
  * **USDT0:**
    * Address: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`
    * Decimals: 6
  * **USDe:**
    * Address: `0x5d3a1ff2b6bab83b63cd9ad0787074081a52ef34`
    * Decimals: 18
  * **USR:**
    * Address: `0x0aD339d66BF4AeD5ce31c64Bc37B3244b6394A77`
    * Decimals: 18

#### Useful Links

* **Vault Token on Explorer:**  [View on hyperscan](https://www.hyperscan.com/token/0x5e105266db42f78FA814322Bce7f388B4C2e61eb)
* **Insurance Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xbE8A4f1a312b94A712F8E5367B02ae6E378E6F19)
* **Redemption Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xC898a5cbDb81F260bd5306D9F9B9A893D0FdF042)
* **Vault Logo:**  [Brand kit](https://www.hyperbeat.org/brand)

## Actions

### Depositing Tokens

To deposit tokens (e.g., USDT0, USDe, USR) into the hbUSDT vault, you must interact with the **Insurance Contract**.

**Steps:**

1. **Approve Spending:**
   * The user must approve the **Insurance Contract** (`0xbE8A4f1a312b94A712F8E5367B02ae6E378E6F19`) to spend the chosen deposit token (e.g., USDT0).
   * Call the `approve(address spender, uint256 value)` function on the chosen deposit token's contract.
     * `spender`: The Insurance Contract address.
     * `value`: The amount to approve, in the token's native decimals (e.g., 6 for USDT0, 18 for USDe).
2. **Perform Deposit:**
   * Once approved, call the `depositInstant` function on the **Insurance Contract**.
   * `depositInstant(address tokenIn, uint256 amountToken, uint256 minReceiveAmount, bytes32 referrerId)`
     * `tokenIn`: The address of the token being deposited.
     * `amountToken`: **IMPORTANT:** The amount to deposit, expressed in **18 decimals**, regardless of the input token's actual decimals.
       * For tokens with 18 decimals (like USDe), use the amount directly.
       * For tokens with fewer decimals (like USDT0 with 6), you must scale the amount. For example: `amountIn18Decimals = amountIn6Decimals * 10**(18 - 6)`.
     * `minReceiveAmount`: The minimum amount of hbUSDT to receive. Can be set to `0` to accept any amount.
     * `referrerId`: A `bytes32` referrer ID. Can be set to `0x0000000000000000000000000000000000000000000000000000000000000000`.\
       or enter your referrerId from our collaboration.

### Withdrawing Tokens&#x20;

To withdraw underlying assets (USDT0) in exchange for hbUSDT, you must interact with the **Redemption Contract**. There are two methods: Instant and Classic.

**Step 1 (Required for both methods): Approve**

* Before withdrawing, the user must approve the **Redemption Contract** (`0xC898a5cbDb81F260bd5306D9F9B9A893D0FdF042`) to spend their hbUSDT.
* Call the `approve(address spender, uint256 value)` function on the **hbUSDT Vault Token** contract (`0x5e105266db42f78FA814322Bce7f388B4C2e61eb`).
  * `spender`: The Redemption Contract address.
  * `value`: The amount of hbUSDT to approve (in 18 decimals).

**Step 2 (Option A): Instant Redeem**

* For immediate withdrawal, subject to a 0.5% fee.
* Call `redeemInstant(address tokenOut, uint256 amountMTokenIn, uint256 minReceiveAmount)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of `hbUSDT` to withdraw, in 18 decimals.
  * `minReceiveAmount`: The minimum amount of the output token to receive. Can be set to `0`.

**Step 2 (Option B): Classic Redeem**

* For withdrawal processed within 48 hours with no fee.
* Call `redeemRequest(address tokenOut, uint256 amountMTokenIn)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of `hbUSDT` to withdraw, in 18 decimals.

### Additional Information

* **Token Balance (BalanceOf):**
  * To get a user's balance for any of the deposit tokens, call `balanceOf(address account)` on that token's contract.
  * To get a user's hbUSDT (vault shares) balance, call `balanceOf(address account)` on the hbUSDT vault contract.
* **Withdrawal Processing Period (Classic):** Classic redemption requests will be processed within 48 hours. The assets are automatically sent to the user's wallet upon processing.
* **Checking Withdrawal Status (Classic):**\
  Unlike the August vaults, status for classic redemption requests is checked via an off-chain API provided by Midas, not a smart contract function.\
  **API Endpoint:**\
  `GET https://api-prod.midas.app/api/data/requests/pending?address=<USER_ADDRESS>&networkId=999`\
  Replace `<USER_ADDRESS>` with the user's wallet address.\
  The API will return a JSON object containing a `redemptions` array. Each object in this array represents a pending withdrawal request and includes details like the amount, creation date, and status (`pending`, `ready`, or `expired`).


# Hyperbeat USDC

This document provides the necessary information to integrate the Hyperbeat USDC (hbUSDC) vault, powered by Midas, into your applications.

### General Vault Information

* **Vault Name:** Hyperbeat USDC
* **Vault Token Symbol:** hbUSDC
* **Chain:** hyperevm
* **Chain ID:** 999
* **Vault Token (hbUSDC):** `0x057ced81348D57Aad579A672d521d7b4396E8a61`
* **Decimals:** 18
* **Custom Feed:** `0xc82CAd78983436BddfcAf0F21316207D87b87462`
* **Data Feed:** `0xb013A5956f8b838B7E668DFbdf1efA978Ccc7a23`
* **Insurance Contract (for Deposits):** `0xd202CF41a607627cd1A31f650D13599b588eBd1c`
* **Redemption Contract (for Withdrawals):** `0xBb820D0c85C0B5D1B0dC8C6D3541fbb1AB4C7a60`

### Token Information

**Accepted Tokens:**

* **USDC:**
  * Address: `0xb88339CB7199b77E23DB6E890353E22632Ba630f`&#x20;
  * Decimals: 6

### Useful Links

* **Vault Token on Explorer:** [View on hyperscan](https://hyperevmscan.io/address/0x057ced81348d57aad579a672d521d7b4396e8a61)
* **Insurance Contract on Explorer:** [View on hyperscan](https://hyperevmscan.io/address/0xd202CF41a607627cd1A31f650D13599b588eBd1c)
* **Redemption Contract on Explorer:** [View on hyperscan](https://hyperevmscan.io/address/0xBb820D0c85C0B5D1B0dC8C6D3541fbb1AB4C7a60)
* **Vault Logo:** [Brand kit](https://www.hyperbeat.org/brand)

## Actions

### Depositing Tokens

To deposit tokens (e.g., USDC) into the hbUSDC vault, you must interact with the **Insurance Contract**.

**Steps:**

1. **Approve Spending**
   * Approve the Insurance Contract (`0xd202CF41a607627cd1A31f650D13599b588eBd1c`) to spend the deposit token (e.g., USDC).
   * Call `approve(address spender, uint256 value)` on the deposit token contract.
   * Parameters:
     * `spender`: Insurance Contract address.
     * `value`: Amount to approve, in the token’s native decimals (e.g., 6 for USDC).
2. **Perform Deposit**
   * Once approved, call `depositInstant` on the Insurance Contract.
   * `depositInstant(address tokenIn, uint256 amountToken, uint256 minReceiveAmount, bytes32 referrerId)`
   * **`tokenIn`:** Address of the token being deposited.
   * **`amountToken`:** Expressed in **18 decimals**, regardless of the input token’s decimals.
     * For USDC (6 decimals): `amountIn18Decimals = amountIn6Decimals * 10**12`.
   * **minReceiveAmount:** Minimum hbUSDC to receive. Can be 0.
   * **referrerId:** Bytes32 referrer ID. Use `0x0...0` if none.

***

## Withdrawing Tokens

Withdrawals are done through the **Redemption Contract** (`0xBb820D0c85C0B5D1B0dC8C6D3541fbb1AB4C7a60`). Two methods exist: **Instant** and **Classic**.

**Step 1 (Required for both methods): Approve**

* Approve the Redemption Contract to spend your hbUSDC.
* Call `approve(address spender, uint256 value)` on the hbUSDC Vault Token contract (`0x057ced81348D57Aad579A672d521d7b4396E8a61`).
* `spender`: Redemption Contract.
* `value`: Amount in 18 decimals.

**Step 2 (Option A): Instant Redeem**

* Immediate withdrawal, subject to a **0.5% fee**.
* **Call** `redeemInstant(address tokenOut, uint256 amountMTokenIn, uint256 minReceiveAmount)`
  * **tokenOut:** Address of the token to receive (e.g., USDC).
  * **amountMTokenIn:** Amount of hbUSDC to withdraw, in 18 decimals.
  * **minReceiveAmount:** Minimum amount to receive. Can be set to `0`.

**Step 2 (Option B): Classic Redeem**

* Withdrawals processed within **48 hours**, **no fee**.
* Call: `redeemRequest(address tokenOut, uint256 amountMTokenIn)`
  * **tokenOut:** Address of the token to receive (e.g., USDC).
  * **amountMTokenIn:** Amount of hbUSDC to withdraw, in 18 decimals.

## Additional Information

* **Token Balance (balanceOf):**
  * For deposit tokens, call `balanceOf(address)` on that token’s contract.
  * For hbUSDC balance, call `balanceOf(address)` on the hbUSDC vault token.
* **Withdrawal Processing (Classic):**
  * Classic withdrawals are processed in **\~48 hours**.
  * Assets are automatically sent upon processing.
* **Checking Withdrawal Status (Classic):**
  * Off-chain API via Midas (same format as hbUSDT).
  * Endpoint: `GET https://api-prod.midas.app/api/data/requests/pending?address=<USER_ADDRESS>&networkId=999`
  * Replace `<USER_ADDRESS>` with the wallet address.
  * The API will return a JSON object containing a `redemptions` array. Each object in this array represents a pending withdrawal request and includes details like the amount, creation date, and status (`pending`, `ready`, or `expired`).


# Hyperbeat XAUt

This document provides the necessary information to integrate the Hyperbeat XAUt (hbUSDT) vault, powered by Midas, into your applications.

### General Vault Information

* **Vault Name:** Hyperbeat XAUt
* **Vault Token Symbol:** hbXAUt
* **Chain:** hyperevm
* **Chain ID:** 999
* **Vault Token (hbUSDT):** `0x5e105266db42f78FA814322Bce7f388B4C2e61eb`
* **Decimals:** 18
* **Insurance Contract (for Deposits):** `0xbE8A4f1a312b94A712F8E5367B02ae6E378E6F19`
* **Redemption Contract (for Withdrawals):** `0xC898a5cbDb81F260bd5306D9F9B9A893D0FdF042`

#### Token Information

* **Accepted Tokens:**
  * **USDT0:**
    * Address: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`
    * Decimals: 6
  * **USDe:**
    * Address: `0x5d3a1ff2b6bab83b63cd9ad0787074081a52ef34`
    * Decimals: 18
  * **USR:**
    * Address: `0x0aD339d66BF4AeD5ce31c64Bc37B3244b6394A77`
    * Decimals: 18

#### Useful Links

* **Vault Token on Explorer:**  [View on hyperscan](https://www.hyperscan.com/token/0x5e105266db42f78FA814322Bce7f388B4C2e61eb)
* **Insurance Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xbE8A4f1a312b94A712F8E5367B02ae6E378E6F19)
* **Redemption Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xC898a5cbDb81F260bd5306D9F9B9A893D0FdF042)
* **Vault Logo:**  [Brand kit](https://www.hyperbeat.org/brand)

## Actions

### Depositing Tokens

To deposit tokens (e.g., USDT0, USDe, USR) into the hbUSDT vault, you must interact with the **Insurance Contract**.

**Steps:**

1. **Approve Spending:**
   * The user must approve the **Insurance Contract** (`0xbE8A4f1a312b94A712F8E5367B02ae6E378E6F19`) to spend the chosen deposit token (e.g., USDT0).
   * Call the `approve(address spender, uint256 value)` function on the chosen deposit token's contract.
     * `spender`: The Insurance Contract address.
     * `value`: The amount to approve, in the token's native decimals (e.g., 6 for USDT0, 18 for USDe).
2. **Perform Deposit:**
   * Once approved, call the `depositInstant` function on the **Insurance Contract**.
   * `depositInstant(address tokenIn, uint256 amountToken, uint256 minReceiveAmount, bytes32 referrerId)`
     * `tokenIn`: The address of the token being deposited.
     * `amountToken`: **IMPORTANT:** The amount to deposit, expressed in **18 decimals**, regardless of the input token's actual decimals.
       * For tokens with 18 decimals (like USDe), use the amount directly.
       * For tokens with fewer decimals (like USDT0 with 6), you must scale the amount. For example: `amountIn18Decimals = amountIn6Decimals * 10**(18 - 6)`.
     * `minReceiveAmount`: The minimum amount of hbUSDT to receive. Can be set to `0` to accept any amount.
     * `referrerId`: A `bytes32` referrer ID. Can be set to `0x0000000000000000000000000000000000000000000000000000000000000000`.\
       or enter your referrerId from our collaboration.

### Withdrawing Tokens&#x20;

To withdraw underlying assets (USDT0) in exchange for hbUSDT, you must interact with the **Redemption Contract**. There are two methods: Instant and Classic.

**Step 1 (Required for both methods): Approve**

* Before withdrawing, the user must approve the **Redemption Contract** (`0xC898a5cbDb81F260bd5306D9F9B9A893D0FdF042`) to spend their hbUSDT.
* Call the `approve(address spender, uint256 value)` function on the **hbUSDT Vault Token** contract (`0x5e105266db42f78FA814322Bce7f388B4C2e61eb`).
  * `spender`: The Redemption Contract address.
  * `value`: The amount of hbUSDT to approve (in 18 decimals).

**Step 2 (Option A): Instant Redeem**

* For immediate withdrawal, subject to a 0.5% fee.
* Call `redeemInstant(address tokenOut, uint256 amountMTokenIn, uint256 minReceiveAmount)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of `hbUSDT` to withdraw, in 18 decimals.
  * `minReceiveAmount`: The minimum amount of the output token to receive. Can be set to `0`.

**Step 2 (Option B): Classic Redeem**

* For withdrawal processed within 48 hours with no fee.
* Call `redeemRequest(address tokenOut, uint256 amountMTokenIn)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of `hbUSDT` to withdraw, in 18 decimals.

### Additional Information

* **Token Balance (BalanceOf):**
  * To get a user's balance for any of the deposit tokens, call `balanceOf(address account)` on that token's contract.
  * To get a user's hbUSDT (vault shares) balance, call `balanceOf(address account)` on the hbUSDT vault contract.
* **Withdrawal Processing Period (Classic):** Classic redemption requests will be processed within 48 hours. The assets are automatically sent to the user's wallet upon processing.
* **Checking Withdrawal Status (Classic):**\
  Unlike the August vaults, status for classic redemption requests is checked via an off-chain API provided by Midas, not a smart contract function.\
  **API Endpoint:**\
  `GET https://api-prod.midas.app/api/data/requests/pending?address=<USER_ADDRESS>&networkId=999`\
  Replace `<USER_ADDRESS>` with the user's wallet address.\
  The API will return a JSON object containing a `redemptions` array. Each object in this array represents a pending withdrawal request and includes details like the amount, creation date, and status (`pending`, `ready`, or `expired`).


# Hyperbeat lstHYPE

This document provides the necessary information to integrate the Hyperbeat USDT (hbUSDT) vault, powered by Midas, into your applications.

### General Vault Information

* **Vault Name:** Hyperbeat USDT
* **Vault Token Symbol:** hbUSDT
* **Chain:** hyperevm
* **Chain ID:** 999
* **Vault Token (hbUSDT):** `0x5e105266db42f78FA814322Bce7f388B4C2e61eb`
* **Decimals:** 18
* **Insurance Contract (for Deposits):** `0xbE8A4f1a312b94A712F8E5367B02ae6E378E6F19`
* **Redemption Contract (for Withdrawals):** `0xC898a5cbDb81F260bd5306D9F9B9A893D0FdF042`

#### Token Information

* **Accepted Tokens:**
  * **USDT0:**
    * Address: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`
    * Decimals: 6
  * **USDe:**
    * Address: `0x5d3a1ff2b6bab83b63cd9ad0787074081a52ef34`
    * Decimals: 18
  * **USR:**
    * Address: `0x0aD339d66BF4AeD5ce31c64Bc37B3244b6394A77`
    * Decimals: 18

#### Useful Links

* **Vault Token on Explorer:**  [View on hyperscan](https://www.hyperscan.com/token/0x5e105266db42f78FA814322Bce7f388B4C2e61eb)
* **Insurance Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xbE8A4f1a312b94A712F8E5367B02ae6E378E6F19)
* **Redemption Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xC898a5cbDb81F260bd5306D9F9B9A893D0FdF042)
* **Vault Logo:**  [Brand kit](https://www.hyperbeat.org/brand)

## Actions

### Depositing Tokens

To deposit tokens (e.g., USDT0, USDe, USR) into the hbUSDT vault, you must interact with the **Insurance Contract**.

**Steps:**

1. **Approve Spending:**
   * The user must approve the **Insurance Contract** (`0xbE8A4f1a312b94A712F8E5367B02ae6E378E6F19`) to spend the chosen deposit token (e.g., USDT0).
   * Call the `approve(address spender, uint256 value)` function on the chosen deposit token's contract.
     * `spender`: The Insurance Contract address.
     * `value`: The amount to approve, in the token's native decimals (e.g., 6 for USDT0, 18 for USDe).
2. **Perform Deposit:**
   * Once approved, call the `depositInstant` function on the **Insurance Contract**.
   * `depositInstant(address tokenIn, uint256 amountToken, uint256 minReceiveAmount, bytes32 referrerId)`
     * `tokenIn`: The address of the token being deposited.
     * `amountToken`: **IMPORTANT:** The amount to deposit, expressed in **18 decimals**, regardless of the input token's actual decimals.
       * For tokens with 18 decimals (like USDe), use the amount directly.
       * For tokens with fewer decimals (like USDT0 with 6), you must scale the amount. For example: `amountIn18Decimals = amountIn6Decimals * 10**(18 - 6)`.
     * `minReceiveAmount`: The minimum amount of hbUSDT to receive. Can be set to `0` to accept any amount.
     * `referrerId`: A `bytes32` referrer ID. Can be set to `0x0000000000000000000000000000000000000000000000000000000000000000`.\
       or enter your referrerId from our collaboration.

### Withdrawing Tokens&#x20;

To withdraw underlying assets (USDT0) in exchange for hbUSDT, you must interact with the **Redemption Contract**. There are two methods: Instant and Classic.

**Step 1 (Required for both methods): Approve**

* Before withdrawing, the user must approve the **Redemption Contract** (`0xC898a5cbDb81F260bd5306D9F9B9A893D0FdF042`) to spend their hbUSDT.
* Call the `approve(address spender, uint256 value)` function on the **hbUSDT Vault Token** contract (`0x5e105266db42f78FA814322Bce7f388B4C2e61eb`).
  * `spender`: The Redemption Contract address.
  * `value`: The amount of hbUSDT to approve (in 18 decimals).

**Step 2 (Option A): Instant Redeem**

* For immediate withdrawal, subject to a 0.5% fee.
* Call `redeemInstant(address tokenOut, uint256 amountMTokenIn, uint256 minReceiveAmount)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of `hbUSDT` to withdraw, in 18 decimals.
  * `minReceiveAmount`: The minimum amount of the output token to receive. Can be set to `0`.

**Step 2 (Option B): Classic Redeem**

* For withdrawal processed within 48 hours with no fee.
* Call `redeemRequest(address tokenOut, uint256 amountMTokenIn)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of `hbUSDT` to withdraw, in 18 decimals.

### Additional Information

* **Token Balance (BalanceOf):**
  * To get a user's balance for any of the deposit tokens, call `balanceOf(address account)` on that token's contract.
  * To get a user's hbUSDT (vault shares) balance, call `balanceOf(address account)` on the hbUSDT vault contract.
* **Withdrawal Processing Period (Classic):** Classic redemption requests will be processed within 48 hours. The assets are automatically sent to the user's wallet upon processing.
* **Checking Withdrawal Status (Classic):**\
  Unlike the August vaults, status for classic redemption requests is checked via an off-chain API provided by Midas, not a smart contract function.\
  **API Endpoint:**\
  `GET https://api-prod.midas.app/api/data/requests/pending?address=<USER_ADDRESS>&networkId=999`\
  Replace `<USER_ADDRESS>` with the user's wallet address.\
  The API will return a JSON object containing a `redemptions` array. Each object in this array represents a pending withdrawal request and includes details like the amount, creation date, and status (`pending`, `ready`, or `expired`).


# Ventuals (HIP-3) VLP Vault

This document provides the necessary information to integrate the Ventuals (HIP-3) wVLP vault, powered by Midas, into your applications.

### General Vault Information

* **Vault Name:** Ventuals (HIP-3) VLP Vault
* **Vault Token Symbol:** wVLP
* **Chain:** hyperevm
* **Chain ID:** 999
* **Vault Token (**&#x77;VL&#x50;**):** `0xD66d69c288d9a6FD735d7bE8b2e389970fC4fD42`
* **Decimals:** 18
* **Insurance Contract (for Deposits):** `0xc800f672EE8693BC0138E513038C84fe2D1B8a78`
* **Redemption Contract (for Withdrawals):** `0x462B95575cb2D56de9d1aAaAAb452279B058Aa06`

#### Token Information

* **Accepted Tokens:**
  * **USDT0:**
    * Address: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`
    * Decimals: 6

#### Useful Links

* **Vault Token on Explorer:**  [View on hyperscan](https://www.hyperscan.com/token/0x5e105266db42f78FA814322Bce7f388B4C2e61eb)
* **Insurance Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xbE8A4f1a312b94A712F8E5367B02ae6E378E6F19)
* **Redemption Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xC898a5cbDb81F260bd5306D9F9B9A893D0FdF042)
* **Vault Logo:**  [Brand kit](https://www.hyperbeat.org/brand)

## Actions

### Depositing Tokens

To deposit tokens (e.g., USDT0) into the wVLP vault, you must interact with the **Insurance Contract**.

**Steps:**

1. **Approve Spending:**
   * The user must approve the **Insurance Contract** (`0xc800f672EE8693BC0138E513038C84fe2D1B8a78`) to spend the chosen deposit token (e.g., USDT0).
   * Call the `approve(address spender, uint256 value)` function on the chosen deposit token's contract.
     * `spender`: The Insurance Contract address.
     * `value`: The amount to approve, in the token's native decimals (e.g., 6 for USDT0).
2. **Perform Deposit:**
   * Once approved, call the `depositInstant` function on the **Insurance Contract**.
   * `depositInstant(address tokenIn, uint256 amountToken, uint256 minReceiveAmount, bytes32 referrerId)`
     * `tokenIn`: The address of the token being deposited.
     * `amountToken`: **IMPORTANT:** The amount to deposit, expressed in **18 decimals**, regardless of the input token's actual decimals.
       * For tokens with 18 decimals (like USDe), use the amount directly.
       * For tokens with fewer decimals (like USDT0 with 6), you must scale the amount. For example: `amountIn18Decimals = amountIn6Decimals * 10**(18 - 6)`.
     * `minReceiveAmount`: The minimum amount of wVLP to receive. Can be set to `0` to accept any amount.
     * `referrerId`: A `bytes32` referrer ID. Can be set to `0x0000000000000000000000000000000000000000000000000000000000000000`.\
       or enter your referrerId from our collaboration.

### Withdrawing Tokens&#x20;

To withdraw underlying assets (USDT0) in exchange for wVLP, you must interact with the **Redemption Contract**. There are two methods: Instant and Classic.

**Step 1 (Required for both methods): Approve**

* Before withdrawing, the user must approve the **Redemption Contract** (`0x462B95575cb2D56de9d1aAaAAb452279B058Aa06`) to spend their wVLP.
* Call the `approve(address spender, uint256 value)` function on the wVLP **Vault Token** contract (`0xD66d69c288d9a6FD735d7bE8b2e389970fC4fD42`).
  * `spender`: The Redemption Contract address.
  * `value`: The amount of wVLP to approve (in 18 decimals).

**Step 2 (Option A): Instant Redeem**

* For immediate withdrawal, subject to a 0.5% fee.
* Call `redeemInstant(address tokenOut, uint256 amountMTokenIn, uint256 minReceiveAmount)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of wVLP to withdraw, in 18 decimals.
  * `minReceiveAmount`: The minimum amount of the output token to receive. Can be set to `0`.

**Step 2 (Option B): Classic Redeem**

* For withdrawal processed within 48 hours with no fee.
* Call `redeemRequest(address tokenOut, uint256 amountMTokenIn)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of wVLP to withdraw, in 18 decimals.

### Additional Information

* **Token Balance (BalanceOf):**
  * To get a user's balance for any of the deposit tokens, call `balanceOf(address account)` on that token's contract.
  * To get a user's hbUSDT (vault shares) balance, call `balanceOf(address account)` on the hbUSDT vault contract.
* **Withdrawal Processing Period (Classic):** Classic redemption requests will be processed within 48 hours. The assets are automatically sent to the user's wallet upon processing.
* **Checking Withdrawal Status (Classic):**\
  Unlike the August vaults, status for classic redemption requests is checked via an off-chain API provided by Midas, not a smart contract function.\
  **API Endpoint:**\
  `GET https://api-prod.midas.app/api/data/requests/pending?address=<USER_ADDRESS>&networkId=999`\
  Replace `<USER_ADDRESS>` with the user's wallet address.\
  The API will return a JSON object containing a `redemptions` array. Each object in this array represents a pending withdrawal request and includes details like the amount, creation date, and status (`pending`, `ready`, or `expired`).


# dnHYPE

This document provides the necessary information to integrate the dnHYPE vault, powered by Midas, into your applications.

### General Vault Information

* **Vault Name:** dnHYPE
* **Vault Token Symbol:** dnHYPE
* **Chain:** hyperevm
* **Chain ID:** 999
* **Vault Token (**&#x64;nHYP&#x45;**):** `0x949a7250Bb55Eb79BC6bCC97fCd1C473DB3e6F29`
* **Decimals:** 18
* **Insurance Contract (for Deposits):** `0xa4a6b89354E278666fb908CcdB16276AE151ff00`
* **Redemption Contract (for Withdrawals):** `0xBe61c1A27689c11b63378e84C9bB70A2cd616Fff`

#### Token Information

* **Accepted Tokens:**
  * **USDT0:**
    * Address: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`
    * Decimals: 6

#### Useful Links

* **Vault Token on Explorer:**  [View on hyperscan](https://www.hyperscan.com/token/0x949a7250Bb55Eb79BC6bCC97fCd1C473DB3e6F29)
* **Insurance Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xa4a6b89354E278666fb908CcdB16276AE151ff00)
* **Redemption Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xBe61c1A27689c11b63378e84C9bB70A2cd616Fff)
* **Vault Logo:**  [Brand kit](https://www.hyperbeat.org/brand)

## Actions

### Depositing Tokens

To deposit tokens (e.g., USDT0) into the dnHYPE vault, you must interact with the **Insurance Contract**.

**Steps:**

1. **Approve Spending:**
   * The user must approve the **Insurance Contract** (`0xa4a6b89354E278666fb908CcdB16276AE151ff00`) to spend the chosen deposit token (e.g., USDT0).
   * Call the `approve(address spender, uint256 value)` function on the chosen deposit token's contract.
     * `spender`: The Insurance Contract address.
     * `value`: The amount to approve, in the token's native decimals (e.g., 6 for USDT0).
2. **Perform Deposit:**
   * Once approved, call the `depositInstant` function on the **Insurance Contract**.
   * `depositInstant(address tokenIn, uint256 amountToken, uint256 minReceiveAmount, bytes32 referrerId)`
     * `tokenIn`: The address of the token being deposited.
     * `amountToken`: **IMPORTANT:** The amount to deposit, expressed in **18 decimals**, regardless of the input token's actual decimals.
       * For tokens with 18 decimals (like USDe), use the amount directly.
       * For tokens with fewer decimals (like USDT0 with 6), you must scale the amount. For example: `amountIn18Decimals = amountIn6Decimals * 10**(18 - 6)`.
     * `minReceiveAmount`: The minimum amount of dnHYPE to receive. Can be set to `0` to accept any amount.
     * `referrerId`: A `bytes32` referrer ID. Can be set to `0x0000000000000000000000000000000000000000000000000000000000000000`.\
       or enter your referrerId from our collaboration.

### Withdrawing Tokens&#x20;

To withdraw underlying assets (USDT0) in exchange for dnHYPE, you must interact with the **Redemption Contract**. There are two methods: Instant and Classic.

**Step 1 (Required for both methods): Approve**

* Before withdrawing, the user must approve the **Redemption Contract** (`0xBe61c1A27689c11b63378e84C9bB70A2cd616Fff`) to spend their dnHYPE.
* Call the `approve(address spender, uint256 value)` function on the dnHYPE **Vault Token** contract (`0x949a7250Bb55Eb79BC6bCC97fCd1C473DB3e6F29`).
  * `spender`: The Redemption Contract address.
  * `value`: The amount of dnHYPE to approve (in 18 decimals).

**Step 2 (Option A): Instant Redeem**

* For immediate withdrawal, subject to a 0.5% fee.
* Call `redeemInstant(address tokenOut, uint256 amountMTokenIn, uint256 minReceiveAmount)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of dnHYPE to withdraw, in 18 decimals.
  * `minReceiveAmount`: The minimum amount of the output token to receive. Can be set to `0`.

**Step 2 (Option B): Classic Redeem**

* For withdrawal processed within 48 hours with no fee.
* Call `redeemRequest(address tokenOut, uint256 amountMTokenIn)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of dnHYPE to withdraw, in 18 decimals.

### Additional Information

* **Token Balance (BalanceOf):**
  * To get a user's balance for any of the deposit tokens, call `balanceOf(address account)` on that token's contract.
  * To get a user's hbUSDT (vault shares) balance, call `balanceOf(address account)` on the hbUSDT vault contract.
* **Withdrawal Processing Period (Classic):** Classic redemption requests will be processed within 48 hours. The assets are automatically sent to the user's wallet upon processing.
* **Checking Withdrawal Status (Classic):**\
  Unlike the August vaults, status for classic redemption requests is checked via an off-chain API provided by Midas, not a smart contract function.\
  **API Endpoint:**\
  `GET https://api-prod.midas.app/api/data/requests/pending?address=<USER_ADDRESS>&networkId=999`\
  Replace `<USER_ADDRESS>` with the user's wallet address.\
  The API will return a JSON object containing a `redemptions` array. Each object in this array represents a pending withdrawal request and includes details like the amount, creation date, and status (`pending`, `ready`, or `expired`).


# dnPUMP

This document provides the necessary information to integrate the dnPUMP vault, powered by Midas, into your applications.

### General Vault Information

* **Vault Name:** dnPUMP
* **Vault Token Symbol:** dnPUMP
* **Chain:** hyperevm
* **Chain ID:** 999
* **Vault Token (**&#x64;nPUM&#x50;**):** `0x8858A307a85982c2B3CB2AcE1720237f2f09c39B`
* **Decimals:** 18
* **Insurance Contract (for Deposits):** `0xaF8FfEDF0e57eE9f6518340b9eb913fFa7dBc66b`
* **Redemption Contract (for Withdrawals):** `0x9c915C94066fF921264071aCB7D59DB6e0cBf0D7`

#### Token Information

* **Accepted Tokens:**
  * **USDT0:**
    * Address: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`
    * Decimals: 6

#### Useful Links

* **Vault Token on Explorer:**  [View on hyperscan](https://www.hyperscan.com/token/0x8858A307a85982c2B3CB2AcE1720237f2f09c39B)
* **Insurance Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0xaF8FfEDF0e57eE9f6518340b9eb913fFa7dBc66b)
* **Redemption Contract on Explorer:** [View on hyperscan](https://www.hyperscan.com/address/0x9c915C94066fF921264071aCB7D59DB6e0cBf0D7)
* **Vault Logo:**  [Brand kit](https://www.hyperbeat.org/brand)

## Actions

### Depositing Tokens

To deposit tokens (e.g., USDT0) into the dnPUMP vault, you must interact with the **Insurance Contract**.

**Steps:**

1. **Approve Spending:**
   * The user must approve the **Insurance Contract** (`0xaF8FfEDF0e57eE9f6518340b9eb913fFa7dBc66b`) to spend the chosen deposit token (e.g., USDT0).
   * Call the `approve(address spender, uint256 value)` function on the chosen deposit token's contract.
     * `spender`: The Insurance Contract address.
     * `value`: The amount to approve, in the token's native decimals (e.g., 6 for USDT0).
2. **Perform Deposit:**
   * Once approved, call the `depositInstant` function on the **Insurance Contract**.
   * `depositInstant(address tokenIn, uint256 amountToken, uint256 minReceiveAmount, bytes32 referrerId)`
     * `tokenIn`: The address of the token being deposited.
     * `amountToken`: **IMPORTANT:** The amount to deposit, expressed in **18 decimals**, regardless of the input token's actual decimals.
       * For tokens with 18 decimals (like USDe), use the amount directly.
       * For tokens with fewer decimals (like USDT0 with 6), you must scale the amount. For example: `amountIn18Decimals = amountIn6Decimals * 10**(18 - 6)`.
     * `minReceiveAmount`: The minimum amount of dnPUMP to receive. Can be set to `0` to accept any amount.
     * `referrerId`: A `bytes32` referrer ID. Can be set to `0x0000000000000000000000000000000000000000000000000000000000000000`.\
       or enter your referrerId from our collaboration.

### Withdrawing Tokens&#x20;

To withdraw underlying assets (USDT0) in exchange for dnPUMP, you must interact with the **Redemption Contract**. There are two methods: Instant and Classic.

**Step 1 (Required for both methods): Approve**

* Before withdrawing, the user must approve the **Redemption Contract** (`0x9c915C94066fF921264071aCB7D59DB6e0cBf0D7`) to spend their dnPUMP.
* Call the `approve(address spender, uint256 value)` function on the dnPUMP **Vault Token** contract (`0x8858A307a85982c2B3CB2AcE1720237f2f09c39B`).
  * `spender`: The Redemption Contract address.
  * `value`: The amount of dnPUMP to approve (in 18 decimals).

**Step 2 (Option A): Instant Redeem**

* For immediate withdrawal, subject to a 0.5% fee.
* Call `redeemInstant(address tokenOut, uint256 amountMTokenIn, uint256 minReceiveAmount)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of dnPUMP to withdraw, in 18 decimals.
  * `minReceiveAmount`: The minimum amount of the output token to receive. Can be set to `0`.

**Step 2 (Option B): Classic Redeem**

* For withdrawal processed within 48 hours with no fee.
* Call `redeemRequest(address tokenOut, uint256 amountMTokenIn)` on the **Redemption Contract**.
  * `tokenOut`: Address of the token to receive (USDT0: `0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb`).
  * `amountMTokenIn`: Amount of dnPUMP to withdraw, in 18 decimals.

### Additional Information

* **Token Balance (BalanceOf):**
  * To get a user's balance for any of the deposit tokens, call `balanceOf(address account)` on that token's contract.
  * To get a user's hbUSDT (vault shares) balance, call `balanceOf(address account)` on the hbUSDT vault contract.
* **Withdrawal Processing Period (Classic):** Classic redemption requests will be processed within 48 hours. The assets are automatically sent to the user's wallet upon processing.
* **Checking Withdrawal Status (Classic):**\
  Unlike the August vaults, status for classic redemption requests is checked via an off-chain API provided by Midas, not a smart contract function.\
  **API Endpoint:**\
  `GET https://api-prod.midas.app/api/data/requests/pending?address=<USER_ADDRESS>&networkId=999`\
  Replace `<USER_ADDRESS>` with the user's wallet address.\
  The API will return a JSON object containing a `redemptions` array. Each object in this array represents a pending withdrawal request and includes details like the amount, creation date, and status (`pending`, `ready`, or `expired`).


# Staking

Builders can integrate with **Hyperbeat staking products** to route user staking flows and earn fees via Builder Codes. There are two staking options supported:

## **1. Vanilla Staking (Direct Delegation)**

Vanilla staking allows users to delegate HYPE directly to the **Hyperbeat validator** on Hyperliquid. It’s the simplest and most direct way to participate in securing the network.

{% hint style="success" %}
Learn more [here](/hyperbeat-builder-codes/staking/vanilla-staking)
{% endhint %}

## **1.** Liquid Staking (beHYPE)

Liquid staking allows users to stake HYPE and mint **beHYPE**, a tokenized staking position that can be used elsewhere in DeFi. The underlying HYPE is staked directly to the active set validators.

{% hint style="success" %}
Learn more [here](/hyperbeat-builder-codes/staking/liquid-staking)
{% endhint %}


# Liquid staking

A comprehensive guide for developers looking to integrate beHYPE staking and unstaking functionality into their applications.

### Overview

beHYPE is a liquid staking token that represents staked HYPE tokens. Users can stake HYPE to receive beHYPE tokens, which continue to earn staking rewards while remaining liquid and transferable.

### Contract Addresses

```solidity
BeHYPE: 0xd8FC8F0b03eBA61F64D08B0bef69d80916E5DdA9
WithdrawManager: 0x9d0B0877b9f2204CF414Ca7862E4f03506822538
StakingCore: 0xCeaD893b162D38e714D82d06a7fe0b0dc3c38E0b
RoleRegistry: 0x90102473a816A01A9fB0809F2289438B2e294F76
BeHYPETimelock: 0xA24aF73EaDD17997EeEdbEd36672e996544D2DE4
L1Read: 0xb7467E0524Afba7006957701d1F06A59000d15A2
```

### Minting (Staking)

Send a transaction to the StakingCore contract with the function signature `stake(string communityCode)`. The `communityCode` is the validator name you want those tokens to be designated to. The amount minted will be the amount of HYPE included in the value of the transaction. If you do not have a specific validator to stake to, you can pass an empty string ("") for automatic distribution across validators.

This will mint beHYPE tokens to the caller's address.

```solidity
function Stake() public {
    address user = address(0x1234);
    vm.deal(user, 10 ether);

    vm.startPrank(user); // using the private key of the user
    
    // Stake 10 HYPE to a specific validator
    stakingCore.stake{value: 10 ether}("validator_name");
    
    // Stake another 10 HYPE with automatic validator distribution
    stakingCore.stake{value: 10 ether}("");
}
```

### Community Codes

All active set validators (Excluding foundation nodes) are eligible to receive stake from beHYPE. Anyone can select their preferred validator to receive their stake. If you don't specify a validator (empty string), the stake will be automatically distributed across active validators.

### Burning (Unstaking)

Burning is a multistep process that depends on the amount of free (unstaked) tokens available in the protocol. There will typically always be a small float of the total supply unstaked to instantly fulfill burns, but for large amounts or high outflow volume, it becomes a two-step process.

**Step 1:** Approve the WithdrawManager contract with the amount of beHYPE tokens you want to unstake.

**Step 2:** Call `withdraw(uint256 beHypeAmount, bool instant, uint256 minAmountOut)` to burn `beHypeAmount` of tokens. The redeemed HYPE will be processed based on the `instant` parameter:

* `instant = false`: Normal withdrawal (7-day processing, no fee)
* `instant = true`: Instant withdrawal (0.5% fee applied)

The `minAmountOut` parameter provides slippage protection. This function returns a `withdrawalId` which will be used to claim the withdrawal once processed.

**Step 3:** For normal withdrawals, wait for processing time, then call `claimWithdrawal(uint256 withdrawalId)` to receive your HYPE tokens.

```solidity
function Burn() public {
    uint256 decimals = 10 ** 18;
    address user = address(0x1234); // set up with a balance of 10 beHYPE
    vm.startPrank(user);
    
    // 1. Approve 10 beHYPE (18 decimals)
    behype.approve(withdrawManager, 10 * decimals); 

    // 2. Normal withdrawal (7-day processing, no fee)
    uint256 minAmountOut = 9.9 ether; // 1% slippage tolerance
    uint256 withdrawalId = withdrawManager.withdraw(10 * decimals, false, minAmountOut);
    
    // 3. Wait for processing time (7 days)
    // ...
    
    // 4. Claim the withdrawal
    withdrawManager.claimWithdrawal(withdrawalId);
    require(user.balance >= 9.9 ether, "user should have received HYPE");
}
```

### Instant Redemption

For immediate access to HYPE, you can use instant redemption with a 0.5% fee:

```solidity
function InstantBurn() public {
    uint256 decimals = 10 ** 18;
    address user = address(0x1234); // set up with a balance of 10 beHYPE
    vm.startPrank(user);
    
    // 1. Approve 10 beHYPE
    behype.approve(withdrawManager, 10 * decimals);
    
    // 2. Instant withdrawal (immediate, 0.5% fee)
    uint256 minAmountOut = 9.4 ether; // accounting for 0.5% fee + slippage
    withdrawManager.withdraw(10 * decimals, true, minAmountOut);
    
    // Tokens are received immediately
    require(user.balance >= 9.4 ether, "user should have received HYPE instantly");
}
```

### API Endpoints

#### Base URL

```
https://api.hyperbeat.org/api/v1/behype/
```

#### Available Endpoints

1. **Get beHYPE Balance**
   * `GET /balance/{user_address}`
   * Returns user's beHYPE balance
2. **Get Exchange Ratio Updates**
   * `GET /exchange-ratio-update`
   * Returns latest exchange ratio between beHYPE and HYPE
3. **Get TVL Data**
   * `GET /tvl`
   * Returns total value locked, exchange ratio, and price information

### Function Signatures

#### StakingCore Contract

```solidity
// Stake HYPE to receive beHYPE
function stake(string calldata communityCode) external payable;
```

#### WithdrawManager Contract

```solidity
// Withdraw beHYPE for HYPE (returns withdrawal ID)
function withdraw(uint256 beHypeAmount, bool instant, uint256 minAmountOut) 
    external returns (uint256 withdrawalId);

// Claim completed withdrawal
function claimWithdrawal(uint256 withdrawalId) external;
```

#### BeHYPE Token Contract (ERC20)

```solidity
// Standard ERC20 functions
function balanceOf(address account) external view returns (uint256);
function approve(address spender, uint256 amount) external returns (bool);
function allowance(address owner, address spender) external view returns (uint256);
```

### Support

For additional support or questions about beHYPE integration, ask us on [discord](https://discord.gg/hyperbeat) or contact the development team.


# Vanilla staking

Hyperbeat offers institutional clients a robust HYPE staking product via its validator on Hyperliquid, powered by the P2P.org Staking API. Built for funds, custodians, and fintechs, this solution delivers secure, scalable staking infrastructure without the constraints of frontend integrations.

{% hint style="success" %}
[Get started here ](/hyperbeat-staking/staking-api/getting-started)
{% endhint %}


# Hyperfolio API

Hyperfolio API is an onchain HyperEVM portfolio tracking API designed to support builder use cases. Builders can also fetch real-time Hyperbeat data, like vault yield metrics and more to power frontends.&#x20;

{% hint style="success" %}
Learn more [here](broken://pages/cnoox41xWGqEa5s8abcd)
{% endhint %}

{% hint style="warning" %}
The above endpoint is only available for Midas Vaults. (i.e. hbUSDT, lstHYPE, XAUt, beHYPE pre-deposit)
{% endhint %}


# Hearts

Hearts is Hyperbeat’s points program, assigned to users that help to scale Hyperliquid and Hyperbeat. Points formula is not public.

## Hearts Distribution

* **Total Supply:** 51M Hearts
* **Distribution Period:** Weekly

## Ranking System

Hearts holders are ranked into tiers based on their total points:

* **Bronze:** 0% – 24.99%
* **Silver:** 25% – 49.99%
* **Gold:** 50% – 74.99%
* **Platinum:** 75% – 94.99%
* **Diamond:** 95% – 98.99%
* **Challenger:** 99% – 100%

## How to Earn Hearts

* Engage with Hyperbeat products.
* Refer a friend
* Sybil activity (fraudulent participation) will be detected and penalized (e.g. point removal, disqualification).

{% hint style="success" %}
[Generate a referral code to earn more hearts](/hearts/referral-program)
{% endhint %}

## Tracking Your Hearts

Users can check their Hearts balance by connecting their wallet to the [Hyperbeat App](https://app.hyperbeat.org/staking/sthype) and clicking the Hearts button in the top right-hand corner.


# Referral Program

Earn extra Hearts by referring friends to Hyperbeat.

## How It Works

Each Hyperbeat user gets a **unique referral code** after connecting their wallet. You can use this code to invite others and earn hearts when they participate.

* **You earn 10% of the Hearts your referrals generate**, across all campaigns.
* Example: If your friend earns 1 Heart/second in a vault, **you earn 0.1 Hearts/second**, passively.

## Getting Your Referral Code

1. Connect your wallet on <https://app.hyperbeat.org/vaults#invite>
2. Generate your referral code:
   * Connect your wallet and sign the tx to generate your code (e.g. `https://app.hyperbeat.xyz/?ref=abcd123`)
   * Copy your code to share it anywhere

## Using a Referral Code

If you were referred to Hyperbeat:

* Open Hyperbeat using your friend’s referral link *or e*nter their referral code manually on the platform within **48 hours** of first connecting your wallet. A timer will show how much time you have left to enter a code.

## Rules & Limitations

* You **cannot refer yourself** or create circular referrals (e.g., A refers B, B refers A).
* Referral codes are **unique to each wallet** and **non-transferable**.
* You have **48 hours** after your first wallet connection to enter a referral code.
* Hearts are awarded **automatically** and **consistently across all campaigns**.
* Sybil or fraudulent behaviour will result in **penalties or disqualification**.


# Proof of solvency

Hyperbeat is committed to transparency and the security of user funds. Users can verify in real time that all vault assets are fully backed through cryptographic proofs. The independent solvency dashboard is powered by [Accountable](https://x.com/AccountableData). Accountable’s system combines Merkle Sum Trees, Secure Enclaves (Nitro, SGX, SEV, TDX), and Zero-Knowledge Proofs to verify asset and liability data directly from on-chain and off-chain sources, ensuring transparent and verifiable financial reporting.

{% hint style="success" %}
[Proof of solvency dashboard](https://accountable.hyperbeat.org/)
{% endhint %}


# Audits

Hyperbeat utilizes a range of vault infrastructure partners, each of which has undergone audits.

## Hyperbeat  Audits

{% hint style="success" %}
[Audit reports](https://github.com/0xhyperbeat/Audits)
{% endhint %}

### August Digital

{% hint style="success" %}
[Audit reports](https://docs.augustdigital.io/smart-contracts/risks-and-audits)
{% endhint %}

### Midas

{% hint style="success" %}
[Audit reports](https://docs.midas.app/resources/audits)
{% endhint %}

### Morpho

{% hint style="success" %}
[Audit reports](https://docs.morpho.org/get-started/resources/audits/)
{% endhint %}


# Addresses

## beHYPE

<table><thead><tr><th>Contract</th><th data-type="content-ref">Address</th></tr></thead><tbody><tr><td>beHYPE</td><td><a href="https://hyperevmscan.io/address/0xd8FC8F0b03eBA61F64D08B0bef69d80916E5DdA9">https://hyperevmscan.io/address/0xd8FC8F0b03eBA61F64D08B0bef69d80916E5DdA9</a></td></tr><tr><td>StakingCore</td><td><a href="https://hyperevmscan.io/address/0xCeaD893b162D38e714D82d06a7fe0b0dc3c38E0b">https://hyperevmscan.io/address/0xCeaD893b162D38e714D82d06a7fe0b0dc3c38E0b</a></td></tr><tr><td>WithdrawManager</td><td><a href="https://hyperevmscan.io/address/0x9d0B0877b9f2204CF414Ca7862E4f03506822538">https://hyperevmscan.io/address/0x9d0B0877b9f2204CF414Ca7862E4f03506822538</a></td></tr><tr><td>RoleRegistry</td><td><a href="https://hyperevmscan.io/address/0x90102473a816A01A9fB0809F2289438B2e294F76">https://hyperevmscan.io/address/0x90102473a816A01A9fB0809F2289438B2e294F76</a></td></tr><tr><td>beHYPETimelock</td><td><a href="https://hyperevmscan.io/address/0xA24aF73EaDD17997EeEdbEd36672e996544D2DE4">https://hyperevmscan.io/address/0xA24aF73EaDD17997EeEdbEd36672e996544D2DE4</a></td></tr></tbody></table>

## HyperEVM Vaults

<table><thead><tr><th>Hyperbeat Vault</th><th data-type="content-ref">Address</th></tr></thead><tbody><tr><td>HYPE Vault</td><td><a href="https://hyperevmscan.io/token/0x96c6cbb6251ee1c257b2162ca0f39aa5fa44b1fb">https://hyperevmscan.io/token/0x96c6cbb6251ee1c257b2162ca0f39aa5fa44b1fb</a></td></tr><tr><td>UBTC Vault</td><td><a href="https://hyperevmscan.io/token/0xc061d38903b99ac12713b550c2cb44b221674f94">https://hyperevmscan.io/token/0xc061d38903b99ac12713b550c2cb44b221674f94</a></td></tr><tr><td>USDT Vault</td><td><a href="https://hyperevmscan.io/address/0x5e105266db42f78fa814322bce7f388b4c2e61eb">https://hyperevmscan.io/address/0x5e105266db42f78fa814322bce7f388b4c2e61eb</a></td></tr><tr><td>XAUt Vault</td><td><a href="https://hyperevmscan.io/token/0x6EB6724D8D3D4FF9E24d872E8c38403169dC05f8">https://hyperevmscan.io/token/0x6EB6724D8D3D4FF9E24d872E8c38403169dC05f8</a></td></tr><tr><td>LST Vault</td><td><a href="https://hyperevmscan.io/token/0x81e064d0eB539de7c3170EDF38C1A42CBd752A76">https://hyperevmscan.io/token/0x81e064d0eB539de7c3170EDF38C1A42CBd752A76</a></td></tr><tr><td>liquidHYPE Vault</td><td><a href="https://hyperevmscan.io/token/0x441794d6a8f9a3739f5d4e98a728937b33489d29">https://hyperevmscan.io/token/0x441794d6a8f9a3739f5d4e98a728937b33489d29</a></td></tr><tr><td>Ventuals (HIP3) VLP</td><td><a href="https://hyperevmscan.io/token/0xD66d69c288d9a6FD735d7bE8b2e389970fC4fD42">https://hyperevmscan.io/token/0xD66d69c288d9a6FD735d7bE8b2e389970fC4fD42</a></td></tr><tr><td>dnHYPE </td><td><a href="https://hyperevmscan.io/address/0x949a7250Bb55Eb79BC6bCC97fCd1C473DB3e6F29">https://hyperevmscan.io/address/0x949a7250Bb55Eb79BC6bCC97fCd1C473DB3e6F29</a></td></tr><tr><td>dnPUMP</td><td><a href="https://hyperevmscan.io/address/0x8858A307a85982c2B3CB2AcE1720237f2f09c39B">https://hyperevmscan.io/address/0x8858A307a85982c2B3CB2AcE1720237f2f09c39B</a></td></tr><tr><td>USDC Vault</td><td><a href="https://hyperevmscan.io/address/0x057ced81348D57Aad579A672d521d7b4396E8a61">https://hyperevmscan.io/address/0x057ced81348D57Aad579A672d521d7b4396E8a61</a></td></tr><tr><td>wNLP</td><td><a href="https://hyperevmscan.io/address/0x4Cc221cf1444333510a634CE0D8209D2D11B9bbA">https://hyperevmscan.io/address/0x4Cc221cf1444333510a634CE0D8209D2D11B9bbA</a></td></tr></tbody></table>

## Morpho

<table><thead><tr><th>Contract</th><th data-type="content-ref">Address</th></tr></thead><tbody><tr><td>Morpho</td><td><a href="https://purrsec.com/address/0x68e37de8d93d3496ae143f2e900490f6280c57cd">https://purrsec.com/address/0x68e37de8d93d3496ae143f2e900490f6280c57cd</a></td></tr><tr><td>Adaptive Curve Irm</td><td><a href="https://purrsec.com/address/0xd4a426f010986dcad727e8dd6eed44ca4a9b7483">https://purrsec.com/address/0xd4a426f010986dcad727e8dd6eed44ca4a9b7483</a></td></tr><tr><td>Morpho Chainlink Oracle V2 Factory</td><td><a href="https://purrsec.com/address/0xeb476f124fad625178759d13557a72394a6f9af5">https://purrsec.com/address/0xeb476f124fad625178759d13557a72394a6f9af5</a></td></tr><tr><td>MetaMorpho Factory v1.1</td><td><a href="https://etherscan.io/address/0x1897A8997241C1cD4bD0698647e4EB7213535c24">https://etherscan.io/address/0x1897A8997241C1cD4bD0698647e4EB7213535c24</a></td></tr><tr><td>Public Allocator</td><td><a href="https://etherscan.io/address/0xfd32fA2ca22c76dD6E550706Ad913FC6CE91c75D">https://etherscan.io/address/0xfd32fA2ca22c76dD6E550706Ad913FC6CE91c75D</a></td></tr><tr><td>PreLiquidation Factory</td><td><a href="https://etherscan.io/address/0x6FF33615e792E35ed1026ea7cACCf42D9BF83476">https://etherscan.io/address/0x6FF33615e792E35ed1026ea7cACCf42D9BF83476</a></td></tr></tbody></table>


# Oracles

<table><thead><tr><th>Hyperbeat Vault</th><th data-type="content-ref">Fundamental Oracle</th></tr></thead><tbody><tr><td>hbHYPE</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/hbhype_fundamental/">https://app.redstone.finance/app/feeds/hyperevm/hbhype_fundamental/</a></td></tr><tr><td>hbBTC</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/hbbtc_fundamental/">https://app.redstone.finance/app/feeds/hyperevm/hbbtc_fundamental/</a></td></tr><tr><td>hbUSDT</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/hbusdt_fundamental/">https://app.redstone.finance/app/feeds/hyperevm/hbusdt_fundamental/</a></td></tr><tr><td>wVLP</td><td><a href="https://app.redstone.finance/app/token/wVLP_FUNDAMENTAL/">https://app.redstone.finance/app/token/wVLP_FUNDAMENTAL/</a></td></tr><tr><td>beHYPE</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/behype_main_fundamental/">https://app.redstone.finance/app/feeds/hyperevm/behype_main_fundamental/</a></td></tr><tr><td>dnPUMP</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/dnpump_fundamental/">https://app.redstone.finance/app/feeds/hyperevm/dnpump_fundamental/</a></td></tr><tr><td>dnHYPE</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/dnhype_fundamental/">https://app.redstone.finance/app/feeds/hyperevm/dnhype_fundamental/</a></td></tr><tr><td>lstHYPE</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/lsthype_fundamental/">https://app.redstone.finance/app/feeds/hyperevm/lsthype_fundamental/</a></td></tr><tr><td>liquidHYPE</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/behype_fundamental/">https://app.redstone.finance/app/feeds/hyperevm/behype_fundamental/</a></td></tr><tr><td>hbUSDC</td><td><a href="https://app.redstone.finance/app/feeds/hyperevm/hbusdc_fundamental/">https://app.redstone.finance/app/feeds/hyperevm/hbusdc_fundamental/</a></td></tr></tbody></table>


# Brand kit

{% hint style="success" %}
[View our brand kit here](https://www.hyperbeat.org/brand)
{% endhint %}


# Legal