Platform reference

Where CoW Swap is available: verify the product and chain

Separate CoW contract deployment evidence from support for a particular interface, wallet and order type on that chain.

Check CoW support at the product and order-type level. An existing settlement contract establishes a deployment; it does not by itself guarantee that every feature in the CoW Swap interface works on the same chain.

The official deployment reference, checked September 24, 2026, includes BNB among networks with core contracts. It also lists networks including Ethereum, Gnosis, Arbitrum, Base, Avalanche, Optimism, Polygon, Ink, Linea and Plasma. This is deployment evidence, not a universal feature matrix.

Four separate checks

  1. Is the relevant protocol contract deployed on the intended chain?
  2. Does the current interface offer the chosen order type there?
  3. Can the connected account authorize that order?
  4. Is a usable quote available for the actual assets and amount?

Failure at any stage can make the planned trade unavailable. A logo or contract address alone cannot answer the remaining questions.

Advanced workflows need extra care

For example, the TWAP tutorial describes a Safe-based workflow. That requirement is distinct from ordinary wallet connectivity. Successful connection should not be presented as proof that the account can use every order product.

Do not copy an address without context

Even where deterministic deployment produces matching addresses across networks, verify the chain and role against the current reference. A settlement address and a token-spender address are different responsibilities.

For an integration or treasury procedure, preserve the date and exact product tested. For an individual trade, rely on the current supported flow and quote. This approach avoids both outdated claims that CoW is available only on its earliest networks and overbroad claims that all EVM chains behave identically.

Sources & verification (2)

Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.

  1. Core

    Documented core deployments, including BNB Chain. Deployment is distinct from support for every interface feature.

    https://docs.cow.fi/cow-protocol/reference/contracts/core
  2. TWAP orders

    Safe wallet required in documented workflow; scheduled parts and multisignature lifecycle. Numeric minimums conflict within source, omitted.

    https://docs.cow.fi/cow-protocol/tutorials/cow-swap/twap

Continue reading

Chain support is a matrix, not a marketing count Choosing a swap service for a smart-contract wallet