Understand major networks, virtual machines, token standards, gas fees, USDC, USDT and why choosing the correct network matters.
A virtual machine is the agreed runtime that executes program instructions consistently across network nodes. Select a network to compare its model.
The original EVM smart-contract network and settlement layer for a large ecosystem of applications and L2 networks.
Every validating node executes the same contract bytecode and reaches the same result. Compatible networks reuse the execution model and much of the tooling, not the same ledger state.
The blockchain processes the transaction, so the wallet normally needs that network's native fee asset or resource system as well as the stablecoin being moved.
ETH pays gas for sends, approvals, swaps and contract calls.
A USDT balance cannot pay BSC gas; keep a small BNB balance.
Transfers consume Bandwidth and smart-contract Energy; TRX may be burned when resources are insufficient.
SOL pays transaction fees and may also fund token-account setup.
POL is the native gas asset on Polygon PoS.
These Ethereum L2 networks use ETH for their network fees.
AVAX pays C-Chain gas for token and contract activity.
Bitcoin uses miner fees paid from BTC, not EVM-style gas.
The sender pays the on-chain fee. Merely viewing a balance also needs no transaction.
Connecting or signing a plain login message is usually off-chain, but still verify what you sign.
These change on-chain state and normally need the network's native fee asset or resources.
Bridges and claims are contract calls and may require fees on more than one network.
A relayer or application may sponsor the fee. The blockchain fee still exists.
The platform may update its own ledger instead, but service or withdrawal fees can still apply.
A sponsor or relayer may pay it for the user, an exchange may process an internal ledger movement, or TRON resources may cover part of the cost. Never assume a public-chain transfer will remain permanently free.
This directory shows mainnets currently listed by Circle for native USDC or by Tether for USDT. A listing does not mean every exchange, wallet or DApp supports deposits on that network.
A US-dollar-referenced stablecoin. Circle publishes native network support, exact contract or asset identifiers, reserve information and third-party assurance reports.
A separate US-dollar-referenced stablecoin with its own issuer, reserves, redemption terms, supported protocols and network-specific token forms.
USDC and USDT aim at a similar dollar value, but they are not the same asset. Compare the issuer, reserve and assurance disclosures, direct redemption rules, supported networks, liquidity at the service you use, and the exact token contract. Neither token removes network fees.
Tether currently lists USDT on BNB Smart Chain. The native-USDC contract list published by Circle does not currently list BNB Smart Chain. A BSC token labelled “USDC” may be bridged or third-party, so verify the exact contract and the official Stable Circle asset specification.
Each blockchain network maintains its own state, rules, validators and transaction history.
Ethereum, BNB Smart Chain, Polygon and other networks are separate systems. Even when two networks use similar address formats or are compatible with the Ethereum Virtual Machine, balances and contracts on one network are not automatically the same as balances and contracts on another.
This is why a wallet may show the same-looking public address across several EVM-compatible networks while the assets visible on each network are different.
When sending crypto, the network is part of the destination. Checking only the wallet address is not enough.
Wrong-network transfers are one of the most common beginner mistakes and can create difficult or impossible recovery situations.
BNB Smart Chain is an EVM-compatible blockchain. BNB is its native utility token and is used to pay transaction fees.
Because BNB Smart Chain is EVM-compatible, many Ethereum-style smart contracts and wallet tools can work with it. Tokens commonly use the BEP20 standard, which is closely related to ERC20-style token behaviour. opBNB is a separate BNB Chain Layer 2 designed for high throughput and ultra-low fees; it has its own chain state and must not be treated as the same network as BNB Smart Chain.
A wallet needs a small amount of BNB on BNB Smart Chain to pay gas when it sends tokens or interacts with smart contracts. Holding a BEP20 token such as a dollar-referenced asset does not remove the need for the network's native gas token.
Gas is paid to the network for processing the transaction. It is separate from the token amount being transferred.
A user can have enough of a token to participate in an application but still be unable to transact because the wallet has insufficient BNB for gas.
Before any BNB Smart Chain transaction, check both your token balance and your BNB balance.
Token standards give wallets and applications a consistent way to interact with fungible tokens.
ERC20 defines a common token interface on Ethereum, including functions for balances, transfers, allowances and approvals. BEP20 performs a similar role on BNB Smart Chain.
The approval mechanism matters for security. A token approval can authorise another smart contract or address to spend tokens up to an allowed amount on your behalf. Approval is not the same action as sending a token, but it can create future spending permission.
That is why you should understand which contract is requesting approval and how much permission is being granted before confirming.
Many Web3 applications require approvals before they can move a user's tokens. Malicious or excessive approvals can create risk.
A ticker such as USDC or USDT does not, by itself, prove the issuer, network or contract behind the asset.
USDC is issued by Circle and USDT is issued by Tether. Both target the value of the US dollar, but they are separate products with different issuers, reserve structures, redemption arrangements, supported networks and contract identifiers.
Circle describes USDC as fully backed by highly liquid cash and cash-equivalent assets and redeemable 1:1 for US dollars through eligible services, with reserve disclosures and third-party assurance reports. Tether publishes its own reserve information, transparency material and direct-customer redemption terms. Learners should compare current issuer disclosures rather than assuming that one dollar ticker is identical to another.
Circle issues native USDC on a defined list of supported blockchains and publishes official contract or asset addresses. Tether publishes its own supported-protocol list for USDT, including network-specific forms such as ERC20, TRC20, Solana tokens and TON Jettons. These lists can change and must be checked rather than assumed.
As of this Academy build, Circle's current native-USDC documentation does not list BNB Smart Chain as a native USDC network. Tokens labelled USDC on BNB Smart Chain may therefore represent bridged, pegged or third-party versions rather than Circle-native USDC. This is exactly why contract verification matters.
Tether's current documentation does list USDT on BNB Smart Chain and TRC20 USDT on TRON. That does not make an ERC20, BEP20 and TRC20 deposit interchangeable at an exchange: the sender and receiver must support the same exact network and token implementation.
Many other stablecoins exist. GSDC on a network where its official contract is supported is one example among them, not a special case for this course. Apply the same issuer, network, representation and contract-address checks to every stablecoin.
For Stable Circle, learners must use the exact BNB Smart Chain token contract officially specified by Stable Circle and should verify that contract independently before transferring or approving tokens. The Academy will not teach users to rely on a ticker symbol alone.
Two tokens can share a familiar name or symbol while representing different contracts and risk profiles.
Never add or send a token merely because its name says USDC. Verify the network and exact contract address from an authoritative source for the application you intend to use.
A token balance and the asset used to pay the network are usually two different things.
USDC and USDT are tokens on their selected networks. In an ordinary on-chain transfer they do not pay their own transaction fee. Ethereum, Base, Arbitrum and OP Mainnet commonly require ETH; BNB Smart Chain requires BNB; Solana requires SOL; Polygon PoS requires POL; and Avalanche C-Chain requires AVAX.
TRON describes its cost model through Bandwidth and Energy. Transactions consume Bandwidth, while smart-contract calls such as TRC20 transfers also consume Energy. Staked or delegated resources can cover costs; otherwise TRX may be burned. A free Bandwidth allowance is not a guarantee that every USDT transfer will cost nothing.
Receiving or holding a token normally requires no gas from the recipient. Sending, swapping, approving, bridging, claiming and other state-changing contract actions normally do require fees or resources.
A gasless experience usually means an application, sponsor or relayer pays the network fee for the user. An internal exchange transfer may instead update the exchange's private ledger. In both cases, do not confuse a zero fee shown to the user with the absence of an underlying network or service cost.
A learner can hold USDT or USDC yet still be unable to move it if the wallet has no native gas asset or adequate network resources.
For a planned transfer, write down the token, its network and the fee asset before opening SafePal. Example: USDT + BNB Smart Chain + BNB gas.
Never buy a so-called gas token from a link sent by a stranger. Confirm the network and acquire only the correct native asset through a trusted route.
A successful crypto transfer requires the sender, recipient, network and asset contract to be compatible.
A centralised exchange may support an asset on one network but not another. A wallet can support many networks, but the receiving service may accept only selected versions of an asset.
Before withdrawing from an exchange or sending between wallets, check the receiving platform's supported network. Do not assume that because two screens both display USDC, USDT or another ticker, the networks match.
A bridge adds contracts, operators or validators, liquidity and a destination representation of the asset. Use only the bridge reached through the network project's official documentation, confirm whether the destination token is native or wrapped, and verify that the receiving service supports that exact representation.
When in doubt, a small test transaction can reduce the amount at risk, although it does not replace checking the correct network and contract first.
Blockchain transactions are generally not reversible by a bank or central help desk after you send them.
Use a four-point check: asset, network, address, amount. For tokens, add a fifth check: contract address.
Most network mistakes are preventable with a short verification routine.
Common errors include selecting Ethereum when BNB Smart Chain was intended, assuming opBNB and BNB Smart Chain are the same network, sending to a service that does not support the chosen chain, or manually adding the wrong token contract.
Another common mistake is believing an asset is missing because a wallet does not display it. The blockchain may show the token correctly even when the wallet interface has not automatically added it. A blockchain explorer can help confirm what actually happened.
Do not respond to a missing-token problem by clicking random links or importing unknown contracts. Verify the transaction first, then the network, then the official token contract.
A calm verification sequence prevents one error from turning into a second, more serious security mistake.
The Academy uses authoritative primary sources wherever practical and converts them into beginner-friendly explanations.