WETH vs ETH: Why Wrapped Ether Exists and When You Need It
Understanding the WETH vs ETH distinction is essential for anyone active in Ethereum DeFi. This guide explains why wrapped Ether exists, how it differs from native ETH, and the exact scenarios where you need it.
What Native ETH Actually Is
ETH serves as the native asset and gas token of the Ethereum blockchain. Every transaction on the network consumes a portion of ETH to pay for computation and storage, which compensates validators and deters spam attacks.
Validators stake ETH to participate in Ethereum's proof-of-stake consensus. This staking mechanism secures the network by creating economic incentives for honest validation while imposing financial penalties on misbehavior through slashing.
Because ETH was created before the ERC-20 standard existed, it lacks the required interface functions such as approve and transferFrom. Consequently, it cannot be used directly inside most smart contracts that power DeFi protocols, liquidity pools, lending markets, or NFT marketplaces, all of which expect ERC-20 tokens.
Native ETH therefore remains essential for paying gas fees even when users hold wrapped versions of the asset, since WETH does not natively cover transaction costs on Ethereum.
Why Wrapped Ether Was Created
Native ETH predates the ERC-20 standard, so it lacks the interface functions such as approve and transferFrom that most DeFi protocols expect. Early liquidity pools, DEX pairs, lending markets, and NFT marketplaces were therefore built around ERC-20 tokens and could not accept native ETH directly.
This mismatch produced concrete problems. Protocols had to maintain separate code paths or wrapper logic for ETH, which fragmented liquidity and limited composability. A user holding ETH could not supply it to a standard ERC-20 pair or deposit it into a lending contract without first converting it, creating friction that slowed adoption of DeFi applications.
WETH solved the issue by wrapping ETH inside a simple smart contract that mints an ERC-20 token on a 1:1 basis. The canonical WETH9 contract on mainnet (0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2) locks ETH and issues the equivalent WETH; the reverse operation burns WETH and releases ETH. Because the solution lives entirely in a contract layer, it required no changes to the base Ethereum protocol or gas mechanics. Native ETH remains necessary for transaction fees, while WETH supplies the missing ERC-20 compatibility that lets protocols treat it identically to any other token.
The Wrapping and Unwrapping Process
The canonical WETH9 contract on Ethereum mainnet, located at 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2, executes the wrapping process by accepting a deposit of native ETH. The contract locks the deposited ETH and mints an identical quantity of WETH tokens, preserving a strict 1:1 peg backed by the locked collateral.
Unwrapping reverses the operation through a call to the contract’s withdraw function. This burns the specified WETH amount and releases the equivalent ETH back to the caller. Because each token remains fully collateralized, the peg holds without deviation under normal conditions.
Both actions incur only standard Ethereum network gas fees; the contract itself charges no protocol fee. Users perform wrapping and unwrapping through wallet interfaces, decentralized exchange front-ends such as Uniswap, or direct contract calls via block explorers. Similar wrapped-ETH contracts exist on Layer-2 networks, yet participants must verify the specific deployment address before use.
ETH vs WETH: Key Differences Table
The distinctions between native ETH and WETH appear most clearly across technical standards and operational roles.
| Aspect | ETH | WETH |
|---|---|---|
| Token Standard | Native asset predating ERC-20; lacks approve, transferFrom and other interface functions. | ERC-20 token issued by the WETH9 contract at 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2. |
| Usability in DeFi Protocols | Incompatible with most liquidity pools, lending markets and NFT marketplaces that expect ERC-20 tokens. | Directly usable in DEX pairs, lending protocols and marketplaces requiring the ERC-20 interface. |
| Gas Behavior | Pays all Ethereum transaction fees; required for any on-chain action. | Cannot cover gas; users must retain separate ETH balances for fees. |
| Custody Requirements | Held directly in wallets or exchanges without contract mediation for ownership. | Stored in the same wallets yet created only through the canonical wrapping contract while preserving 1:1 value. |
| Liquidity Sources | Obtained via exchanges, issuance or staking; total supply approximately 122.05 million ETH. | Generated by wrapping ETH or trading on venues such as Uniswap; market cap near $5.13 billion with 2.04 million tokens in circulation as of 2026-09-14. |
These contrasts explain why DeFi applications standardize on WETH while native ETH remains essential for fees and base-layer transfers. Data from MetaMask and DefiLlama confirm the peg and supply figures on that date, with roughly 3 percent of ETH locked in the WETH contract.
When You Actually Need WETH
DeFi protocols and NFT platforms built on the ERC-20 standard cannot accept native ETH directly because it predates that interface and lacks the required functions. Users therefore convert ETH to WETH when they need to supply liquidity, lend assets, or place bids in those environments.
On Uniswap V2 and V3, adding liquidity to an ETH trading pair means first wrapping ETH so the pool contract can treat both sides as ERC-20 tokens. The same requirement applies when removing liquidity or collecting fees. Although v4 and UniswapX routes can sometimes bypass the step for simple swaps, liquidity provision still relies on WETH in the majority of active pools.
Lending protocols such as Aave list WETH as a distinct market. Depositors supply WETH to earn interest or use it as collateral for borrowing other assets; the smart contracts expect the ERC-20 approval and transfer mechanics that only WETH provides.
Several NFT marketplaces require WETH for offers and purchases because their settlement contracts are written exclusively for ERC-20 tokens. Bidders wrap ETH once, then interact with the marketplace without repeated gas-intensive native-ETH handling.
In each case native ETH remains necessary only for transaction fees, while WETH serves as the interchangeable unit inside the protocol itself.
FAQ
Is WETH worth exactly the same as ETH?
As of 2026-09-14, WETH traded at $2,511.17 with a market cap of $5.13 billion, while ETH traded between $2,507 and $2,515, preserving the 1:1 economic equivalence created by the canonical contract.
Can I always convert WETH back to ETH?
The wrapping process is fully reversible at a 1:1 ratio. Calling withdraw on the WETH9 contract burns the WETH tokens and releases the locked ETH without additional protocol fees.
What security risks should I consider with WETH?
The mainnet WETH9 contract at 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 has been formally verified and remains battle-tested, with approximately 3% of circulating ETH supply locked inside it as of September 2026.
Are there extra fees when wrapping or unwrapping?
Only standard Ethereum gas costs apply. The contract itself imposes no protocol fee for either the deposit or withdraw functions.
Do regulatory rules treat ETH and WETH differently?
Both assets face similar oversight, yet WETH usage inside DeFi protocols or liquidity pools can trigger platform-specific compliance reviews or transaction monitoring under frameworks such as the Travel Rule.
Why do some DEXes require WETH instead of native ETH?
Native ETH predates the ERC-20 standard and lacks functions such as approve and transferFrom, so most DeFi contracts and NFT marketplaces expect the ERC-20 interface that WETH supplies.
Can WETH pay gas fees on Ethereum?
No. Only native ETH can cover transaction fees; WETH must first be unwrapped before it can be used for gas.