Skip to main content

Technology and Platform

This page provides a technical overview of the foundational layers and technologies that Hyra Network is built on.

  • Layer 1: Ethereum – root security and final settlement
  • Layer 2: Base – optimistic rollup scalability and L2 verification
  • Layer 3: Hyra Network (Orbit + AnyTrust) – specialized L3 for AI and compute

Unlike the System Architecture page (which explains how components interact and how the system runs), this page focuses on what technologies are used and why.

1. Layer 1 – Ethereum​

1.1 Overview​

Ethereum is the root trust layer in the Hyra stack. It provides:

  • Final settlement for Layer 2 and Layer 3
  • Economic security through Proof of Stake
  • A standardized smart contract platform (EVM)
  • A data availability fallback of last resort

Base (L2) is built on Ethereum, and Hyra (L3) is deployed on Base.
So security flows as:

Ethereum (L1) → Base (L2) → Hyra Network (L3)

1.2 Ethereum Virtual Machine (EVM)​

The EVM is the standard execution environment used by smart contracts on Ethereum and EVM-compatible chains.

Key properties:

  • Deterministic execution of bytecode
  • Account and storage model
  • Gas metering and resource accounting
  • Wide tooling support (Solidity, Hardhat, Foundry, etc.)

Hyra Network, via Base and Orbit, is fully EVM compatible, allowing Hyra contracts to use the same tooling and patterns as normal Ethereum smart contracts.

1.3 Proof of Stake Consensus​

Ethereum uses Proof of Stake (PoS) for block production and finality.

Important aspects:

  • Validators stake ETH and propose/attest to blocks
  • Slashing discourages malicious behavior
  • Economic finality: once blocks are finalized, reverting them is extremely costly

All rollup and L3 guarantees ultimately rest on this PoS security.

1.4 Networking and Data Availability​

Ethereum clients participate in a peer–to–peer network that:

  • Propagates blocks and transactions
  • Synchronizes chain state
  • Provides baseline data availability

While Hyra primarily relies on Base and AnyTrust for DA, Ethereum remains the ultimate fallback in worst-case scenarios where upper layers must rely on L1.

2. Layer 2 – Base (Optimistic Rollup)​

2.1 Overview​

Base is an Optimistic Rollup built on top of Ethereum using the OP Stack. It provides:

  • Low-fee, high-throughput execution environment
  • EVM equivalence
  • Rollup security model with fraud proofs
  • Native bridges between Ethereum and Base

Hyra Network uses Base as its parent chain for:

  • Settlement of Layer 3 batches
  • Bridge primitives
  • Inherited security guarantees

2.2 OP Stack Architecture​

The OP Stack splits responsibilities into multiple layers:

  • Execution Layer – where EVM transactions are executed
  • Derivation Layer – reconstructs L2 blocks from L1 data
  • Settlement Layer – posts state roots to Ethereum
  • Data Availability Layer – handles where transaction data is stored

This modular design allows Base to be flexible and upgradable, and Hyra benefits from this architecture.

2.3 Base Sequencer and Verifiers​

Base has its own L2 sequencer and verifier logic:

  • Sequencer

    • Orders L2 transactions
    • Produces L2 blocks
    • Submits batches to Ethereum

  • Verifiers

    • Reconstruct chain state
    • Can challenge invalid state transitions through fraud proofs

Hyra’s L3 sequencer and validator logic sits “on top” of this, relying on Base’s correctness and settlement.

2.4 Fraud Proofs and State Roots​

Base is an Optimistic Rollup:

  • It assumes batches are correct by default
  • It allows a challenge window where anyone can submit a fraud proof
  • Fraud proofs re-execute a segment of the chain to verify correctness
  • Final state roots are posted to Ethereum for long-term security

Hyra L3 uses Base as the verification and settlement layer for its own batches.

2.5 L1–L2 Bridging​

Base provides standard bridging mechanisms:

  • Bridging ETH and ERC-20 tokens
  • Cross-domain messaging between Ethereum and Base
  • Withdrawals with a delay period for fraud-proof safety

Hyra’s L3 bridge uses these primitives to connect assets and messages across the three layers.

3. Layer 3 – Hyra Network (Orbit and AnyTrust)​

3.1 Overview​

Hyra Network is a Layer 3 Orbit chain deployed on Base. It is optimized for:

  • AI-related workloads
  • Decentralized compute coordination
  • Micro-transaction heavy applications

It combines:

  • Arbitrum Orbit for Layer 3 execution
  • AnyTrust Data Availability for low-cost DA
  • EVM compatibility for developer friendliness

3.2 Orbit Technology​

Orbit chains are built using the Arbitrum Nitro/Orbit framework.
Hyra leverages this stack for its L3:

  • ArbOS-like execution kernel
  • Nitro-style derivation and state management
  • EVM-compatible environment

Key properties:

  • Deterministic block derivation
  • Compatibility with existing toolchains
  • Flexible configuration (gas, fees, parameters)

Hyra chooses an EVM-equivalent Orbit configuration to maximize developer adoption.

3.3 Layer 3 Derivation and State Commitments​

At a high level, Hyra’s L3 derivation process:

  1. Hyra accepts L3 transactions and executes them locally.
  2. The sequencer builds L3 blocks and aggregates them into batches.
  3. The aggregator prepares metadata and data availability information.
  4. The batch metadata and commitments (including DAC signatures) are posted to Base.
  5. Contracts on Base verify and track these batch commitments.

This creates a chain of verifiable state roots anchored to Base, which is anchored to Ethereum.

3.4 AnyTrust Data Availability Model​

Hyra uses AnyTrust as the primary DA model for L3.

The idea:

  • Instead of posting all data on L1 or L2, Hyra posts data to a Data Availability Committee (DAC).
  • Only succinct metadata and signatures are posted on Base.
  • This results in much lower costs while keeping safety fallback mechanisms.

3.4.1 Data Availability Committee (DAC)​

A DAC is a committee of independent servers/operators that:

  • Receive full batch data from Hyra
  • Store that data for a defined retention period
  • Sign the batch hash when data is safely stored

Hyra’s design:

  • Requires a quorum of DAC members to sign each batch
  • Uses these signatures as proof that data is available
  • Posts the signatures and metadata to Base

If the DAC is operating correctly and a quorum signs, data is assumed to be available at very low cost.

3.4.2 Quorum and Safety​

AnyTrust relies on a simple trust assumption:

  • As long as at least one honest DAC member in the quorum provides data when needed, the system is safe.
  • The chain checks that enough DAC signatures are present before treating a batch as valid in AnyTrust mode.

If the DAC fails to reach quorum:

  • Hyra falls back to a rollup-style DA mode, posting full data to Base.
  • This prevents data withholding attacks and keeps the system recoverable.

3.4.3 Rollup Fallback​

Rollup fallback ensures that:

  • If DAC members are offline, malicious, or unresponsive, Hyra can still continue operating.
  • Full batch data is posted on Base.
  • The cost is higher, but security does not degrade.

This is a critical property: cost optimization without sacrificing safety.

3.5 Data Availability Modes​

Hyra can conceptually support multiple DA configurations:

  1. DAC-based (AnyTrust mode) – default, lowest cost, uses DAC signatures.
  2. L2 DA mode – post compressed data directly on Base for higher security and slightly higher cost.
  3. L1 DA mode – post data directly on Ethereum in extreme cases, with maximum security and highest cost.

In practice, Hyra runs in AnyTrust mode by default with automatic fallback to rollup-style posting if the DAC is unavailable.

3.6 Execution Environment and Future Extensibility​

Hyra’s execution layer is designed to be:

  • EVM-compatible from day one
  • Friendly for Solidity contracts and existing tooling
  • Open to future enhancements, such as:
    • WASM execution environments
    • Zero-knowledge proof integration
    • ML model attestation and verification

This allows Hyra to evolve from a simple EVM L3 into a specialized compute and AI platform while keeping its base tech stack stable.

3.7 Bridging Architecture​

Hyra uses a multi-layer bridging approach:

  • Ethereum ↔ Base bridge provided by Base (canonical L1–L2 bridge)
  • Base ↔ Hyra bridge for L2–L3 assets and messages

Bridge use cases:

  • Moving tokens between L1, L2, and L3
  • Passing messages and instructions (for example: task requests, settlement messages)
  • Coordinating state and liquidity across layers

This allows Hyra to act as a specialized execution environment while still staying connected to the broader Ethereum ecosystem.

4. Why Layer 3 for AI and Compute​

Hyra’s choice to be an L3 is driven by the needs of AI and decentralized compute:

  • High frequency, low-value transactions (for example: task updates, micro-rewards)
  • Tight feedback loops between on-chain logic and off-chain compute providers
  • Demand for very low fees and high throughput

Layer 3 allows Hyra to:

  • Offload most load from L1 and L2
  • Optimize parameters (gas, block time, costs) specifically for its AI and compute use cases
  • Innovate faster at the application layer without impacting base layer consensus or security

5. Summary​

The Technology and Platform stack behind Hyra Network can be summarized as:

  • Ethereum (L1)

    • Root security, PoS consensus, settlement and ultimate DA fallback.

  • Base (L2)

    • Optimistic Rollup, OP Stack, state roots, fraud proofs, L1–L2 bridging.

  • Hyra Network (L3 on Orbit + AnyTrust)

    • EVM-compatible execution, AnyTrust data availability via DAC, rollup fallback, low-cost high-throughput environment for AI and compute.

Together, these layers allow Hyra Network to operate as a secure, scalable, and specialized Layer 3 platform for AI, GPU sharing, and microtransaction-heavy applications.