Trading services and order controls
Sections ↑CoW Swap is a wallet-connected trading interface for CoW Protocol. Users specify the assets, quantities and conditions they will accept; competing solvers find a way to execute those instructions. Liquidity can come from matching opposite user orders, automated market makers, other aggregators or private market makers. The interface and the underlying settlement system have different roles.[1]
DefiLlama showed approximately US$3.217 billion of rolling 30-day routed swap volume on 20 October 2026. This measures trades routed through the aggregator, rather than turnover in a proprietary CoW liquidity pool. It is not directly comparable with leveraged perpetual notional or an exchange’s registered-user total.[37]
For a separate historical reach measure, CoW DAO reported 47,700 active wallets and 292,947 trades for April 2026. Wallets are not verified individual people, and those April figures should not be presented as current monthly users.[34]
Trading routes and instructions
| Route | Documented operation | Execution boundary |
|---|---|---|
| Ordinary swaps | A signed intent enters the order system; winning solver solutions settle on-chain. | Submission does not itself transfer the purchased token. Receipt follows successful settlement.Source 2 |
| Limit orders | The user selects a limit and validity period. Partial fills are the default; fill-or-kill can be selected. | A small remainder can stay unfilled when settling it is uneconomic.Source 5 |
| TWAP | One instruction produces smaller scheduled trades. | Price protection can leave a part unsold; later parts continue on their schedule.Source 27 |
| Conditional strategies | The programmatic framework supports custom conditions and grouped order management. | A developer capability is distinct from a ready-made control in every wallet or interface.Source 15 |
The standard auction compares solutions for directed token pairs. A fast-path order instead gives the winning quote provider a short exclusive opportunity to settle immediately. If that window ends without settlement, the order returns to the normal auction. Fast path requires an unchanged matching quote and opt-in; partially fillable, pre-signed and ERC-1271 smart-contract orders are excluded. The user’s limit still applies.[3]
A 30 September 2026 announcement extended TWAP placement, editing and cancellation to ordinary EVM wallets. The older tutorial still describes Safe setup and fallback-handler changes; those instructions should be read as the Safe-specific route, rather than a universal current wallet requirement.[27][6]
Order validity, size and cancellation
| Control | Practical consequence |
|---|---|
| Execution threshold | A limit price can be reached without a fill: execution also needs to cover the applicable network cost. The open-order panel distinguishes the limit from the current executable price.Source 5 |
| Cancellation | Off-chain cancellation is free but depends on processing. On-chain cancellation requires gas. Either can lose a race with a settlement already proceeding.Source 5 |
| Token compatibility | ERC-20 compatibility alone is insufficient. A usable quote and adequate liquidity are required; fee-on-transfer or other problematic tokens can be rejected.Source 11 |
| Minimum size | There is no established universal minimum across every network and order route. The older Safe TWAP guide lists US$1,000 on mainnet and US$5 on Gnosis, Arbitrum One and Base for that documented workflow.Source 6 |
Fees, execution costs and price improvement
Sections ↑CoW’s charging model combines network costs, protocol volume charges and a share of qualifying price improvement. An application integrating the protocol may add its own partner charge. These components should be read together with the quoted output; gasless order submission does not mean a cost-free trade.[32]
Published charging framework
| Component | Published basis | Scope |
|---|---|---|
| Standard volume fee | CIP-74 introduced 2 basis points, or 0.02%, of trade volume. | Pair-specific settings can differ.Source 30 |
| Reduced fee | The 3 February 2026 notice set 0.3 basis point, or 0.003%, for correlated pairs and reduced-fee tokens. | The applicable token classification and current quote matter.Source 31 |
| Price-improvement share | CIP-61 standardised a 50% share of qualifying improvement, with a 1% order-volume cap. | The reference differs for out-of-market limits and market or in-market orders.Source 32 |
| Partner charge | An integrating application chooses its own fee. | This is separate from CoW DAO’s share of that partner revenue.Source 32 |
| Network execution | Solvers recover execution costs through the trade economics. | An approval, wrapping transaction or on-chain cancellation can require separately paid gas.Source 4Source 7 |
CIP-74’s adopted discussion includes authority to vary the baseline by token pair between 0% and 0.05%, and a 1% total protocol-fee cap excluding partner fees. A 14 October 2026 fee-policy proposal remains labelled draft in the inspected forum. Its proposed wider ranges are not treated here as an implemented tariff.[30][33]
Fee illustration: US$10,000 of unchanged trade value incurs US$2 at 0.02%, or US$0.30 at 0.003%. These are volume-fee components only; they exclude improvement sharing, network costs, partner or bridge charges and market movement.[31]
A solver can improve execution by netting opposite orders, using deeper liquidity or reducing transaction overhead. The resulting improvement depends on the actual auction. It is not a guaranteed rebate, and the protocol’s quoted competitive advantages are not an independent test of every available venue.[8]
Wallet funding, bridging and recovery
Sections ↑Ordinary ERC-20 trading starts from the user’s wallet. An allowance authorises the vault relayer to move a specified token; it is not a bank deposit into a CoW account. The relayer separates that approval from the settlement contract’s execution logic. A remaining token allowance and an unfilled order are different permissions.[14]
Native tokens and unfinished orders
| Route | Asset handling | Exit or cost condition |
|---|---|---|
| Wrap then trade | Wrap the native token into its ERC-20 representation, then submit the swap. | Wrapping is an on-chain action with a gas cost; repeated wrapped-token trades use the normal intent route.Source 7 |
| Eth-flow | A contract combines native-token wrapping and order placement. | The initial transaction’s gas is not refunded merely because the trade fails.Source 7 |
| Expired Eth-flow | The automatic refund service returns unmatched ETH only under its documented eligibility conditions. | Orders below 2% slippage tolerance require manual recovery. The 2% criterion governs that service; it is not a recommended tolerance.Source 21 |
| Manual native recovery | The documented tool takes the creation transaction hash and generates an invalidation transaction. | It returns the unmatched portion. Previously executed trades are not unwound.Source 21 |
Cross-chain execution and recovery
| Stage | Documented treatment |
|---|---|
| Destination selection | Available networks and tokens depend on the source asset and bridge provider; the guide does not support bridging the same token between networks.Source 26 |
| Quote | The display separates swap minimum output, bridge cost and destination minimum. Estimated arrival comes from the bridge provider.Source 26 |
| Commitment | The bridge starts after the swap. Once the proxy submits the bridge deposit, the transfer cannot be cancelled through swap cancellation.Source 26 |
| Failed delivery | A provider refund may arrive in the user’s Account Proxy. Select the relevant proxy version and recover its token balance; provider policy governs timing.Source 26 |
The cited funding documentation describes crypto wallets, contract transactions and bridges. It does not establish a CoW-operated bank-transfer deposit, card purchase or fiat withdrawal facility. Token networks and destination addresses therefore define the documented funding route.[24]
Asset control, settlement and security history
Sections ↑Who controls each layer
| Layer | Documented authority |
|---|---|
| User wallet | The user signs trade parameters. The settlement checks order authenticity, limits and filled amounts before completing a trade.Source 12 |
| Token allowance | The vault relayer moves approved tokens as part of settlement. Approving a token does not grant arbitrary ownership of every asset in the wallet.Source 14 |
| Solver admission | A manager can add or remove solvers; the manager or proxy owner can change the manager. The authentication contract uses an upgradeable proxy.Source 13 |
| Custom actions | Hooks can request calls before or after a swap. The signed action can reach another contract and must be assessed with that contract’s permissions.Source 16 |
Off-chain intents and private settlement routing are designed to reduce front-running and sandwich opportunities. This protection concerns trade execution. It does not protect against a user signing a malicious wallet request on a compromised website or against every external contract used in a transaction.[23]
On 14 April 2026, the cow.fi domain was hijacked and visitors were shown a phishing interface. CIP-86 reports an estimated US$1.2 million of affected user assets. Its relief programme was discretionary and incident-specific, with eligibility verification rather than a standing insured-balance promise.[35]
CoW DAO’s April recap says the domain was recovered. KPK’s August H1 treasury review reports that the defence reserve funded victim reimbursements in June. Those sources document a recovery and payments; they do not establish that every claimed loss was paid or that equivalent relief is guaranteed after a future incident.[34][36]
The public contract repository supplies source code, deployment information and an audit directory. It also retains a warning that zero buy or sell amounts can allow repeated fee collection, and directs integrators to prevent such orders. This is a documented contract-use constraint, not a finding that the current CoW Swap interface creates those orders.[38]
Eligibility, wallets and data handling
Sections ↑The interface terms require legal capacity and compliance with applicable laws, sanctions and restricted-party rules. They do not provide a comprehensive affirmative list of eligible countries. Public technical access alone cannot settle a particular resident’s eligibility.[28]
Access and record boundaries
| Subject | Published scope |
|---|---|
| Wallets and devices | The documentation supports injected wallets, WalletConnect v2, Safe and compatible hardware-wallet routes. Mobile-wallet support does not imply identical controls in every wallet.Source 24 |
| Networks | The current SDK lists Ethereum, Gnosis, Arbitrum One, Base, Polygon, Avalanche, BNB, Linea, Plasma and Ink, plus Sepolia testnet. Integration support is distinct from every product being available on each network.Source 10 |
| Privacy | The policy describes IP and device logs, off-chain order-intent data and public settlement records. Public blockchain entries cannot be erased by deleting interface-held data.Source 29 |
The privacy policy excludes under-18 users and identifies CoW Hosting Limited as the BVI data controller. Data-rights requests can be sent to [email protected], with additional identity or wallet verification where required. That procedure concerns personal data; it cannot reverse a settled blockchain trade.[29]
Support, disputes and transaction records
Sections ↑Support and records
| Need | Route or documented information |
|---|---|
| Product help | The official documentation links the CoW Protocol Discord. No staffed response hours or authorised telephone dealing service were established in the inspected support material.Source 24 |
| Transaction tracing | CoW Explorer combines off-chain orders with on-chain settlement data. Search by order ID, wallet address or settlement transaction hash.Source 19 |
| Order history | Address views show buy/sell amounts, limits, surplus, creation time and status. Creation times follow the browser’s locale, so exported or compared records need timezone context.Source 20 |
| History completeness | Open, filled, expired, cancelled, partially filled and pre-signing states are distinct. A submitted order and an executed transaction should not be counted as the same event.Source 20 |
Contractual disputes first go to [email protected]. After 30 days from notification without amicable resolution, the terms specify ICC mediation; after 40 days from the mediation request without settlement, ICC arbitration follows unless another period is agreed. The stated seat is Tortola, BVI, in English. A sole arbitrator applies below US$250,000 of combined claims and counterclaims; otherwise three. The terms retain an individual small-claims carve-out. They also state a US$100 aggregate liability cap, subject to liabilities that applicable law cannot exclude. These are contractual provisions, not free statutory compensation.[28]
The privacy policy gives retention periods of 30 days for server logs unless security work requires longer, one year after execution or expiry for order-intent records, and 18 months after closure for support or research records. The order tools establish transaction visibility, not a complete tax calculation or indefinitely retained brokerage statement service.[29]
Permissions and legal scope
Sections ↑The researched documentation describes a software interface, a trading protocol and independent solvers. BVI incorporation identifies the interface company; it does not itself establish a financial-services permission. This review did not establish a current entity-specific exchange authorisation or statutory customer compensation entitlement. No such permission is inferred from protocol governance, open-source code or the availability of the website.[25]
Operator, governance and development
Sections ↑CoW Hosting Limited is the interface counterparty named in the current linked terms, which remain dated July 2025.[28]
The protocol and CoW DAO are described separately from the interface provider.[25]
The contract repository records the former Gnosis Protocol name. CoW DAO marked CoW Swap’s fifth anniversary in April 2026. The current business model centres on trading infrastructure, solver execution and protocol revenue; it should not be described as a conventional exchange holding a pooled customer cash account.[38][34]
Governance can change commercial policy. The October fee-iteration draft seeks continuing discretion over fee experiments, while retaining treasury reporting and allocation conditions. Its draft status matters: discussing a policy and implementing it are different stages.[33]
- Operator
- CoW Hosting Limited
- Exchange model
- Decentralised
- Service scope
- Wallet-signed swaps, limits, TWAP and supported bridge routes through CoW Protocol.
- Client types
- Retail clients
- Pricing publication
- Public pricing
- Other names
- CoWSwap; CoW Protocol
- Pricing scope
- Volume fees, improvement sharing and network costs; partner and route charges can differ.
- Funding scope
- Crypto wallets, wrapping and supported bridge routes.
- Custody and asset handling
- Wallet assets and signed allowances; native-token and bridge routes can involve user-specific contracts.
- Client eligibility
- Legal capacity, applicable law and sanctions restrictions.
- Support
- Official Discord and contractual legal contact.
- Authorisation and registration scope
- No current entity-specific financial permission established in this review.
Exchange metadata checked 20 Oct 2026Source 1Source 25Source 28Source 29Source 14Source 7Source 24Source 31
Covered contracting entities
CoW Hosting Limited
- Jurisdiction
- British Virgin Islands
- Covered services
- CoW Swap interface provider.
- Client and location scope
- Subject to interface terms.
Automation, integrations and referral conditions
Sections ↑Automation and API authority
| Facility | What it enables | Boundary |
|---|---|---|
| REST API | Request a quote, submit a signed order, inspect status, cancel and retrieve trades. | A market-data request is not authority to spend. Executable orders need the appropriate signature and token permissions.Source 9 |
| Streaming quote | The API can return quotes as solvers respond. | Closing the stream early can exclude slower responses and change price quality; a shorter timeout is not a guarantee of best execution.Source 9 |
| SDK wallet context | The integration stores its chain and account context. | Applications must update that state when the wallet or network changes.Source 10 |
| Programmatic framework | Conditions can express timed trading, price triggers or treasury actions. | The programmed rules govern execution; this is not evidence of an adviser or AI manager selecting investments.Source 15 |
| TWAP persistence | The contract defines separate validity windows for order parts. | A skipped part need not be recovered later. Closing a browser does not itself cancel a valid scheduled order.Source 22 |
Illustration: a TWAP instruction for 12 tokens in six equal parts schedules two tokens per part. If two parts expire unfilled and the other four fully execute, eight tokens trade and four remain unsold. This assumes equal parts and no replacement order; it is not a prediction of execution price or completion.[22]
Published referral pilot terms
| Condition | Documented parameter |
|---|---|
| Qualification | The FAQ requires a wallet new to direct CoW Swap trading, a referral activation and successful qualifying execution. Prior use through a partner integration does not alone disqualify it.Source 18 |
| Reward | The published setting pays 10 USDC to each side per US$250,000 qualifying milestone. The attribution window is up to 90 days; rewardable volume is capped at US$50 million per referred wallet.Source 17 |
| Payment | Weekly USDC batch payments normally use Ethereum; the payout wallet is fixed. Unpaid rewards can be withheld for review or disqualification.Source 18 |
| Term and budget | The stated pilot lasts six months from launch with a 500,000 USDC total incentive cap. Renewal or material expansion requires a new governance proposal.Source 17 |
| Tracking | Only qualifying executed volume counts. Dashboard data normally updates at 02:00 UTC daily and can lag; an expected reward is not a received payment.Source 18 |
The April recap dates the pilot’s launch to April 2026.[34]
The inspected current programme pages repeat the six-month term but do not establish an extension beyond that initial term. Their parameters are reported as published pilot conditions, rather than a promise that a newly referred October trade will earn a reward.[17]
Sources & further reading
- CoW Protocol overview CoW Protocol · Accessed 20 Oct 2026
- Order flow CoW Protocol · Accessed 20 Oct 2026
- Fast-path orders CoW Protocol · Accessed 20 Oct 2026
- Market swap guide CoW Protocol · Accessed 20 Oct 2026
- Limit order guide CoW Protocol · Accessed 20 Oct 2026
- Safe TWAP guide CoW Protocol · Accessed 20 Oct 2026
- Native token guide CoW Protocol · Accessed 20 Oct 2026
- Price improvement CoW Protocol · Accessed 20 Oct 2026
- API integration CoW Protocol · Accessed 20 Oct 2026
- CoW SDK CoW Protocol · Accessed 20 Oct 2026
- Supported tokens CoW Protocol · Accessed 20 Oct 2026
- Settlement contract CoW Protocol · Accessed 20 Oct 2026
- Solver allowlist CoW Protocol · Accessed 20 Oct 2026
- Vault relayer CoW Protocol · Accessed 20 Oct 2026
- Programmatic orders CoW Protocol · Accessed 20 Oct 2026
- CoW Hooks CoW Protocol · Accessed 20 Oct 2026
- Affiliate programme CoW Protocol · Accessed 20 Oct 2026
- Affiliate FAQ CoW Protocol · Accessed 20 Oct 2026
- CoW Explorer CoW Protocol · Accessed 20 Oct 2026
- Address order history CoW Protocol · Accessed 20 Oct 2026
- Eth-flow reference CoW Protocol · Accessed 20 Oct 2026
- TWAP contract CoW Protocol · Accessed 20 Oct 2026
- MEV protection CoW Protocol · Accessed 20 Oct 2026
- Supported wallets CoW Protocol · Accessed 20 Oct 2026
- Protocol and interface roles CoW Protocol · Accessed 20 Oct 2026
- Cross-chain swap guide CoW Protocol · Accessed 20 Oct 2026
- TWAP for EVM wallets CoW DAO · Accessed 20 Oct 2026
- Interface terms CoW Hosting Limited · Accessed 20 Oct 2026
- Privacy policy CoW Hosting Limited · Accessed 20 Oct 2026
- CIP-74 fee framework CoW DAO · Accessed 20 Oct 2026
- CIP-74 fee adjustment CoW DAO · Accessed 20 Oct 2026
- CIP-61 revenue framework CoW DAO · Accessed 20 Oct 2026
- Fee-policy iteration draft CoW DAO · Accessed 20 Oct 2026
- April 2026 recap CoW DAO · Accessed 20 Oct 2026
- CIP-86 incident grants CoW DAO · Accessed 20 Oct 2026
- H1 2026 treasury review KPK / CoW DAO forum · Accessed 20 Oct 2026
- CoWSwap activity snapshot DefiLlama · Accessed 20 Oct 2026
- CoW contract repository CoW Protocol / GitHub · Accessed 20 Oct 2026
This profile reports dated public information, including exchange-published services and terms. It does not independently test or guarantee trading, custody, pricing or withdrawals. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.
Report an error or submit an update