Moving coins from a wallet you control looks finished once the address pastes cleanly and you confirm. The confirmation screen treats a valid-looking string as enough, so the coins leave as soon as the network includes the call.
The same address can exist on more than one network, and a cheaper-looking fee can pull you onto a chain the person expecting your coins is not watching. Their screen stays empty even though your wallet already shows a successful send.
Token transfers of this kind are signed ERC-20 moves: one network, one token contract, paid with that chain's native fee token. They sit beside pool swaps and exchange fills as a different action, because the call only moves a balance from one address to another on the chain you signed.
UNI is Uniswap's ERC-20 governance token, and sending it is that kind of transfer. The first check is whether the network label and the UNI contract match what the other side is watching.
Match the network and the UNI contract
A UNI send lands only where both the network and the token contract match. A paste can look complete and still credit Arbitrum UNI while the other person waits on Ethereum, because those two hexes are separate contracts that share a ticker.
Uniswap is a competing decentralized exchange (DEX), and UNI is its ERC-20 vote token, so what Uniswap is is the protocol picture. A send moves a UNI balance from one address to another on the chain the signer is showing.
The docs list the Ethereum UNI token, then a second table for other chains, under the heading for contract addresses on chains where the protocol fee is active (source: Uniswap Docs, UNI Token). Arbitrum One UNI is 0xFa7F8980b0f1E64A2062791cc3b0871572f1F7f0, while Ethereum UNI is a different hex: same ticker, different contract, so treat those two as the pair you can mix.
Suppose you copy a receive string the other person sent from an Ethereum signer, the string starts with 0x and looks complete, and your wallet is set to Arbitrum because the fee looks smaller. You send 25 UNI, the Arbitrum UNI leaves, and their Ethereum screen stays at zero, because the paste worked while the network was the miss.
| Network they are watching | UNI contract that has to arrive | Fee token for a later move |
|---|---|---|
| Ethereum | Ethereum UNI, a different hex from the Arbitrum contract | ETH on Ethereum |
| Arbitrum One | Arbitrum UNI at 0xFa7F8980b0f1E64A2062791cc3b0871572f1F7f0 |
ETH on Arbitrum |
That table is a match check, so a Bitcoin-only app will skip both lines, and a right ticker on the wrong chain is a different balance. Bridged UNI on Arbitrum is still UNI, and it appears as Ethereum UNI only after someone bridges it, which is a later step.
You can open the token line in your signer after the send and read the contract. If it is the Arbitrum hex and they are on Ethereum, you already know why their screen is empty, because matching letters in the ticker is the weak check while the network label plus that hex is the check that finishes the send.
If you are sending to a BloFin deposit string, the same rule holds. The withdrawal or send network has to be the network that deposit screen named. A cheaper-looking network in your wallet is a different path.
Hold on to one thing: a valid receive string is the start of a send. The network and the UNI contract still have to be the ones the other side is watching.
How to send UNI from a wallet
UNI moves when a signer you control calls the token contract's transfer on one network, and that network's fee token pays for the call, which is a signed ERC-20 move. It is a different action from a Uniswap pool swap and from a BloFin UNI/USDT book fill, and sending ETH is a different call again because ETH predates the ERC-20 interface.
EIP-20 is the token interface wallets reuse, and the standard provides basic functionality to transfer tokens and to approve a third party to spend them (source: EIP-20, Token Standard). The call that moves UNI is transfer, or transferFrom if a contract is moving UNI you already approved, so a 25 UNI send from your signer is the first of those while a swap in a pool is a different call.
ethereum.org states the same split: ERC-20 tokens are transferred using the transfer or transferFrom functions (source: ethereum.org, ERC-20 Token Standard). ETH is a native coin rather than an ERC-20, so a UNI send is a contract call, which is why the wallet shows UNI and a fee in the chain's native token at the same time.
Uniswap Labs is blunt about what happens after Confirm: transfers on the blockchain are permanent, so a confirmed send stays on the chain it used. The same page tells you to confirm that your wallet, address, or dapp supports the network you are sending the token on before you proceed (source: Uniswap Labs support, How to send tokens with the Uniswap Web app). The Send tab in that app is one way to build the call, and the signer still has to be on the matching network.
The two things to get right for UNI specifically are the contract address and the network, and the walkthrough below builds the call step by step. For transfers in general, see how to send and receive crypto.
Walk a UNI send in this order, and stop if a step fails. First ask which network the other person is actually watching, in their words. Confirm the UNI contract on that network, because Ethereum UNI and Arbitrum UNI are different hexes. Copy the receive string from inside their signer, or from their venue deposit screen for that same network. In the signer you control, select UNI on that same network, and check that the fee token is there. Send a small test, then wait until they say it showed on that network. Only then send the rest of the 25 UNI, or leave the rest where it sits.
On the Uniswap Web app, the Labs send article walks the clicks that build that call. Open the Uniswap Web app, connect the wallet that holds the UNI, and select Send. Open the token drop-down, select UNI, and enter the amount, or Max, then open the To field and paste the recipient's Uniswap username, 0x string, or ENS name. Select Send, read any first-time warning and Continue, then select Confirm send and confirm again in the wallet if the button spins. A pending icon appears once the send is submitted, and the notification opens the explorer record (source: Uniswap Labs support, How to send tokens with the Uniswap Web app). Stay on the network they named through every one of those clicks.
From a MetaMask extension, the path is the same match with different labels. Click Send on the homepage, select the network and UNI, paste the recipient address, enter the amount, and continue, then review the estimated network fees and the recipient and Confirm. The Activity tab shows the pending call, then Confirmed once the network includes it (source: MetaMask Help Center, How to send tokens from your MetaMask wallet). You need a sufficient UNI balance and enough of the network's native token to cover the fee.
Treat a Uniswap Swap click as a different list, because Swap trades UNI for another token in a pool while Send moves UNI to an address. If you only wanted to sell, you wanted Swap, and a send is extra.
A UNIUSDT or UNIUSD position is a different holding as well, because closing that product is how it exits. It stays a venue position until you flatten it, and it becomes a UNI transfer only after you hold spot UNI you can withdraw.
What matters here is the call: UNI transfer on the network they named, paid with that chain's fee token, after a test they can actually see.
How to receive UNI you can actually see
Receiving UNI means the coins land at an address you sign for, on the network you are watching, as the UNI contract you expected. A ticker in a search box is only a lookup and a chat string is only a message, which is why you copy the string from inside the signer you will use.
An Ethereum account that you sign for is controlled by anyone with the private keys, and it can receive, hold, and send ETH and tokens (source: ethereum.org, Ethereum accounts). The coins sit on that ledger, and the app is only a window, so if the window is pointed at the wrong chain a full UNI balance can look empty.
Open Receive inside the signer on the network you will watch, copy that string onto paper, and check the characters against the screen. Then send those characters to the other person on a channel you already use, skip a faster address from a helper chat, and skip a string found in a group.
On Ethereum the fee token is ETH, so gas fees have to be paid in ether, and the fee is paid whether a transaction succeeds or fails (source: ethereum.org, Gas and fees). You can see UNI that already arrived with zero ETH in the account, but you need ETH in that same account before you can send UNI back out. How to store UNI is the later page for that fee-token stall, because receiving only needs the window pointed at the right chain.
If you are receiving onto BloFin, open the UNI deposit screen and copy the string and network from that screen. Leave the network as the one the deposit screen named, even when a wallet offered a cheaper one. BloFin has listed UNI/USDT on spot since January 15, 2024. A UNI credit on this venue is a cash-market balance after a matching deposit. Treat the listing as a current setting.
Wait until the test shows, and if they sent 1 UNI as a test and your Ethereum signer still reads zero after a normal wait, say so before they send 24 more. An empty screen is a stop.
The idea to carry forward: receive is a string you copied from the place you will watch, on the network you will watch, plus a test that actually appeared there.
What a wrong-network UNI send actually did
A wrong-network UNI send usually succeeds, so the coins leave and sit on the chain you actually used, while the person watching a different chain sees nothing. That empty screen is a mismatch of labels.
If the destination was a venue deposit, the venue often will skip the credit. Funds sent on the wrong network stay out of the account because the networks are incompatible. Recovery depends on the pair, and a second send to the same string makes the mess worse (source: Bitget Support, How to Deal with Wrong Coin or Wrong Blockchain Deposits?). Open the venue's own recovery page if it has one, and skip paying a stranger who messages first.
If you sent the 25 UNI to an address the other person also controls, on another Ethereum Virtual Machine (EVM) chain, the coins may simply be out of view. MetaMask's help page says that tokens sent to a friend on the wrong EVM-compatible network are still there once they switch that wallet to the network you used (source: MetaMask Help Center, I sent crypto to the wrong place). That is a view change, a wallet switch.
Walk the miss as a split: you signed and the Arbitrum UNI left, they watched Ethereum and Ethereum UNI stayed put, and those two facts sit together so the loss is the mismatch.
Uniswap safety names protocol and venue kinds without a grade. A missing balance after a send is a network error until the labels match. It is a label miss.
If the address was a smart contract that skips holding UNI, recovery is something you should assume is closed. If the other chain is out of EVM compatibility with that 0x string, the coins may sit where nobody you know can sign. Stop at the test so the rest of the holding never takes that path.
Leave a second 25 UNI unsent. Name the chain the first send actually used, then decide whether they can switch a wallet they control, or whether a venue recovery form is the next step.
The point is the landing: the coins are on the chain you signed for, so recovery starts there.
Bridged UNI vs a second token
Bridged UNI is still UNI, and it uses a different contract on that chain, so it is the vote token as that chain records it. A send that used the bridged hex will stay hidden in an Ethereum-only window.
Your 25 UNI on Arbitrum is the Uniswap vote token as that chain records it, at 0xFa7F8980b0f1E64A2062791cc3b0871572f1F7f0, rather than Ethereum's genesis UNI, so someone watching only Ethereum is watching a different balance. Bridging later can move value across, if you use a route you already trust, because a send is a transfer on one chain rather than a bridge.
A look-alike UNI that appears on Ethereum as a new token line is a different problem, because that is a fake ticker on the same chain rather than a bridge, so leave that line untouched. Spend real UNI on a send you intended. The send check is the network you used, and the UNI contract that actually moved.
Uniswap on other chains is the later page for how deployments exist beyond Ethereum. The send check only needs one fact from that list, which is to pick the contract on the chain you are actually using, so leave a twelve-chain catalog for that later page.
Transactions that change Ethereum state have to be broadcast and included, because transactions that change the state of the EVM need to be broadcast to the whole network (source: ethereum.org, Transactions). Once that UNI transfer is in a finalized block, waiting leaves it on the chain it used, so switching the wallet view can reveal bridged UNI while it leaves the first send on Arbitrum.
If you still want them to hold Ethereum UNI, you need a new send on Ethereum, after you have Ethereum UNI to send, plus ETH for that fee. The Arbitrum 25 UNI stays on Arbitrum until you move it with a bridge or a send on that chain, and confirming the first send does not move them.
Keep the split short: bridged UNI is the same asset family on another hex, a fake ticker is a different asset that borrowed the name, and wrong-network is the first family sent to the wrong ledger.
A UNI send checklist
Before you confirm a UNI send, name the network, the UNI contract, and whether a test already showed, because the checks that follow are that last pass. Generic seed setup stays on the security pages already named.
MetaMask's send article is the fee reminder in wallet language: you need a sufficient token balance to send the token of your choice and to cover the network fee for the transaction. On many networks that fee is the native token (source: MetaMask Help Center, How to send tokens from your MetaMask wallet). UNI on the screen with zero fee token is a stall.
Use this list as the last pass. Name the network the other person is watching out loud, because Ethereum and Arbitrum are different ledgers. Confirm the UNI contract on that network, because Arbitrum UNI and Ethereum UNI are different hexes. Copy the receive string from inside their signer or from their matching venue deposit screen, then write it on paper. Keep the fee token in the same signer, on that same network. Send a tiny test and wait until they see it, then send more or stop.
Leave seed steps on what self-custody is, and type a recovery phrase only into the wallet you already control. Wallet setup and backup live on how to choose a crypto wallet.
If you still needed to buy the UNI first, how to buy UNI is the fill, and the UNI token is the ERC-20 those fills hold.
Stay on the venue, or hold the send, when the other person has yet to name a network, or the receive string came from chat rather than from inside their signer or deposit screen. Hold the send as well when the UNI contract on your screen is a different hex from the one they can watch, or your signer has UNI and zero fee token.
You still have 24 UNI on Ethereum after the test never appeared on their Ethereum window, so leave the 24 unsent. Name Arbitrum as the chain you used, tell them to switch if they control that address, and only then decide whether a bridge or a new Ethereum send is the next move. If they used a venue deposit, stop and they open that venue's own form.
Self-custody is the right fit when you want UNI you can sign and send without a withdrawal wait. It is the wrong next click when you are still treating a valid 0x string as enough. Leave the coins where they are until the network and the contract match.
You skip memorizing the list if you name the network, match the UNI contract, copy the string from the right screen, and test, because that sequence is the send.
Frequently asked questions
Can I send UNI out of a UNIUSDT position?
A USDT-margined UNI perpetual credits a price position, so you close it to exit, and a send form leaves that position as a derivative. Spot UNI/USDT is the venue credit you can withdraw, then send from a signer. If the screen shows isolated, cross, or a funding line, you are looking at a position rather than coins you can paste to someone.
If I paste an ENS name, can I skip the network check?
An ENS name still resolves to an address on the chain your wallet is showing. Labs Send will accept a username, a 0x string, or an ENS name, and the transfer is still permanent. If your wallet is on Arbitrum and they are watching Ethereum, a correct-looking name still moves Arbitrum UNI, so match the network first, then paste.
Does Arbitrum UNI vote on Ethereum GovernorBravo?
Bridged UNI is still UNI on that chain, and the Ethereum Governor watches Ethereum UNI at an address it can see. Arbitrum UNI at 0xFa7F8980b0f1E64A2062791cc3b0871572f1F7f0 casts that vote only after it sits on Ethereum as the genesis UNI. A send that landed on Arbitrum is a balance they can hold or send there, which is a local balance until a later bridge.
If they use BloFin, which network do I pick?
Pick the network on their UNI deposit screen, rather than a cheaper network in your wallet, and copy the string from that screen after they open it. A BloFin UNI/USDT credit appears only after a matching deposit, so if you send Arbitrum UNI to an Ethereum deposit string the venue line will stay empty. Ask them to confirm the network label before the test.
Can BloFin reverse a UNI send I already confirmed in a wallet?
Once the chain accepts the transfer, BloFin has no button that rolls it back, and Labs says those transfers are permanent. A venue can only help if the coins landed on a deposit address it controls, and even then recovery is a support request. If you sent to a signer you do not control, the send is done.
Do I need ETH on the chain the 25 UNI already landed on?
You need the matching fee token if you want to move that UNI again on that chain, because Ethereum UNI needs ETH on Ethereum and Arbitrum UNI needs ETH on Arbitrum. The fee token lives on the ledger where the UNI sits, so adding ETH on Ethereum leaves an Arbitrum send unpaid. Switch the window, add the matching fee token, then send a test.
Is Uniswap Send the same as a swap?
Send delivers UNI to a receive string, while Swap exchanges UNI inside a pool and leaves you holding a different coin. Picking the Send tab leaves the wallet's network as you set it, so an Arbitrum window still ships Arbitrum UNI. If you wanted them to hold Ethereum UNI, stay on Send after Ethereum is selected. Unwinding a swap later leaves the UNI you already shipped on the chain you used.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated September 2026. Primary sources include Uniswap docs on UNI contracts, Uniswap Labs support on sending tokens, EIP-20, ethereum.org on ERC-20, gas, accounts, and transactions, MetaMask send and wrong-network help, Bitget wrong-network deposit help, and BloFin's public spot instrument list. All facts independently verified against cited documentation current as of September 2026.
This article is educational and general in nature, not financial or investment advice. Cryptocurrencies like UNI carry real risks, including price swings, lost keys, wrong-network sends, venue failure, and protocol losses in pools. Nothing here is a recommendation to buy, sell, or hold any asset. Do your own research, and consider a licensed professional before making financial decisions. BloFin does not provide investment advice.