Overnight, two different failures can empty a token holding: a lost recovery phrase can wipe coins while the pools keep running, and a pool can lose value while the keys that signed the deposit stay safe.
People mix those failures into one storage question, because a hardware device leaves pool risk in place, and leaving coins on an exchange leaves a later fake-token send as a later problem if you then withdraw and start swapping.
Custody is who can move the coins tonight, while protocol risk is what those coins are doing in a pool or a vote, so hardware and software are a choice inside the signed home.
UNI is Uniswap's ERC-20 governance token, and you can leave it as a BloFin UNI/USDT spot balance, listed January 15, 2024, or hold it at an address you sign for. Storage is which of those two homes can still move the coins tomorrow, plus the fee token on the matching network.
What storage still needs besides UNI
A wallet that holds UNI still needs the chain's fee token and a view of the network where that UNI sits. UNI on the screen is enough to look at, and a later send still waits until you can pay the fee and until the app is looking at the matching chain.
On Ethereum the fee token is ETH, because Ether is the native cryptocurrency that powers the Ethereum network. It is used to pay transaction fees, known as gas, for using the network and the applications built on top of it (source: ethereum.org, What is ether (ETH)?). A BloFin UNI/USDT credit leaves that fee unspent, so the venue send happens on BloFin's side, and the later onchain send happens only after UNI sits in a signer that can also pay ETH.
An Ethereum account that you sign for can hold both, because it is controlled by anyone with the private keys and can receive, hold, and send ETH and tokens (source: ethereum.org, Ethereum accounts). UNI without ETH in that same account is a balance you can see and a send that waits, while ETH in a different account is a second send.
Suppose you withdraw 40 UNI to Ethereum and leave 0 ETH in that signer, so the wallet shows UNI while a small send to a second address you also control stays unrun. You have to add ETH first, wait until that ETH shows, then retry, because the 40 UNI stayed put and stayed a display until the fee token arrived.
The network view is the other stall: if the UNI landed on Ethereum and the wallet is set to another Uniswap deployment, the Ethereum UNI can look empty. That empty screen is proof the window is pointed at a different chain, rather than proof the coins vanished, so switch the network in the wallet, or look up the receive string on that chain's explorer, before you sign again.
Keep the fee token and UNI in the same signer you will actually use, because a hardware device that holds UNI but has no ETH on that account has the same stall, and moving ETH from a second address is its own send. How to send and receive crypto is the generic transfer page, and storage cares because a later UNI send waits for that fee.
If you are still gathering ETH, matching networks, and copying a receive string from inside the signer, the honest next step is to leave UNI on the venue a while longer.
Hold on to one thing: stored UNI is UNI plus the fee token on the network where that UNI actually sits.
How to move UNI off a venue
Moving UNI off BloFin is a withdrawal to an address you copy from inside the signer you will use. It is a connect click only later, and it is a Uniswap swap only later. Match the network on the withdrawal list to that signer, then send a small test first.
What Uniswap is names the protocol as a competing decentralized exchange (DEX). Connecting that site leaves a BloFin UNI/USDT line where it is. The coins move when BloFin sends them to an address the signer already shows.
Confirm the signer can hold Ethereum ERC-20 tokens before you paste anything, because a Bitcoin-only app will leave UNI unreceived (source: Uniswap Labs, How to Transfer Crypto from an Exchange to a Self-Custody Wallet). Open Receive inside the app you will sign with, copy the string from that screen, write those characters on paper, then paste into BloFin, because a helper chat that offers a faster address is a different string.
Walk the move in this order, and stop if a step fails:
- Open the signer you will actually use and copy the receive string from inside that app, rather than from a message.
- Write the characters on paper and check them against the screen before any paste.
- On BloFin, open UNI withdrawal and pick the same network the signer is showing.
- Send a tiny test amount, rather than the whole UNI/USDT line.
- Wait until the signer shows that test, and only then send more.
BloFin has listed UNI/USDT on spot since January 15, 2024. A UNI credit on this venue is a real cash-market balance until you withdraw. Treat the listing as a current setting, and re-check the withdrawal network against the wallet you opened today.
How to buy UNI is the venue-aware fill that creates that credit, and the steps here only move it after the fill.
A UNIUSDT or UNIUSD position is a different product, so closing a perpetual is how that product exits, and a UNI withdrawal still wants a spot balance.
If the test stays missing, you still have the rest of the venue line, which is the point of the test, so leave the rest on BloFin while the first amount is missing and leave a stranger unpaid to speed it up.
What matters here is the paste: the receive string from inside the signer, the matching network, and a test that actually shows before the rest of the balance moves.
Hardware and software for UNI keys
Hardware and software can both hold UNI you already sign for, because hardware keeps keys off the phone and software keeps keys in an app that sits on the net. Neither is the BloFin UNI/USDT credit, so pick by how you will sign.
Labs splits those two signer types in plain words: physical devices that keep assets offline, and software apps in a browser, phone, or desktop. Both can hold UNI if they support that ERC-20 on the network you used.
A hardware device is built so the keys stay in the chip. Ledger describes hot wallets, otherwise known as software wallets, as storing private keys online, which is the attack surface those devices are built to leave behind (source: Ledger, How Ledger Hardware Wallets (signers) Work). That claim is Ledger describing its own design, and it is a score of every phone wallet you might already use only if you treat it as one, while the hardware path keeps those keys in a physical chip away from the browser.
A software signer is faster to open, and it also sits on a device that is already online. Ledger's offline-key page says that using a crypto wallet directly on an internet-connected device, such as any hot wallet, leaves you open to malware (source: Ledger, An Offline Key Is The Only Key). Malware on that phone can target the keys, hardware leaves later risks in place, and you still have to read the device screen before you sign a send.
| Home | Where the UNI keys sit | What you can do overnight |
|---|---|---|
| BloFin UNI/USDT | Venue credit | Sell on that book without paying chain fees |
| Software signer | Keys in a phone or browser app | Sign a send if the fee token is there |
| Hardware signer | Keys in a device chip | Sign on the device, then broadcast |
That table is a description. What self-custody is is the category page for holding your own keys. How to choose a crypto wallet is the picker and backup page.
You can use hardware with a software window, because the device still holds the keys while the app only shows the address and ships the signed send.
The idea to carry forward: hardware and software is a choice inside the signed home. It leaves the venue credit as its own overnight, and it leaves a winner unpicked for every overnight.
Matching the network and the UNI contract
UNI is an ERC-20, so the wallet and the venue must agree on the network and on that token contract. A Bitcoin-only app will leave Ethereum UNI hidden, and a right ticker on the wrong chain is a different balance.
The ERC-20 standard describes fungible tokens: each unit of a given contract is the same type and value as another unit of that contract (source: ethereum.org, ERC-20 Token Standard). Fungible means one real UNI equals another real UNI on that same contract, while bridged UNI on another chain uses a different contract, so match the network label first.
Wallets and venues reuse that standard, because a standard interface allows any tokens on Ethereum to be reused by other applications, from wallets to decentralized exchanges (source: EIP-20, Token Standard). That is why one Ethereum address can show UNI, ETH, and other ERC-20 balances together, and it is also why a wrong-network paste can still look like a valid 0x string even when the format matches and the chain differs. Uniswap scams and fake tokens is the look-alike ticker page, and matching the contract after a test lands is the store check here.
Suppose you copy an Ethereum receive string and BloFin's UNI list also offers another network, then you pick the other network because the fee looks smaller. The test leaves BloFin while the Ethereum signer stays empty, so the coins sit on the network you picked, away from the phone you are staring at, and a later recovery ticket leaves those coins on that other network. Stop at the test and leave the rest on BloFin.
After a test lands, you can confirm the token contract in the signer or on that chain's explorer, because the name UNI is a label and the contract is the asset. A second UNI that appeared after a random airdrop is a different balance, so leave the real UNI unspent as a cleanup of a fake line, leave the fake line alone, and keep the receive string you already checked on paper.
If you later use Uniswap from that signer, the site still only sees the network the wallet is showing. Storage is already done when the test landed on the matching chain. The swap is a later click, and it still needs the fee token from the first section.
Keep the match as three checks: the network on the withdrawal, the network the signer is showing, and the UNI contract that actually arrived. Miss one, and the ticker on the screen is a different home than the one you meant.
Protocol risk and custody risk
A Uniswap pool can lose value while your keys stay safe, and a lost phrase can wipe UNI while the pools keep running. Custody risk is who can move the coins, and protocol risk is what those coins are doing in a pool or a vote.
Investor.gov names who sits in that third-party seat: third-party custodians include crypto exchanges and dedicated crypto asset custody providers (source: Investor.gov, Crypto Asset Custody Basics for Retail Investors).
A BloFin UNI/USDT line is third-party custody until you withdraw, while UNI in a signer you control is self-custody, and both can lose in different ways.
Uniswap pool risk is a different fork: if you put UNI into a pool, you hold a pool share or a position NFT, the keys still sit in the signer, and the pool can move against you. That is protocol risk, and it leaves the wallet as working and the venue as working. Uniswap safety names those protocol and venue kinds without a score.
Keep the two apart when you ask whether UNI is stored, because a hardware wallet leaves a pool loss in place. Leaving UNI on BloFin leaves a later hook or fake-token risk in place if you then withdraw into a signer and start swapping. Storage answers who holds the keys tonight, while Uniswap answers what those keys are allowed to touch.
You can store UNI in a signer and leave Uniswap unopened, which is a valid overnight, and you can also leave UNI on BloFin and leave keys unheld, which is a valid overnight too. The store purpose is the home: it leaves Uniswap exploit risk as a later question, and it leaves venue-failure risk as a later question.
If you want UNI you can vote with from that address, the coins have to sit in a signer the Governor can see. That is a use of stored UNI. If you only wanted a balance you can sell on UNI/USDT, the venue line already is the store.
The point is the split: fix custody as a home, then treat Uniswap pool, hook, and governance risk as a different question.
An overnight UNI storage checklist
Before you sleep on a UNI balance, name the home, the network, and whether a later send can pay its fee. The checks that follow are the store purpose for that night, and seed setup stays on the security pages already named.
Wallet providers leave custody of your funds with you, and they provide a window to see your assets on Ethereum and tools to manage them (source: ethereum.org, Ethereum wallets). A window is a second custodian only if you treat it as one, and a Uniswap pool share is a backup of that window only if you treat the pool as keys.
Use this list as the last pass:
- Name the home as venue UNI/USDT, software signer, or hardware signer. The UNI token is the ERC-20 balance those homes hold, so treat a Uniswap pool share as a pool position.
- If the home is BloFin, confirm the balance is UNI on the spot line, rather than a perpetual you would have to close.
- If the home is a signer, copy the receive string from inside that signer and keep the paper copy.
- Match the network on any withdrawal to the network the signer is showing.
- Keep the fee token in the same signer as the UNI, on that same network.
- Send a test, wait until it shows, then send more or stop.
- Leave seed steps on the self-custody and wallet picker pages already named, and leave a recovery phrase out of chat, cloud photos, or a support form. How to revoke token approvals is later hygiene if you connected a site.
Stay on the venue when any of these is still true: you have no signer you control, you have yet to copy the receive string from inside it, the withdrawal network disagrees, or the signer has UNI and no fee token. Stay when you only wanted a book you can sell without paying a chain fee.
Suppose you have 80 UNI on BloFin and a new hardware device with no ETH, so you leave the 80 UNI on Friday night. You add a small ETH amount to that account, confirm the receive string on paper, then send a tiny UNI test. If the device stays empty you still have the venue line, while if the test lands you can send more on a quiet day.
Self-custody is the right fit when you want UNI you can sign with, send without a withdrawal form, or keep off a venue book. It is the next step after you already know the receive string, already hold ETH, and already treat a Uniswap connect prompt as a later click, so leave the coins on the venue until those are true, then move a test.
Skip memorizing the list: name the home, match the network, keep the fee token, and test, because that is the store.
Frequently asked questions
If I add UNI to a pool from a hardware signer, did the UNI leave that device?
The UNI you deposited is now a pool share or position NFT in that same account, and the same keys still hold that share, so hardware stayed put while the asset changed. A later pool loss is protocol risk on that new token. If you wanted UNI you can sell on UNI/USDT, close the position first, then store the UNI as a venue credit or as coins in a signer.
Does a UNIUSDT position count as stored UNI?
A USDT-margined UNI perpetual credits a price position, and you close it to exit, while a withdrawal form leaves that position as a contract. Stored UNI is either a UNI/USDT spot credit you can withdraw, or UNI at an address you sign for. If the screen shows isolated, cross, or a funding line, you are looking at a price position rather than a store of coins.
If I leave UNI on BloFin tonight, do I need ETH in a wallet?
A venue UNI/USDT credit leaves ETH unspent overnight, and ETH is for a later onchain send after a withdrawal lands in a signer. You can add ETH to that signer on a quiet day, confirm the receive string, then move a UNI test. Buying ETH the same minute you withdraw the whole UNI line is how a UNI balance with 0 ETH happens.
Can a hardware wallet tell a fake UNI token from the real one?
The device signs for the account it holds, and it leaves every ticker that appears in a software window uncertified, so match the network and the UNI contract after a test lands. A look-alike name in the token list is still a separate contract. Leave that look-alike line untouched, and keep the receive string you already checked on paper.
If I lose the phone but still have the written backup, is the UNI gone?
The coins sit on the chain if that backup opens the same keys in a new official app, because the phone was a window. How to restore from a written backup is a security topic. If you never made a backup, UNI in that signer is out of reach. Venue UNI you never withdrew is still a BloFin line.
Can I keep some UNI on BloFin and some in a signer?
Those are two homes, so they need two checks. The venue line needs a spot UNI balance you can sell or withdraw, and the signer needs the matching network, the fee token, and a receive string copied from inside that app. A test on one home leaves the other unproved, so size each home as cash you can leave there.
Should I paste a UNI receive string from chat?
Copy the receive string from inside the signer you will use, write it on paper, then paste into the withdrawal form. A chat string can swap middle characters and still look like a 0x address. The test send is cheap only if you still have the rest of the balance on BloFin. If the test lands at an address you do not control, stop.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated September 2026. Primary sources include ethereum.org on ether, accounts, wallets, and ERC-20, EIP-20, Investor.gov crypto asset custody, Ledger pages on hardware signers and offline keys, the Uniswap Labs transfer post, and BloFin's public spot instrument endpoint. 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.