# Handling of ETH and tokens
The previous versions of the testnet allowed users to pay fees with ERC20 tokens. However with the advent of the paymaster feature it has become redundant. To provide better compatibility and alignment with the L1, zkSync 2.0 allows only ether as a fee token.
ETH is implemented as a special token with address
0x000000000000000000000000000000000000800a, though zero address (
0x0000000000000000000000000000000000000000) is often used as an alias for it. It can only be transferred by providing
msg.value, i.e. the same way it is done on Ethereum and it does not expose the ERC20 contract interface.
Similar to other rollups, zkSync provides a native ETH bridge, while the rest of the bridges are built using L1<->L2 messaging. The team provides a generic ERC20 token bridge that can be used by anyone for bridging token to L2. More details on the bridges' architecture will be published soon.