Skip to main content

Interactions with HyperCore.

Hyperbeat Staking - beHYPE

Pulse.hl | Hyperbeat avatar
Written by Pulse.hl | Hyperbeat
Updated over 2 months ago

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.

Did this answer your question?