What EVM is, and why you have the same address on Ethereum, BNB Chain and Polygon
In plain words
EVM is the “engine” built into the Ethereum network that runs smart contracts identically on every computer in the network. Other networks, such as BNB Chain, Polygon, Arbitrum and Base, adopted this engine, which is why the same wallets, the same “0x…” addresses and the same token standards work on all of them. Convenient, but with a trap: one address exists on all these networks at once, and a wallet will not stop a transfer to the wrong one.
EVM stands for Ethereum Virtual Machine. It is the part of the network that runs programs, that is smart contracts, which the article smart contract explains. Every computer taking part in the Ethereum network runs the same EVM and pushes the same operations through it, so the result is identical everywhere. Each operation inside the EVM is paid for with a fee called gas, and the article what is gas explains how it works 1.
Think of a games console. A game is written once and runs on any console of that model, behaving the same way on all of them. EVM is that kind of console for smart contracts. A token, an exchange with no intermediary or an NFT collection is written for it once and then works wherever that console is installed.
Why does this matter to you? Because the “console” is not installed only on Ethereum. Many other networks copied the EVM, and as a result one wallet and one address work across a dozen networks at once. That is convenient right up until you send a token to the wrong network. Below we explain why that happens and how to avoid it.
Deeper
What "EVM-compatible network" means
A network is called EVM-compatible if the same engine as Ethereum’s runs inside it and programs written for Ethereum run there without being rewritten. BNB Chain, Polygon and Avalanche are built this way, as are the layer-two networks on top of Ethereum itself, such as Arbitrum, Optimism and Base. Each of them is a separate network with its own coin for paying gas and its own rules, but with a shared “language” for programs and wallets. Networks built differently, such as Solana, Tron or Bitcoin, are not EVM networks; they have their own engines and their own address formats.
Three shared things follow from the shared engine. First: the same address format, forty characters after “0x”. Second: the same wallets, MetaMask or Trust Wallet, work with all these networks, and all it takes is adding the network to the list. Third: the ERC-20 token standard, which the article token standards explains, is repeated on these networks under their own names, BEP-20 on BNB Chain and so on.
Why you have one address on every EVM network
An address on an EVM network is calculated from your private key, which the article what is a private key explains. The method of calculation is the same on every EVM network, and you have one key, so the address comes out the same. Your address on Ethereum, BNB Chain, Polygon and Arbitrum matches character for character. That is neither a coincidence nor a wallet bug but a direct consequence of the shared engine.
What matters is that this is one address but not one balance. Each network keeps its own record of what sits at that address. Picture the same flat number in several buildings on different streets: the number is shared, the flats are different, and things from one do not appear in another. Your USDT on Ethereum and your USDT on Polygon are two different balances at one address, and the wallet shows whichever one belongs to the network currently selected.
The trap: a transfer to the wrong EVM network
When networks are built differently, a mistake usually does not get past the form: a Tron address starts with “T”. An exchange will not accept it in the field for the Ethereum network. EVM networks have no such protection. A “0x…” address is equally valid for Ethereum, BNB Chain and Polygon. So neither the exchange nor the wallet sees anything suspicious and sends the token to the network you picked from the list, even if the recipient was expecting it on a different one.
Let’s take an example. You hold USDT on an exchange and need to send it to someone who gave you a “0x…” address and said they expect USDT on the Polygon network. On withdrawal the exchange shows the list of networks for USDT, and it includes Ethereum, Polygon, BNB Chain and others. You are in a hurry and pick BNB Chain. The exchange checks the address, it fits, the transfer goes through, and a minute later the history says “completed”. No error is visible anywhere: the address is right, the amount is right, only the “flat” is wrong. The USDT sits at the recipient’s address on BNB Chain, while they are looking at that same address on Polygon and see zero.
From here everything depends on one question: who holds the key to that address.
If the address belongs to an ordinary crypto wallet, yours or the recipient’s, where a person holds the key, the money has not gone anywhere. The wallet’s owner adds the BNB Chain network to the wallet, switches to it, and the USDT appears in the balance. To send it on or swap it, they will need a little BNB for the fee. Because on that network gas is paid in BNB, as the article what is gas explains. The loss here is only time and a small fee for sending it back.
If the address belongs to an exchange or a swap service, the picture is different. This is a deposit address the service issued to the recipient, and the key to it is held by the service, not by a person. The service expected USDT on Polygon, it arrived on BNB Chain, and its system did not credit the deposit. There is nothing you can do on your own here. You need to write to the receiving service’s support and attach the transaction hash, the amount, the name of the network the transfer went to, and the address. Some services return such transfers manually, for a fee and not quickly; others refuse, especially if they do not support that network at all. The hash and the network are taken from the explorer of the network the money actually went to where to check: the explorer of the transfer’s network, for example BscScan for BNB Chain, PolygonScan for Polygon, Etherscan for Ethereum.
A similar thing happens with the token itself. If you sent USDC instead of USDT to an ordinary crypto wallet by mistake, the recipient simply receives USDC, and that is easy to put right. If the wrong token went to an exchange’s deposit address, it again depends on the exchange: some credit a “foreign” token if they support it, others return it only through support.
Before sending to any EVM network, check two fields, not one: the address and the network. On an exchange the network is chosen from a separate list at withdrawal; in a wallet, with the network switcher at the top. The network in the withdrawal field and the network the recipient is expecting must match letter for letter. If the recipient is an exchange or a swap service, a mistake costs the most, so the first transfer there is always a test one, for a small amount.
Frequently asked questions
- Is EVM the same thing as ETH or Ethereum? No, these are three different things, even though the words look alike. Ethereum is the network itself, that is thousands of computers around the world that together keep a shared record of who owns what. ETH is that network’s own coin, used to pay the fee for every operation. EVM is the engine inside the network that runs programs, the smart contracts. When another network, say BNB Chain, adopts the EVM, it copies only the engine. Its coin stays its own, BNB, and the computers that support it are its own too. So “EVM-compatible” does not mean “part of Ethereum” and does not mean “runs on ETH”.
- What is an “EVM wallet”? It is a crypto wallet that can work with networks built on the EVM engine. In practice that means three things. It shows your balance on Ethereum, BNB Chain, Polygon, Arbitrum and other EVM networks under one and the same address. It can send coins and tokens on each of those networks, provided you hold that network’s coin for the fee. It can connect to websites built on smart contracts, for example exchanges with no intermediary. MetaMask and Trust Wallet are examples of such wallets. The word “EVM” in a wallet’s description speaks only to compatibility with these networks and says nothing about how reliable or safe the wallet is. How to choose a crypto wallet on the merits is covered in the hub how to choose a crypto wallet.
- Is Solana an EVM network? No. Solana, Tron, Bitcoin and the XRP Ledger are built on their own engines. Their addresses look different: a Solana address is a long string of letters and digits with no “0x” at the start, a Tron address starts with the letter “T”. So an address from MetaMask or another EVM wallet cannot be given to anyone to receive SOL. USDT on Solana will not show up at your “0x” address, even if the amount is right. For these networks you need either a separate wallet or a wallet that supports both EVM networks and Solana at the same time, and those exist too.
What EVM does not guarantee
A shared engine does not make networks equally reliable. Each EVM network has its own set of computers supporting it, its own rules for issuing its coin and its own risks. A layer-two network on top of Ethereum depends on Ethereum; a standalone network like BNB Chain depends on its own validators and on the company developing it. Compatibility of programs does not mean compatibility of risks. So before keeping a noticeable sum on an unfamiliar EVM network, it is worth looking at its profile and its history of outages, not just at the fact that “the wallet connected”.