Hyperdrive networks are Ethereum, Base, Linea and Gnosis pool deployments

Transaction cost follows the selected network and pool

Network cost on Hyperdrive splits into chain gas, rollup data charges and the selected pool's configured trade fee. Gas and pool fees are separate deductions.

Every EVM network meters execution in gas. One gwei equals 1,000,000,000 wei, while one ETH equals 1,000,000,000,000,000,000 wei. Gnosis uses xDAI as its native gas asset and keeps the same 18-decimal base-unit convention. Ethereum quotes a base fee and priority fee. Base and Linea add rollup-specific data costs to execution. The wallet quote therefore reflects transaction complexity, calldata and network demand. A pool's curve fee and flat fee come from its configuration, while governance LP and zombie-fee shares allocate portions of pool economics. Those values belong to the pool, not the chain.

Separate a transaction quote into four layers:

• EVM execution gas for the contract call.
• Rollup data cost on Base or Linea.
• Hyperdrive curve and flat fees set in the pool configuration.
• Any independent swap or bridge transaction needed before entry.

Small positions feel fixed transaction costs most sharply because gas doesn't scale with deposit value. The flat fee also reflects the trade's remaining term, whereas the curve fee follows the curve portion of the trade. Compare the final asset output, not gas alone, when choosing among Hyperdrive networks.

Ethereum, Base, Linea and Gnosis serve different settlement needs

Ethereum, Base, Linea and Gnosis give Hyperdrive four distinct settlement environments rather than one shared liquidity venue. Each network keeps its own pool reserves and positions.

Ethereum is the L1 reference environment. Base is an OP Stack rollup that posts data to Ethereum, while Linea is a zkEVM rollup that uses validity proofs. Gnosis runs its own EVM execution and proof-of-stake consensus with xDAI for fees. These designs change transaction pricing, confirmation flow and bridge requirements. They don't change the core Hyperdrive interface: a local pool still reads a local yield source, prices terms and settles through contracts on that same chain.

A quoted rate on Linea has no claim on liquidity held by an Ethereum pool. Accessing it requires the right asset and gas on Linea.

Five identifiers prevent wrong-chain execution

Five fixed identifiers make Hyperdrive network selection verifiable before any wallet confirmation or contract call. Chain identity and contract identity must agree.

The canonical identifiers are chain ID 1 for Ethereum, 8453 for Base, 59144 for Linea and 100 for Gnosis. An EVM address contains 20 bytes, normally rendered as 40 hexadecimal characters after the prefix. A transaction hash contains 32 bytes or 64 hexadecimal characters. Recording the chain ID beside the pool address and transaction hash prevents two locally valid records from being mistaken for one position.

Ethereum concentrates L1 settlement and mature yield sources

Ethereum gives Hyperdrive direct L1 settlement and access to yield sources native to the main Ethereum ecosystem. ETH pays every transaction fee.

Ethereum uses chain ID 1 and 12-second consensus slots. Exactly 32 slots form a 6.4-minute epoch, although an empty slot produces no block. The Ethereum deployment set includes 182-day sDAI and stETH pools, an rETH pool tied to Rocket Pool and Morpho Blue markets involving sUSDe, USDe and DAI. Those examples span ERC-4626 vault shares, liquid-staking tokens and lending-market integrations. Lido, Rocket Pool, Ethena and Morpho therefore enter through distinct pool contracts rather than one universal asset adapter.

L1 settlement also places every approval, trade and close directly in Ethereum state. That path removes a rollup layer from the transaction lifecycle, while gas demand on Ethereum remains a separate cost variable.

Base pairs rollup execution with Coinbase ecosystem assets

Base gives Hyperdrive rollup execution, ETH-denominated gas and access to assets rooted in the Coinbase ecosystem. Its mainnet chain ID is 8453, as documented in Using Hyperdrive.

Base uses the OP Stack and submits compressed transaction data to Ethereum. A Base fee quote combines local execution with data-related charges, so calldata size matters alongside the contract's gas use. Base deployments include a 182-day cbETH pool, a Morpho Blue cbETH and USDC market and a Moonwell ETH vault integration. Coinbase issues cbETH, Circle issues USDC and Moonwell supplies an ERC-4626-compatible yield route. Those are separate reserves, even when their economic exposure resembles an Ethereum pool.

ETH bridged or acquired on Base pays gas there; ETH held only on Ethereum doesn't fund a Base transaction. Compare the Base pool's available depth and output against its complete fee quote.

Linea supports zkEVM settlement and liquid-staking integrations

Linea gives Hyperdrive a zkEVM venue where ETH settles gas and rollup proofs anchor state to Ethereum. Linea uses chain ID 59144.

The zkEVM design preserves familiar EVM addresses, calldata and Solidity contract behavior while changing the settlement path. Linea deployments include 182-day integrations for Renzo xezETH and Kelp DAO rsETH. Both represent liquid-restaking exposure, but each pool uses its own integration contract and reserves. A position in the xezETH pool doesn't draw liquidity from rsETH, Ethereum stETH or Base cbETH. The shared EVM programming model makes the calls familiar; it doesn't combine balances across networks or assets.

Linea transaction cost includes local execution and rollup data economics. Its quoted fixed rate remains pool-specific because reserves, trade direction and term state live in the Linea contract.

Gnosis settles gas in xDAI and emphasizes stable-value liquidity

Gnosis gives Hyperdrive an EVM chain with xDAI gas, five-second blocks and stable-value liquidity routes. Its chain ID is 100.

Gnosis specifies a 30,000,000-gas block size and uses GNO for consensus while xDAI pays transaction fees. Gnosis deployments include 182-day wstETH, sxDAI and sGYD pools. The wstETH route brings Lido exposure, sxDAI represents staked xDAI and sGYD connects a Gyroscope yield-bearing asset. Their gas token doesn't determine the deposited asset: an account needs xDAI for execution plus the exact base token or share token accepted by the selected pool.

A low gas quote doesn't compensate for insufficient pool depth. On Gnosis, the relevant comparison still joins the rate, price impact, term and redeemable asset.

Pool depth and term availability outweigh chain branding

Pool availability, usable depth and term length decide whether a Hyperdrive network is actionable for a specific trade. Network support alone isn't enough.

Deployed Hyperdrive contracts include 182-day pools on Ethereum, Base, Linea and Gnosis. A duration of 182 days equals 15,724,800 seconds, but a position's maturity follows the pool's checkpoint-based timestamp rules. Hyperdrive pools don't share reserves across chain IDs, so each contract develops its own bond reserves, share reserves and outstanding exposure. The displayed fixed annual percentage rate changes as trades move those reserves. A large balance on Ethereum therefore says nothing about executable size on Base, and a deep cbETH market doesn't create depth for Linea rsETH.

Read the pool address, base asset, vault-share asset, position duration, checkpoint duration and minimum transaction amount from that pool's configuration. Then inspect the quote for the intended size. This sequence keeps a network comparison tied to executable terms rather than ecosystem reputation.

Asset standards determine what each deployment supports

Asset standards define which yield source each Hyperdrive deployment accepts and how balances move through its contracts. ERC-20 handles transferable token balances and allowances.

ERC-4626 standardizes deposits, withdrawals and accounting for tokenized vault shares. Hyperdrive includes an ERC-4626 integration for compatible sources such as sDAI, sxDAI and Moonwell vaults. Direct integrations handle sources with different mechanics, including Lido stETH and Rocket Pool rETH. Chainlink-based instances read configured share-price data, while Morpho Blue instances connect lending-market positions. The integration kind is part of the pool contract; switching networks doesn't transform one kind into another.

Token precision also stays asset-specific. USDC uses 6 decimals, while DAI and ETH use 18. Interfaces must scale amounts with the selected token's decimals before submitting a minimum output. A familiar ticker isn't sufficient identity because chain ID and contract address define the actual asset.

Network switching, approvals and settlement stay local

Network switching keeps each Hyperdrive transaction, approval and resulting position inside one chain's state. A wallet switch doesn't move assets.

State before signing

The wallet should expose the active chain, native gas balance and local token balance before it constructs the Hyperdrive call.

Chain identity remains explicit

Ethereum reports 1, Base reports 8453, Linea reports 59144 and Gnosis reports 100 through the standard EVM chain identifier call. The selected Hyperdrive registry and pool address must belong to that response. Reusing an address string without its chain ID leaves the record ambiguous, even when deterministic deployment produced the same characters elsewhere.

Asset identity remains local

An ERC-20 approval authorizes a spender for one token contract on one chain. It grants nothing to a same-named token on another network. When a bridge delivers an asset, the destination contract address determines whether a Hyperdrive pool accepts it. The pool's base-token and vault-share getters resolve that requirement without relying on a ticker.

State after settlement

The receipt should show the expected chain ID, pool address, transaction status and emitted Hyperdrive events. A successful trade creates or changes a position only in that pool. Closing it later requires access to the same network and enough native gas for another transaction. Cross-chain movement starts a separate sequence: exit locally, bridge a supported asset and enter a destination pool.

The four-chain footprint reflects Hyperdrive's integration model

Hyperdrive's four-chain footprint reflects a deployment model built around local yield sources and reusable EVM interfaces. Expansion followed available integrations, not shared state.

Ethereum deployments began in June 2024, followed by Gnosis in August 2024 and Linea and Base in September 2024. Factories and deployer coordinators create instance-specific pools for ERC-4626, Lido, Rocket Pool, Chainlink, Morpho Blue and other supported sources. EIP-170 caps deployed contract code at 24,576 bytes, so Hyperdrive shards pool logic across a main contract and targets. The interface exposes five target addresses, numbered target0 through target4, beside the main pool address. That architecture repeats across networks while the reserves and positions remain local.

This structure explains the decisive network rule. Choose the chain because it hosts the exact yield source and pool you need, then judge that local market's depth, fees and settlement path.