Hyperleaf · Docs

Hyperleaf Documentation

Infrastructure for liquid staking on HyperEVM

• App: https://hyperleaf.finance/app
• Site: https://hyperleaf.finance

What is Hyperleaf

Hyperleaf is infrastructure for liquid staking on HyperEVM.

Phase 1 focuses on Nest: deposit NEST, receive transferable hNEST. The vault locks NEST into Nest’s veNEST flow (about 26 weeks) and attaches to Nest’s HYPE Engine Vault (HEV, managedTokenId = 1). Nest handles voting and relock on that attachment. You do not vote or manage locks yourself.

hNEST is an ERC-20 receipt — transferable, not a hard peg to NEST, not a promise of instant face-value redeem.

Hyperleaf Phase 1:

• Accepts NEST (pause / cap may apply)
• Mints hNEST against deposited liability
• Locks most NEST into Nest + HEV; keeps about 1% idle (idleDepositBps = 100) for withdraw liquidity, with a minimum idle floor (minIdleNest, currently 50 NEST)
• Offers a queue-based protocol exit (not instant unlock)

Hyperleaf does not (yet):

• Offer in-app HYPE claim (Nest HYPE Spring is a separate Nest-side Merkle claim)
• Claim that hNEST NAV auto-compounds while recordCompound is disabled
• Launch a Hyperleaf token, run a points program, or claim audited status

Deposits are enabled on HyperEVM. That means the vault can accept deposits — not a marketing launch. Current deposit cap (as of 2026-09-06): 20000 NEST on-chain; the Owner may raise it. Always trust the live chain / app value if it differs.

Token & points

• No plans to launch a Hyperleaf protocol token.
• No Hyperleaf points program. Rewards referenced in the product are underlying Nest staking rewards only — not Hyperleaf points or loyalty farming.

How to deposit

1. Connect a wallet on HyperEVM (chain id 999).

2. Hold NEST + gas.

3. In the app: Approve NEST → Deposit.

4. Receive hNEST.

About 1% of each deposit stays as vault idle NEST; the rest is locked into Nest / HEV.

If the cap is hit or deposits are paused, wait for owner updates — the app surfaces live state.

Explorers may show attached lock amount/end = 0. That is expected under Nest HEV attachment, not a zeroed user balance.

How to exit

Primary path: sell or swap hNEST on secondary markets when liquidity exists. Expect discount/premium and thin books early.

Fallback: protocol redeem via withdraw queue.

• requestWithdraw burns hNEST and enqueues — it does not immediately dettach.
• A keeper may dettach positions when the queue needs liquidity (Nest detachment gates apply, on the order of days after attach plus vote-window rules).
• After dettach, Nest’s unlock clock is about ~26 weeks (~6 months).
• Queue fulfillment spends idle surplus only (above minIdleNest).

Not instant. Not a spot peg. Prefer market exit when you need speed.

Risks

• No hard peg; no fixed APY
• Protocol exit can take on the order of ~6 months after dettach, plus queue/idle limits
• ~1% idle skim on deposit; idle floor currently 50 NEST
• Smart contract, Nest/HEV, and ops (pause/cap) risk
• Not yet externally audited
• While recordCompound is disabled, do not assume share price auto-rises from Nest compounding
• No in-app HYPE claim; Nest HYPE Spring is a separate Merkle claim(proof, account, amount) on Nest’s claim contract (example: 0x33afCe55…0905), by wallet proof — not a direct Vault claim
• No personal redemption backstop is promised publicly

Contracts (HyperEVM 999)

Explorer: https://hyperevmscan.io

Flow: NEST.approve(Vault) → Vault.deposit

Parameters such as depositCap, idleDepositBps, and minIdleNest are on-chain. If docs and chain disagree, chain wins. ABI package: protocol repo deployments/frontend-abi/.

Appendix — roles (ops, not marketing)