DEX Development for Chains, DeFi Protocols and Finance Teams
Protofire's DEX development gives chains, DeFi protocols and finance teams the contracts, pool design, swap front end and subgraph of a spot exchange. Your team runs the venue. Uniswap governance's list of v3 deployments names Protofire as the deployer on eight networks, recognized between May 2024 and April 2026.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Spot exchanges that Protofire builds and your team runs
Protofire's DEX development serves chains, DeFi protocols and finance teams that need a spot exchange. We deliver the contracts, the pool design, the subgraph and the swap front end. Your team runs the venue and holds the authorization it needs.
Once you have picked the code for your exchange, three questions follow. Does the code's license cover your use? Who decides that a Uniswap deployment is official? Does the venue need an authorization that you do not hold?
Who builds, approves and runs a DEX
Protofire builds the contracts, front end and indexing. Your team supplies the liquidity and runs the venue, and Uniswap governance decides whether a v3 deployment is official.
Exchange contracts and pools
Swap front end and analytics
Subgraph and price feeds
Liquidity
Venue operation
Official status
Contract ownership
Audit report
Fix review
License, official status and exchange rules for a DEX
Exchange code that you copy keeps its license, and the rules on who may run an exchange are separate from the code.
Uniswap's v3 code is open to copy, so recognition as an official deployment is a separate step. The Uniswap Accountability Committee's deployment guideline requires a front end "to be recognized as official". Uniswap's v4-core license file is BUSL 1.1 until a change date no later than 15 June 2027.
In the EU, operating a trading platform for crypto-assets means managing one or more multilateral systems (MiCA Article 3(1)(18)). Such a system brings together multiple third-party purchasing and selling interests in crypto-assets, or facilitates bringing them together. It does so in the system and in accordance with its rules, in a way that results in a contract.
MiCA bars a person from providing crypto-asset services in the Union, with two exceptions (Article 59(1)). The first is a person authorized as a crypto-asset service provider under Article 63. The second is a credit institution, investment firm or another listed institution allowed to provide those services under Article 60. For the routes to authorization, see our MiCA license routes guide.
In the US, a group of persons provides "a market place or facilities for bringing together purchasers and sellers of securities" under two conditions. The conditions are set out in 17 CFR 240.3b-16(a). First, the group brings together the orders for securities of multiple buyers and sellers. Second, it uses established, non-discretionary methods under which those orders interact and the buyers and sellers agree to the terms of a trade.
Your counsel decides whether your venue falls under either rule, and who operates the venue. Protofire holds no license and gives no legal opinion. The license, the official status and the authorization each need an answer before the first pool opens, because each answer changes the build.
Our record: Uniswap v3 deployments, Swarm Markets and CoW Protocol
Uniswap governance's official list of v3 deployments names Protofire as the deployer on Redstone, Zero, Cyber, Ink, Shape, Abstract, Flow and Stable.The eight deployments were recognized between May 2024 and April 2026.
The list is a record of deployments made. Each of the 8 entries reads "Deployer: Protofire" and gives its date of recognition. The Uniswap Accountability Committee's April 2025 report counted 7 deployments by Protofire. The list marks the front ends of Redstone, Cyber and Ink as "[CURRENTLY DEPRECATED]". Our case study states the status of each deployment.
A DEX core and subgraph for Swarm Markets
In 2021 Protofire built the DEX core (a Balancer fork) and the subgraph for Swarm Markets. We also contributed to dOTC. Swarm Markets was a BaFin-licensed DEX at launch, where only KYC-verified wallets trade. Swarm held the license and ran the KYC.
Uniswap's contracts repository records the Ink deployment
Pull request 153 in Uniswap's contracts repository records the Ink deployments registry. The pull request was opened and merged on 11 June 2026. The pull request's description lists "Adopted Protofire v2/v3 (Dec 2024, v3-on-Ink governance RFC) + canonical Permit2".
Front end, SDK and subgraph work for CoW Protocol
For CoW Protocol, Protofire contributed to the explorer front end and the SDK. We also integrated the batch viewer and worked on the subgraph, as the CoW case study describes.
What each Uniswap license file says
The license files of Uniswap's v2-core, v3-core and v4-core set three different terms, as the files read on 13 November 2026.The v3 change date has passed, so the v3 core has been GPL-2.0-or-later since 1 April 2023 at the latest. Protofire reads the license file of your codebase against your planned use before the first change to the code.
v2-core
License in the file: GNU General Public License v3, 29 June 2007
Change date in the file: None stated
v3-core
License in the file: BUSL 1.1, with uses listed at v3-core-license-grants.uniswap.eth
Change date in the file: The earlier of 1 April 2023 or a date set at v3-core-license-date.uniswap.eth, then GPL v2 or later
v4-core
License in the file: BUSL 1.1, with uses listed at v4-core-license-grants.uniswap.eth granted and a commercial license needed for other use
Change date in the file: The earlier of 15 June 2027 or a date set at v4-core-license-date.uniswap.eth, then MIT
What DEX development from Protofire gives you
A written model for your exchange before the first line of code
You know what you are building, and why, before any code is written. The choice is a constant-product pool, concentrated liquidity, a custom pool or a hook pool on Uniswap v4. Protofire also writes down the pairs and fee settings. At the same time, Protofire reads the license of the codebase you prefer against your use.
Exchange contracts on your chain
Your chain gets a working exchange. Protofire deploys the released Uniswap v3 and v2 contracts and verifies them on your explorer. Alternatively, we write pool contracts for your own design.
A swap front end, analytics pages and a subgraph
Traders get a swap interface, and your team gets pages that show pools and trades. Protofire builds both on Uniswap's v3 interface, with a routing API where the stack needs one. We also build the subgraph that indexes the pools and trades.
Price feeds and a threat model for the swap path
Pool logic that reads a price needs a price feed that is connected on purpose. Protofire connects price feeds to the pool. We also write a threat model for the swap path, and the model includes token behavior. Uniswap's v3 docs say fee-on-transfer tokens will not function with Uniswap's router contracts. With rebasing tokens, pool creation and swaps succeed, but liquidity providers bear the loss from a negative rebase.
Uniswap v4 pools and hooks
A pool can behave the way your market needs. Uniswap's docs describe hooks that run logic before or after a swap, or gate who adds or removes liquidity. The docs also describe hooks that apply dynamic fees or build a custom curve. Protofire designs the pool, writes the hook and deploys it.
A venue where only approved wallets trade
Issuers of tokenized assets can offer a market that only approved wallets can use. On your own contracts, Protofire builds the permission checks into the pool. The party that holds the license and runs the KYC keeps the allowlist. See also our pages on decentralized OTC trading and RWA issuers.
How a DEX build runs from license to handover
- Step 1
A written exchange model and a license check
You send the chain or product, the pairs and the codebase you have in mind. Protofire writes down the exchange model and the pool and fee settings. We also record what the codebase's license file says about your use. - Step 2
Contracts and tests
Protofire deploys the released Uniswap contracts, or writes your own pool contracts. We test those pool contracts against the swap-path failures in the threat model. - Step 3
Front end, indexing and price feeds
Protofire builds the swap interface and the analytics pages. We also build the subgraph and connect the price feeds. We build all four against the same pool addresses, so the pages show what the contracts do. - Step 4
An outside audit and the fixes
An audit firm that you pick reviews the contracts that hold funds. Protofire prepares the tagged commit and the audit scope, and fixes each finding. - Step 5
Launch scripts and handover
The pool initialization scripts run, and the venue opens. A canonical Uniswap v3 deployment follows the Uniswap Accountability Committee's guideline. Under that guideline, the deployment deploys the v3 and v2 contracts and verifies them on a block explorer native to your chain. Then the Uniswap DAO takes ownership of the contracts. A front end is integrated, and the public list records who deployed. On your own contracts, your Safe or timelock holds the owner and admin roles. Your Safe or timelock also holds the upgrader and pauser roles. Protofire keeps no role after launch.
How work with Protofire starts
To start work with Protofire, you send the chain or product, the pairs and the codebase you prefer.For your own contracts, you also name the Safe or timelock that will hold the roles.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
When a DEX build with Protofire does not fit
A DEX build with Protofire does not fit in three cases.
- Your venue needs an authorization that nobody on your side holds yet. That authorization comes first, and the build follows.
- You want a promise of volume or of official status. Uniswap governance decides recognition, and the market decides volume.
- You want a perpetual exchange, or your chain is not EVM. Perpetual exchanges have their own perp DEX page. A non-EVM chain needs its own proposal to Uniswap governance.
This grants authority solely to the Uniswap DAO to declare which v3 deployments are official, thereby preserving Uniswap's reputable brand.
FAQ
What is DEX development?
Who can deploy Uniswap v3 on a new chain, and does it become official?
What does a Uniswap v4 hook do, and what are its limits?
Do I need a license to run a DEX in the EU?
Who supplies liquidity, and who runs the venue after launch?
Which exchange model should I build?
Does an audit make a DEX safe?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
