Wrapped Ether (WETH)

Overview

Wrapped Ether, or WETH, is an ERC-20-compatible representation of native ETH used by smart contracts and decentralized applications that expect token-standard interfaces.

Users deposit ETH into the canonical wrapper to mint an equal amount of WETH and can burn WETH through withdrawal to receive ETH one-to-one. The supply of Wrapped Ether (WETH) should correspond to assets held, burned, or verifiably controlled by the wrapping system. Some designs use a centralized custodian, others use threshold signers or smart contracts, and synthetic versions may use collateral rather than one-for-one custody.

WETH is not a staking token, yield-bearing asset, or bridge by itself, and WETH contracts on other networks can represent different native or bridged assets. A wallet may show Wrapped Ether (WETH) beside the underlying coin at a similar price, but their settlement guarantees differ. native ownership follows the base network, whereas the wrapped balance also depends on the wrapper’s contracts, keys, custody, and cross-chain messaging.

Risks include fake wrapper contracts, malicious approvals, wrong-chain transfers, contract errors, bridge exposure, and wrapping all available ETH needed for gas. A one-to-one market price is not proof of one-to-one backing. Verification should consider on-chain supply, custody or lock evidence, mint authority, redemption tests, audits, and whether the bridge or issuer still supports the specific network.

Applications should verify the canonical contract for the target chain, deposit and withdrawal events, balance change, allowance, recipient, and remaining ETH fee balance. Treasury policy should define whether Wrapped Ether (WETH) can be held, converted, or accepted only temporarily. For Wrapped Ether (WETH), operators should monitor proof of backing, bridge status, contract upgrades, liquidity, withdrawal limits, and official deprecation notices before allowing deposits or payouts.

Comparisons with Ether (ETH) clarify the role of Wrapped Ether (WETH), while also showing why similar names do not create identical custody, redemption, or accounting treatment.