When a website and a set of deployed contracts share a logo, an outage on the website gets read as a freeze of the market itself. You close a tab, the quote disappears, and it feels as if the pools stopped filling, even though another caller can still reach the same contracts if they can pay the chain fee.
The hard part is matching the name on the screen to the thing that actually has to keep working, because a software company can take an app offline while contracts that already live on a chain keep filling until the chain or the bytecode itself fails. A nonprofit that ran grants can wind down while those contracts stay where they were deployed, and a legal wrapper around holder votes can sit beside all three.
Interface software, deployed automated-market-maker contracts, a grants nonprofit, and a Wyoming association around voting are four parts that search pages and support articles often collapse under one word. Mixing them is how a dark homepage becomes a story that the protocol shut down.
Uniswap Labs ships the web app and the Uniswap Wallet, while the Uniswap protocol is the deployed pool contracts, the Uniswap Foundation ran grants, and DUNI is the Wyoming wrapper around Uniswap Governance. What Uniswap is names that protocol as the competing decentralized exchange (DEX) those four sit under.
What Uniswap Labs actually ships
Uniswap Labs is the company that ships the web app and wallet that sit on the protocol. Those products leave your tokens in the wallet you connected during a swap. The Terms last modified July 28, 2026 govern that software.
The legal name on those Terms is Universal Navigation Inc., doing business as Uniswap Labs, and the Products listed there start with the website-hosted interface at app.uniswap.org plus the Uniswap Wallet. That catalog is software.
Labs' Terms describe the hosted interface as one way to reach the protocol, and they say Labs leaves control and operation of every protocol version on every chain to the deployed contracts. That is why a Labs tab can go dark while a pair keeps filling (source: Uniswap Labs Terms of Service).
You open the web app, connect a signer, and review a 55 UNI swap, and the prompt is for Labs software talking to a router, then to a pool. If you close the tab, the pool balances stay where they were. If you use another legal front-end tomorrow, the same pair can still fill so long as the call is valid and you can pay gas. The logo on the tab is a software label.
Uniswap Labs is headquartered in New York City and contributes to ongoing protocol development as well as building products that help people access DeFi. That includes the Uniswap Web App and Wallet, as well as crypto infrastructure like the Uniswap Trading API and Unichain. The same page names the steward split: the protocol is governed by Uniswap Governance, led by UNI token holders, and stewarded by the Uniswap Foundation, an independent 501(c)(4) nonprofit (source: About Uniswap Labs).
The web app, wallet, and Trading API are Labs products, and Unichain is named there as Labs infrastructure rather than a fifth AMM version, so pool math sits in how Uniswap works while generic automated market maker (AMM) literacy sits in how AMMs work.
The Terms also say each Product is non-custodial, meaning Labs leaves custody, possession, and control of your digital assets with you. That is a statement about the interface company. It is a custody claim about Labs Products. Self-custody still means you hold the keys, which is the generic picture in what self-custody is.
What matters here is smaller than a company profile: Labs is the interface most people open, and the AMM is the set of contracts behind it. The next part is those contracts, because a company pause and a contract pause are different failures.
Why a dark app leaves the pools running
The Uniswap protocol is the deployed pool contracts, rather than a website Labs can switch off. Once those core contracts are live, a Terms page cannot pause them, so a dark app is an interface outage while the factory stays where it was deployed.
Support copy puts that in holder language, and immutable, persistent, non-upgradable smart contracts on the Ethereum blockchain define the Uniswap protocol. The protocol's services stay open for public use, and the support page describes access as open: anyone can swap, list a token, or provide liquidity, subject to gas and the token's own rules (source: Uniswap Labs support, How does the Uniswap protocol work?).
Developer docs say the same thing without a support-article voice: Uniswap is an automated market maker, a set of smart contracts that let anyone swap tokens, provide liquidity, or create new markets directly onchain. After deploy, core contracts stay as written, so a Terms page cannot pause them, reverse a fill, or rewrite protocol behavior after the fact. Governance can still turn on fee mechanics inside limits the code already exposes, which is a configuration knob the code already exposes (source: Uniswap Docs, How Uniswap Works).
Ethereum's upgrading page is why a blog cannot patch that pair. Immutability is treated there as necessary for trustlessness, decentralization, and security of smart contracts, with the drawback that a later patch is hard. The same page then walks proxy patterns, where a storage contract delegates to new logic, which is a built hatch, and Uniswap's core pairs skipped that hatch. If a pair was deployed without a proxy, you wait in vain for a silent patch from Labs (source: ethereum.org, Upgrading smart contracts).
Ethereum smart contracts is the generic picture of code that sits onchain, and smart-contract upgradability is the generic picture of those proxy hatches. Uniswap's core pools are the case where the hatch was left out of the product, so a new version can ship beside an old pair while the old pair keeps the old code.
Suppose the Labs tab fails to load while you still have 55 UNI in a signer you control. You can point another interface at the same pair, or encode the call yourself, if you can pay the chain's fee token. On Ethereum that fee token is ETH even when the pool is USDT and UNI, which is the gas picture in how Ethereum works.
Labs software is one caller among many, so the next named part is the nonprofit that sat beside that work, because grants and products are easy to flatten into one staff photo.
Where Foundation grants sit beside Labs software
The Uniswap Foundation is an independent nonprofit that ran grants and governance programs. It is distinct from Labs, and it is distinct from the pool factory. After UNIfication, most of that staff moved toward Labs, with a lean grants team remaining, then a planned close once the remaining grants budget is deployed.
About Labs already called the Foundation an independent 501(c)(4) nonprofit that stewards governance beside UNI holders, and that steward line is the starting split. The Foundation's own UNIfication post then names the staff move. The majority of the Uniswap Foundation team and its ongoing initiatives are expected to transition to Uniswap Labs, with a lean team remaining at the Foundation to manage continued grants administration. The Foundation will deploy the remaining about $100 million grants budget consistent with its mission, after which it will close operations. Those figures are the Foundation's own remaining-budget number (source: Uniswap Foundation, UNIfication: Uniswap's Next Era).
A later Foundation finance note on the governance forum restates the split after the vote. Most Foundation staff transitioned to Labs, which absorbed the majority of the work (protocol stewardship, ecosystem support, developer relations) that was previously handled under the Foundation. The Foundation retains a small, dedicated team focused on grant programs, and the same note says the Foundation plans to fund that remaining desk from assets already on its side. A remaining grants desk is still a nonprofit program (source: Uniswap Governance, Uniswap Foundation Summary FY 2025 Financials).
You can read a grant announcement and think you just watched Uniswap ship a product, but a grant is money and a program while a Labs release is software. A pool deploy is bytecode, so those three can share a blog week and still be three named parts. Flattening them is how a grants wind-down gets read as Uniswap shutting down.
The Foundation's remaining purpose, as those two posts write it, is to finish grants administration from existing assets, while Labs keeps shipping the interface and contributing to protocol work. UNI holders still vote, and the pools still sit where they were deployed. UNI governance is the later page for what a passed vote can change. Grants are distinct from the AMM, and they are distinct from Labs Terms, so the idea to carry forward is the remaining desk. If the Foundation later closes after that budget is deployed, that close is a nonprofit wind-down. v2 pairs stay where they were deployed. The next named part is DUNI, because a legal wrapper is the fourth name people paste onto the same logo.
What DUNI wraps for UNI holders
DUNI is the Wyoming legal wrapper around Uniswap Governance, rather than a share of pool income, and UNI holders are represented through DUNI while they still lack an individual or pro-rata claim on protocol revenue. Association paperwork is a later legal page.
In August 2025, the Uniswap Foundation proposed that Uniswap Governance adopt a Wyoming-registered Decentralized Unincorporated Nonprofit Association (DUNA) as the legal structure for the Uniswap Governance protocol, and that entity is called DUNI. The same overview says the governance process stayed the same. Membership is hold UNI and engage in Uniswap Governance, for example by delegating, posting, or voting. That membership line names no minimum UNI amount (source: Uniswap Docs, Governance overview).
The UNI token is the ERC-20 vote token that line is talking about, and the UNI docs state that holders have governance rights and are represented through DUNI. Value accrual is mediated entirely through the burn mechanism and any other distribution mechanism governance may subsequently authorize, so a burn is a supply event (source: Uniswap Docs, UNI Token).
You screenshot a fee-burn and think 55 UNI now pays you like a stock, but fees can be collected and later released only against a UNI burn, which is a supply event. The mechanism page is the fee switch and UNI burns, and holding UNI is distinct from a pro-rata invoice against TokenJar.
DUNI is also distinct from Labs, even when Labs sits under a services agreement with that wrapper, which still leaves four names. A holder who needs the legal structure, tax posture, or association agreement should open DUNI's legal structure. August 2025 is the proposal month on the docs, and as of September 9, 2025, Uniswap Governance adopted a Wyoming-registered Decentralized Unincorporated Nonprofit Association (DUNA) as the legal structure for the Uniswap Governance Protocol. Those are two dates, rather than one calendar day (source: DUNI info board, Welcome to DUNI).
Wyoming is a registration fact. A DUNA is an association. If you never delegate and never post, skip the assumption that the membership sentence already includes you, because the docs example is hold and participate, including a forum post.
Hold on to one thing: DUNI wraps governance so it can sign in the offchain world, and it leaves UNI as a vote token. The next section puts the four names on one table, because a versus title still needs a description grid.
How one Uniswap name covers four parts
Uniswap is one word covering four purposes, and the table below describes those purposes. Labs ships the interface, the protocol holds the pools, the Foundation ran grants, and DUNI wraps governance, with every named part matching a different task.
You can keep using the same ticker on a screen and still be pointing at a different part, because a Labs outage is a Product outage while a pool outage would be a chain or contract failure. A grants pause is a nonprofit program, and a DUNI filing is a wrapper event, so treating those as one Uniswap-down banner is the mix to keep apart.
The table is a description of parts, and the shared name is the only thing every named part has in common.
| Named part | What it is | What you can do with it | What sits elsewhere |
|---|---|---|---|
| Labs | Interface company | Open the web app or wallet | The pool factory |
| Protocol | Deployed AMM contracts | Swap or LP against reserves | A Terms of Service |
| Foundation | Independent nonprofit | Read a grant program | Labs, or the AMM |
| DUNI | Wyoming governance wrapper | Vote or delegate as a member | A fee dividend |
Read across the table as a description: if you want a quote on a phone, you want Labs software or another front-end, and if you want the pair to exist without that phone, you want the protocol. If you want ecosystem funding history, you want the Foundation desk, and if you want a vote that a Governor can see, you want UNI in a signer plus DUNI's membership line.
A centralized venue is a fifth route, and it sits outside the four Uniswap parts. The generic split lives in centralized versus decentralized exchanges. Your Uniswap fill is the DEX version of that split, and Uniswap is a competing DEX, so a BloFin UNI/USDT fill is a venue book credit, outside those four Uniswap parts.
You can skip memorizing the grant budget or the Terms filename, because the four named parts are what travels, and the last section is which one to reach for when the logo is the same and the purpose is different.
Matching the part you opened to the thing you wanted
Pick the named part that matches the purpose, then stop collapsing the logo. If you want a swap screen, you want an interface, and if you want the pair to keep running after that screen dies, you want the protocol. Grants, votes, and venue credits are other purposes.
Use this as a check:
- Website, wallet, Trading API, or a Labs Terms clause: Uniswap Labs.
- Pool balances, a swap against reserves, or whether anyone can call this: the protocol.
- Grant program, remaining nonprofit desk, or a Foundation finance post: the Foundation.
- Wyoming wrapper, membership, or representation through DUNI: DUNI, with the legal page for depth.
- UNI as a vote token in a signer: a Governor-visible balance, then governance.
- UNI as a book credit on BloFin: a venue balance, rather than DUNI membership.
BloFin has listed UNI/USDT on spot since January 15, 2024. That date is a venue listing date, which leaves DUNI membership and pool deployment as separate facts. Closing that balance later flattens a book credit, and it leaves a pair you never called still running.
If the purpose is whether this still works after Labs disappears from your bookmarks, the protocol line is the one that answers, because other people can still encode a legal call. You still need gas, the right token contracts, and a signer set to that network. If the purpose is whether a fee-burn screenshot means you get paid from fees, the DUNI line plus the missing pro-rata claim is the answer. If the purpose is who wrote the app you just opened, the Labs line is the answer, including Universal Navigation Inc as the signer on the Terms.
A yes-or-no title would have asked whether Labs is the protocol, and the honest answer depends on which purpose you brought. There is no single winner across swap, grant, vote, and custody, so match the named part and then use the matching page for depth.
Frequently asked questions
Is Uniswap Labs the same company as Universal Navigation Inc.?
Yes. The last-modified date on the Labs Terms of Service is July 28, 2026, and the Agreement is signed by Universal Navigation Inc, doing business as Uniswap Labs. The Products listed there include the hosted interface at app.uniswap.org and the Uniswap Wallet, and that corporate signer is how the interface company contracts. It is distinct from a second protocol, and it is distinct from the Foundation's 501(c)(4), so read the d/b/a line as a company tell.
If I call a Uniswap pool from another front-end, do Labs Terms still bind that call?
Labs Terms attach when you use Labs Products, rather than when you send a valid call from some other interface you already trust. A third-party front-end has its own terms, if it publishes any, including its own downtime and routing bugs. Geographic access limits on a token inside Labs' app are interface or token-issuer rules. You still owe gas and the right token contracts on that chain. The Agreement stays with Labs Products.
If I accept Labs Terms of Service, did I join DUNI?
Labs Terms attach to Labs Products, while DUNI membership in the docs is holding UNI and taking part in Uniswap governance. Clicking through an app agreement is distinct from a Governor vote, a delegation, and a DUNI filing. You can use the Labs app under those terms and still skip Bravo entirely, and you can also participate on Bravo from a signer you control while leaving that app closed, so those two routes leave each other alone.
Did UNIfication turn the Foundation into Labs?
UNIfication moved people and programs, and it left the 501(c)(4) as its own nonprofit beside Universal Navigation Inc rather than filing a merger that folded one into the other. The FY 2025 financials note still describes a remaining grants desk funded from assets already on the Foundation side. A staff move is distinct from a merger of the pool contracts into a company, and it is distinct from a close of every grant on the same day.
If I hold UNI and skip every vote, does that already make me a DUNI member?
Membership in the overview is hold UNI and take part, and the same page says DUNI skips collecting, storing, or reporting member data, while personal identity disclosure stays optional. A ticker sitting in a wallet that never posted, delegated, or voted sits outside the participate example. This is distinct from a tax opinion and from a KYC promise.
Is the Uniswap Trading API the Uniswap protocol?
About Uniswap Labs lists the Trading API with the web app, the wallet, and Unichain as Labs products and infrastructure, while the protocol is the pool contracts those products can call. An API key, a hosted quote, and a router path are software around the AMM, and they can fail while the pair still sits onchain. Treat an API status page as a software outage, and treat a pool as onchain inventory.
If a grant-funded team stops shipping, can the Foundation pull that team's live Uniswap pair?
A grants desk can stop future payments, and it leaves an already-deployed pair's bytecode in place even if a recipient missed a milestone. Core Uniswap contracts stay as written after deploy, so the Foundation's remaining budget is a nonprofit operations story and a paused grant is distinct from a factory pause. If you used that pair, your position still points at that pair's code until you exit it yourself.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated September 2026. Primary sources include the Uniswap Labs Terms of Service, About Uniswap Labs, Labs' How does the Uniswap protocol work page, Uniswap Docs on How Uniswap Works, Governance overview, and the UNI token, the Uniswap Foundation UNIfication post, the Foundation FY 2025 financials note, the DUNI info board, ethereum.org upgrading docs, 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, legal, or investment advice. Cryptocurrencies like UNI carry real risks, including price volatility, smart-contract risk in pools, interface and unofficial-front-end risk, venue risk on an exchange balance, and the chance of losing funds. 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.