Contract Architecture

HyperQuote’s smart contracts are deployed on HyperEVM (chain ID 999) as non-upgradeable, immutable contracts. This page describes the dependency graph, design patterns, and high-level structure.

Dependency Graph

The diagram below shows the contract inheritance hierarchy and shared dependencies between the OptionsEngine and SettlementPublisher contracts.

Compiler Configuration

All contracts use Solidity 0.8.24 with via_ir enabled in the Foundry configuration. This produces optimized bytecode through the intermediate representation pipeline. OpenZeppelin v5 contracts are imported as dependencies.

[profile.default]
solc = "0.8.24"
via_ir = true

EIP-712 Domain

The OptionsEngine uses a fixed EIP-712 domain for quote signature verification:

EIP712("HyperQuote Options", "1")

The full domain includes:

• name: "HyperQuote Options"
• version: "1"
• chainId: Set at deployment (999 for HyperEVM mainnet)
• verifyingContract: The deployed OptionsEngine address

All quote signatures must be produced against this exact domain. The relay and SDK use the same domain parameters.

Admin Pattern

Both OptionsEngine and SettlementPublisher use OpenZeppelin’s Ownable for admin access control. The owner can:

OptionsEngine:

• Add/remove allowed collateral tokens (setAllowedCollateral)
• Add/remove allowed underlying tokens (setAllowedUnderlying)
• Update the oracle address (setOracle)
• Set keeper fee parameters (setKeeperBps, setMaxKeeperFee)
• Pause/unpause the contract

SettlementPublisher:

• Add/remove authorized price publishers (addPublisher, removePublisher)

ERC-721 Position NFTs

Each filled options position is minted as an ERC-721 NFT ("HyperQuote Option", symbol "HQOPT"). The NFT is minted to the buyer (maker in V1) at execution time and burned upon settlement or expiry.

The NFT ID is a sequential counter starting at 1. The position data (seller, buyer, underlying, collateral, strike, quantity, premium, expiry, collateral locked, state) is stored in a mapping keyed by the NFT ID.

Position States

enum PositionState {
  Active,    // Position is live, awaiting expiry
  Settled,   // ITM position settled via physical delivery
  Expired    // OTM/ATM position expired, collateral returned to seller
}

Contract Interactions

A typical options lifecycle involves these contract calls:

1. Taker approves collateral/underlying tokens to the OptionsEngine
2. Taker calls execute() with the maker’s signed EIP-712 quote
3. OptionsEngine verifies signature, creates position, mints NFT, transfers premium, locks collateral
4. Publisher commits settlement price hash before expiry
5. Publisher reveals settlement price after the reveal delay
6. Anyone calls settle() for ITM positions (keeper model) or expirePosition() for OTM positions after the settlement window

Security Properties

• Reentrancy protection: All state-modifying functions use nonReentrant
• Replay protection: Each quote hash is marked as used after execution; nonce ordering provides bulk cancellation
• Immutable deployment: No proxy pattern, no upgrade path
• Checked arithmetic: Solidity 0.8.24 has built-in overflow checks