Contract Interfaces and ABI

Contract Addresses & ABI

Below are the core contracts used by HyperFlash.


StakingManager

  • Testnet: TBD

  • Mainnet: 0x275B60596eFd03CE1C66b5F151a66F48B3E0FB44

  • Notes: Entry point for staking/unstaking and rate queries


FHYPE (ERC20)

  • Testnet: TBD

  • Mainnet: 0x57Ac5ee128A76531d7940966CaB290D5D8de9Cd4

  • Notes: fHYPE token (18 decimals), ERC20 + permit


ValidatorManager

  • Testnet: TBD

  • Mainnet: 0x8B723fb70cF103184a9D1e3f8B2b6E5175e6B360

  • Notes: Validator lifecycle and delegation target


PauserRegistry

  • Testnet: TBD

  • Mainnet: 0xD9BA155187975734FdA44cdF41C5268Bad9BeF20

  • Notes: Pause control and authorized contracts


ABI downloads:

  • StakingManager ABI:

file-download
257KB
  • FHYPE ABI:

file-download
102KB
  • ValidatorManager ABI:

file-download
123KB
  • PauserRegistry ABI:

file-download
71KB

Once our second audit concludes, the contracts will be verified on HyperEVM explorers.

On-chain functions

Developers interact primarily with StakingManager and the FHYPE ERC20.

  • Staking

Pass address(0) to use the default validator, or an active validator address on first stake.

  • Unstaking

Queue, wait for withdrawalDelay, then confirm to receive HYPE. A 0.1% unstake fee (default 10 bps) goes to treasury.

  • Exchange rate and conversions

Returns HYPE per fHYPE scaled to 1e18. Conversions don’t include the unstake fee.

  • FHYPE token (ERC20)

fHYPE uses 18 decimals and supports standard ERC20 operations.

Last updated