Skip to main content
Hashbeam

Crypto protocols, markets and policy

5450c6

Native ETH and WETH Quotes: Compare the Route, Not the Label

ETH and WETH redeem at par, but their quotes can differ because routes, liquidity, fees and gas differ; compare the same trade and its full execution cost.

The Hashbeam Desk··5 min read

Abstract cover artwork for Native ETH and WETH Quotes: Compare the Route, Not the Label

To compare native ETH and WETH quotes, hold the trade constant and compare the route’s output and execution cost, because the two assets are redeemable at par but do not use the same token interface or necessarily the same liquidity. Native ETH is held as an account balance and sent as transaction value; WETH is an ERC-20 balance controlled by a token contract. Wrapping deposits ETH and mints WETH, while unwrapping burns WETH and releases ETH. The conversion rate is one to one, before transaction costs.

A quote is an estimate for a particular route and state, not a standing price for ETH. A native ETH trade may wrap ETH inside the transaction before sending it through an ERC-20 pool. Another route may use a pool that accepts WETH directly. For the transaction path, approvals, and gas mechanics behind that distinction, see the fuller fermi swap article.

Why can ETH and WETH quotes differ?

They can differ because the quote may use different pools, routing steps, fees, or execution assumptions, even when the input value is economically equivalent. WETH’s one-to-one redemption relationship with ETH does not require every trading pool to offer the same price for each asset against a third token.

For example, an ETH-to-token route might wrap ETH and then swap WETH in an ERC-20 pool. A WETH-to-token route might use that pool directly, or use a different pool and intermediate asset. Each swap applies the pricing curve and fee rules of the pools it touches. A route that splits an order across pools can produce another output. Differences can therefore reflect available liquidity and route construction rather than a discount or premium in WETH’s redemption value.

Some interfaces label a route “ETH” because the user pays with native ETH, even if the swap contract handles WETH internally. The label alone does not establish which pools the route uses or whether wrapping is part of the transaction. Check the route details and transaction summary where available.

What should stay the same when comparing quotes?

Use the same chain, trade size, direction, recipient, and quote conditions; otherwise the numbers do not isolate the ETH-versus-WETH difference. Confirm the token’s chain and contract identity too: a token called WETH on one network is not identified by its name alone.

Compare quotes for the same output asset and either the same exact input or the same exact output. Then inspect the route, estimated output, fees, and any price-impact or minimum-output setting the interface provides. A comparison between “spend this much ETH” and “receive exactly this much of the other token” is not like-for-like unless the amounts and fee treatment line up.

  • Keep the network and output token identical.
  • Match the trade size and exact-input or exact-output mode.
  • Read the route steps and pool fees, including any wrap or unwrap.
  • Compare the estimated output after swap fees, then account for gas separately.

Quotes are based on pool state at the time they are produced. If that state changes before execution, the realized output can differ. A minimum-output condition limits how far execution may fall below the quoted expectation; it does not make the quote itself current or guarantee that the transaction will succeed.

How do wrapping, approvals, and gas affect the comparison?

Wrapping and unwrapping are contract calls, so a route that performs either can use more gas than a direct token swap. The added cost depends on the actual transaction path; it should be read from the transaction estimate rather than inferred from the ETH or WETH label.

WETH is an ERC-20, so a swap contract that pulls WETH from a wallet generally needs token allowance. Native ETH is instead attached to a transaction as value, so it does not use an ERC-20 allowance. An interface may combine wrapping and a swap in one transaction, while a separate wrap action requires its own transaction. If the wallet has not approved WETH already, include any approval transaction’s gas when comparing the cost of completing the trade. That approval is not necessarily repeated on every later trade.

Gas is paid in the network’s native asset, ETH on Ethereum, not in WETH. A WETH quote therefore does not remove the need to hold ETH for execution. For a fair economic comparison, consider both the swap’s expected output and the ETH-denominated gas for the actions needed to reach that output. Separate setup costs, such as a first-time approval, from costs that recur on each swap, but include both when they are part of the decision at hand.

Which quote is the better one?

The better quote is the route that delivers more of the same output asset after accounting for all required transaction costs and conditions. If the estimated outputs match, a direct WETH route may avoid an extra wrap step; if the native ETH route reaches deeper liquidity, its higher swap output may outweigh the additional gas. The route and execution cost decide the comparison, not the ticker.

For most readers, compare the final token amount and the total ETH needed to execute, including any required approval or conversion. Treat the one-to-one ETH/WETH relationship as the conversion baseline, not as proof that two swap quotes must match.