Two coins that usually sit near the same dollar can still live in two different kinds of pool. Shared names on a review tab are a poor proof that you used the same pricing rule, because the protocol that created the pool is what prices the swap.
That mix-up is ordinary: people treat a familiar pair of names as one market, then later find the confirmation named a different protocol. Fees, votes, and later fills follow the protocol that created the pool, which is why copying ticker text from a browser tab can still leave you on a stableswap family.
General-purpose automated market makers and stableswap families are two product classes that search engines often collapse under one comparison. The useful split is which factory created the pair, which fee switch is on, and which governance token that project uses.
Uniswap is the general-purpose constant-product protocol in this comparison, and Curve is named here as a stableswap family Uniswap does not operate. BloFin lists UNI as UNI/USDT on spot and as UNIUSDT and UNIUSD perpetuals, which sit beside either decentralized exchange (DEX).
Uniswap's factory as the pair tell
Uniswap's tell is the permissionless factory that creates one pair contract per token pairing. Read that pair's hex before you treat two tickers that also appear on a stableswap screen as one market, because shared ticker text is still two pools if two protocols minted them.
The v2 architecture docs put that factory's purpose in one line: it creates one smart contract per unique token pair, and only one (source: Uniswap Docs, v2 architecture). That factory is Uniswap's, so a Curve-looking pool is a different contract even when the review screen shows the same two tickers.
Protocol fees on Uniswap are a later governance setting, a slice of swap fees that can feed UNI burns, and they sit on top of the pool fee liquidity providers already earned. Historic v2 pools charged a flat pool fee that compounded in reserves, and that LP line is a different switch from turning on protocol fees.
UNI is the token that votes those switches, an ERC-20 on Ethereum with governance rights, so a Curve screenshot is a different project's market.
Suppose you hold 40 UNI and open two review screens that both say USDC and DAI, one naming a Uniswap factory pair and the other naming a stableswap pool. The 40 UNI you already hold are the same ERC-20. The pool you are about to use is the factory that minted the pair, because shared ticker text is still two markets.
| Criterion | Uniswap | Curve (stableswap family) |
|---|---|---|
| Who creates the pair | Uniswap factory indexes pairs | A separate protocol |
| What the pool looks like | Two-token AMM reserves | Also reserves, different invariant |
| Pool fee on classic v2 | Flat pool fee into reserves | Off this page |
| Protocol fee | Governance setting, later votes | Off this page |
| Governance token | UNI, ERC-20 | Off this page |
| Near-peg pair | Still reprices on constant product | Named as stableswap family |
That table is a description of Uniswap-side architecture, starting with the factory that indexes pairs. The hex on the confirmation is the check you can actually run, because two review screens can repeat USDC and DAI while two protocols still minted two pools.
Two reserves and a different pricing rule
A Uniswap pool and a Curve pool can both hold two coins you already know, and a review screen can repeat the same ticker text, while your 40 UNI still move as ERC-20 UNI. The invariant that prices the swap is still the tell.
Uniswap liquidity pools are two token reserves in a contract, and that two-reserve picture is the shared work. How Uniswap AMMs work is the Uniswap pool picture across versions, without reteaching the full product walk.
Uniswap manages liquidity pools of two token reserves. When you swap one token for another, you trade against the pool's reserves, and the pool prices those tokens from the two balances (source: Uniswap Docs, How Uniswap Works). Generic AMM literacy sits in automated market makers.
Put two near-peg coins into a Uniswap constant-product pool and the pair still reprices when one reserve moves. Suppose one reserve of 70 USDC changes against 70 DAI. The product of the two balances still moves the price, because Uniswap treats those coins as ordinary tokens. Curve is named here as the stableswap family for assets that are supposed to stay close. Neither side wins that split by default.
Curve's StableSwap exchange uses a StableSwap invariant to trade stablecoins and other stable assets (source: Curve Docs, StableSwap overview). That sentence names the family. It is a family label.
Once Uniswap core is deployed, it keeps running as written, so a stableswap family existing beside Uniswap leaves those Uniswap pairs in place. Your 70 USDC / 70 DAI Uniswap pool can still reprice after a reserve move.
Gas is still the chain's fee token, so on Ethereum that is ETH even when the pool is USDC and DAI, and how Ethereum works is the chain picture.
Generic CEX versus DEX literacy sits in centralized versus decentralized exchanges, while the Uniswap-versus-Curve split stays on two AMM families. Why a DEX mid and a CEX last can disagree is a separate price story in DEX and CEX prices.
The useful check is small: copy the pair address from the confirmation, then ask whether that hex is a Uniswap factory pair. A mismatch means the screenshot was a different protocol even when both tabs said USDC and DAI.
Fees are the next Uniswap-side check, because the screenshot also hides which fee switch is on.
Pool fees and the protocol-fee switch
Every Uniswap swap pays a pool fee to liquidity providers, and a later protocol fee can take a portion of that fee toward UNI burns. The historic v2 pool fee of 0.30 percent is the LP line, a different setting from the protocol-fee switch Tally 100 executed on July 27, 2026.
Uniswap v2 charged a flat 0.30 percent fee that was added to pool reserves. After a December 2025 governance proposal, the same fees page still says protocol fees are active on all v2 pools and select v3 pools. It also says v4 fee-adapter flows can be enabled through governance (source: Uniswap Docs, Fees). Treat that page as a concept explainer that can lag executed votes.
Tally proposal 100 is Executed as of July 27, 2026. Protocol fees are live across all v2 and v3 pools on 11 chains, and the same text introduces a v4 system on a subset of v4 pools on those same chains (source: Tally, Uniswap proposal 100). The eleven-chain v2/v3 recap is a named list from that vote.
The 0.30 percent v2 pool fee is still the amount the classic pair charged traders before any protocol cut, and mixing those two numbers conflates the LP line with the protocol cut.
Uniswap v3 concentrated liquidity is the in-range fee-tier picture, named here. A v3 position can sit in a chosen fee tier and price range while classic v2 still uses the flat pool fee.
On Uniswap, the live setting is the executed fee vote plus the UNI burn path, and both can change again by governance, so treat current chain lists as current settings.
You can skip a stableswap screenshot and still use the fee split if you can name the fee on the screen. Name the pool's LP fee on the pair, or the protocol fee Uniswap governance turned on for named versions and chains. Suppose the confirmation shows the classic v2 LP line, and that figure is paid inside the swap. The protocol-fee switch is a later vote on named versions and chains.
UNI is the token that votes those settings, so the balance itself is the next split.
What a UNI balance actually governs
UNI is the Uniswap protocol's ERC-20 governance token, and holders are represented through DUNI. Protocol fees can burn UNI as a supply path, and that burn is a supply mechanism, so a stableswap fill of UNI does not mint a second Uniswap claim.
"UNI holders have no individual or pro-rata claim on protocol revenue; value accrual is mediated entirely through this burn mechanism and any other distribution mechanism governance may subsequently authorize" (source: Uniswap Docs, UNI token).
That sentence is Uniswap's: a stableswap fill of UNI leaves you with the same ERC-20, and it creates no second UNI and no Uniswap coupon. You can delegate and vote when the tokens sit in a signing wallet the Uniswap governor can read, while UNI left on an exchange ledger stays a venue line until you withdraw.
Suppose you already hold 40 UNI in a wallet from an earlier stableswap output, then later want to vote on a Uniswap fee proposal. The governor reads UNI at the proposal's start block for that wallet after delegation, with no DEX field on the ballot. A BloFin sub-account stays an exchange ledger line until you withdraw, because support cannot cast that vote for you.
Uniswap versus a centralized exchange, including who holds UNI after a BloFin fill, sits with Uniswap versus centralized exchanges. Use that parent when the other market is a venue book, and use the Uniswap-versus-Curve split when the other market is a stableswap family.
A UNI balance is a Uniswap governance position, and a Curve headline is a different project's story, so keep the token check and the factory check separate. Park the buy decision off this versus-Curve question with whether to invest in crypto as the generic frame.
A venue UNI product is still a third screen even when both DEXes show UNI, which is why the BloFin listings sit beside either DEX.
UNI/USDT and UNIUSDT beside either DEX
UNI/USDT is BloFin spot, UNIUSDT is a USDT-margined perpetual, and UNIUSD is a separate inverse SWAP. A Uniswap pool is two reserves in a factory pair, and a Curve-looking pool is still another market, so a fill on one leaves the other ledgers untouched.
BloFin has listed UNI/USDT on spot since January 15, 2024. Those listing dates are venue dates, separate from a Uniswap factory event and from a Curve pool creation.
BloFin lists two UNI perpetuals: UNIUSDT at up to 75x, listed January 12, 2023, and UNIUSD, an inverse contract settled in UNI, at up to 20x, listed June 27, 2025. Copying UNIUSDT's 75x onto UNIUSD mixes two listings, and copying either perpetual onto UNI/USDT mixes a derivative with spot.
You can hold UNI/USDT, a small UNIUSDT position, wallet UNI from a Uniswap pair, and wallet UNI from a stableswap-looking pool at the same time. The screens will all say UNI while the fills stay separate. Closing UNIUSDT credits or debits the venue, withdrawing UNI/USDT to a wallet is a transfer, and the pool swap is a later chain call.
| Product | What you hold | What that product settles |
|---|---|---|
| BloFin UNI/USDT | Venue spot balance | A listed cash-market fill |
| BloFin UNIUSDT | USDT-margined SWAP at 75x | Price exposure in quote |
| BloFin UNIUSD | Inverse SWAP at 20x, settle UNI | A second perpetual listing |
| Uniswap pair | Wallet UNI plus a factory pair | A Uniswap factory swap |
| Curve-looking pool | Wallet UNI plus a different protocol | A stableswap-family fill |
Copying 75x onto a pool mixes a derivative with two token reserves, and copying a Curve screenshot onto UNI/USDT mixes a stableswap fill with a listed book. Read the product on the screen you are about to confirm. That product check is the last split before the purpose test.
When the Uniswap vs Curve split applies
Use this Uniswap versus Curve split when you needed a general AMM versus a stableswap family, factory and UNI first, and use the parent CEX page when the other market was BloFin. Which comparison fits depends on that purpose, and there is no single winner.
Uniswap versus Sushi is the forked-AMM comparison, named here as a third comparison a searcher can park, because a Sushi pool is still a constant-product cousin.
If you wanted UNI in a Uniswap factory pair, you read the pair hex and pay chain gas, while UNI that only had to match a stableswap ticker can still sit off Uniswap's factory. A listed UNI/USDT fill with no chain call is BloFin, whose parent page owns that custody split.
Suppose you still hold 40 UNI after a stableswap-looking output, then route that same ERC-20 into a Uniswap pair on the same chain. The hop is a transfer of UNI from one protocol's output to Uniswap's factory pair, so sequence does not merge the protocols. You still have two markets, two fee settings, and one governance token that only Uniswap's governor reads as UNI. The stableswap-looking pool did not become a Uniswap pair because you reused the coins.
You can use both protocols in sequence, and that hop still merges none of the markets. If the other market was a centralized book, the parent page is the comparison that matches.
Keep the test short: which factory created the pair, which fee switch you are quoting, and whether the UNI in hand can vote on Uniswap. If the screenshot was a Curve deployment, treat it as the stableswap family and stop, and leave that project's LP runbook on that project's own docs.
Common questions about Uniswap vs Curve
If you paste the same 0x address into a Uniswap review and a Curve review, is that the same UNI pool?
That hex is your wallet, because Uniswap's v2 factory creates and indexes its own pairs while a Curve pool is a different deployer. Both screens can show UNI because UNI is one ERC-20, so you read the pair address on the confirmation. If the pair hex is a Uniswap factory pair you are on Uniswap, and if it is a Curve pool you are on the stableswap family, while the same UNI can exit either pool.
If you deposit UNI to BloFin after a Curve-looking swap, does BloFin credit a Uniswap fill?
The venue credits UNI when the asset arrives on the network and any memo the deposit form named, and it reads neither "Curve" nor "Uniswap" off the transfer. A screenshot of a Curve confirmation is a poor substitute for a BloFin UNI/USDT listing, so you confirm the token, the chain, and the memo, then send a small test. A wrong network can park the coins even when the ticker looks right.
If your UNI is still inside a Curve LP position, does Tally read that LP token as UNI?
The governor reads UNI balances it can see, and a Curve pool share is a different token from UNI, so leaving 40 UNI inside that position means Tally is looking past UNI in your signing wallet. Exit the position if you want those coins counted as UNI, then delegate before the proposal's start block, because the LP token is a pool share.
If a review app labels stableswap on a USDC/DAI pool, did Uniswap's factory create it?
The label is a UI mark on a screenshot. Uniswap's v2 factory creates one smart contract per unique token pair, and a stableswap badge leaves that contract unminted. You still copy the pair hex from the confirmation, and a Uniswap pair can hold USDC and DAI while remaining a Uniswap pair, so the label is a weak tell.
Does Tally 100's 11-chain v2/v3 list include Robinhood Chain?
Tally 100's eleven-chain v2/v3 recap omits Robinhood Chain, and Tally 99, executed the same calendar day, July 27, 2026, is the Robinhood v2/v3 expansion. That onchain vote covers v2 and v3 fees on Robinhood Chain (source: Tally, Uniswap proposal 99). v4 on Robinhood sits in Tally 100's subset, so count the executed text and skip adding a twelfth chain onto proposal 100.
If you are liquidated on UNIUSDT, does that close UNI sitting in a Curve pool?
UNIUSDT is a BloFin SWAP, and a Curve UNI pool is a pair contract, so liquidation on UNIUSDT is a venue engine event on that SWAP. It leaves UNI in a Curve pool and UNI in a Uniswap pair in whatever wallet still holds the ERC-20. The reverse is also true: a thin Curve pool can move your 40 UNI while UNIUSDT stays open, so you read each product's close path.
If you swap USDC for DAI on Uniswap, then swap that DAI on Curve, does the second hop use Uniswap's pair?
The first hop is Uniswap's pair after that fill, and the DAI you receive is ERC-20 DAI, so the second hop is whichever pool contract you sign next. A single wallet session leaves you free to leave Uniswap's factory, so you read two confirmations and two hexes. Sequence is a sequence, and shared ticker text on both screens still leaves two markets.
Does BloFin's UNI/USDT listing date tell you which Uniswap fee tier to use?
January 15, 2024 11:00 UTC is when this CEX spot market went live, and a Uniswap UNI/USDT pool still has a fee tier on a specific factory pair. The listing date leaves Uniswap fee tiers and Uniswap versions to the pair itself, so you read the pair's fee on the confirmation, then still match chain and pair hex.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated September 2026. Primary sources: Uniswap How Uniswap Works docs, Uniswap v2 architecture docs, Uniswap fees docs, Uniswap UNI token docs, Tally Uniswap proposal 100, Tally Uniswap proposal 99, and Curve's StableSwap overview. 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 volatility, smart-contract risk in pools, venue risk on an exchange balance, and the chance of losing funds to a lost seed, a fake token, or a lookalike pool. Nothing here is a recommendation to buy, sell, hold, or participate in any project. Do your own research, and consider speaking with a licensed professional before making financial decisions. BloFin does not provide investment advice.