CoW Protocol: trade explorer, SDK, and subgraph
CoW Protocol settles trades through batch auctions and a competitive solver market rather than routing each swap straight to an AMM, which is how it protects users from front-running and sandwich attacks. That architecture only reaches traders through the tooling around it: a trade explorer to inspect batches and settlements, an SDK for integrators, and a subgraph that indexes on-chain activity for both.
Protofire engineered exactly those pieces: we contributed to the explorer front end and the SDK, integrated the batch viewer, and worked on the CoW Protocol subgraph on The Graph. We also supported the rebrand from Gnosis Protocol to CoW Protocol and ran QA across the trading interface. The subgraph is public at cowprotocol/subgraph.
“CoW Protocol does not match a trade the way a typical DEX does.”
Why CoW Protocol needed indexing and interface work, not another AMM
CoW Protocol does not match a trade the way a typical DEX does. Orders are collected and settled in batch auctions, where independent solvers compete to find the optimal execution, matching traders directly against each other (a coincidence of wants) before touching external liquidity.
That design suppresses the MEV that ordinary AMM swaps leak to front-runners. It also makes the protocol harder to read: a single settlement can clear many orders at once, so a trader who wants to confirm a fair price, or an integrator building on the protocol, needs a way to see batches, settlements, and per-token volume that a block explorer does not provide.
The scale made this concrete. By early 2022 the protocol's GPv2 settlement contract had cleared roughly $8B in sell volume across about 236,000 trades and 169,000 solved batches (on-chain figures reported by CoW Protocol). During the same period the project changed identity from Gnosis Protocol to CoW Protocol, which meant the trading interface, the explorer, and the surrounding developer tooling had to be reworked at once without breaking live trading.
The interface had to keep functioning for users mid-transition, the SDK had to stay stable for integrators, and the data layer feeding the explorer had to keep indexing settlements accurately through the change.
How Protofire contributed to CoW Swap's explorer, SDK, and subgraph
Protofire contributed to CoW Protocol's tooling over an open-ended engagement. On the front end, we worked on the trade explorer and integrated the batch viewer, so a settlement can be opened and read as the set of orders it actually cleared. We contributed to the SDK that integrators use to build against the protocol, provided QA across the trading interface, and supported the Gnosis Protocol to CoW Protocol rebrand across those surfaces.
The data layer is the publicly verifiable piece. The CoW Protocol subgraph on The Graph indexes the protocol's on-chain activity into queryable entities: settlements, trades, solvers, and per-token buy and sell volume. That includes attributing each settlement to its solver and calculating volume by token, so the explorer and other consumers can query trading activity without scanning the chain directly.
Protofire contributed to that subgraph; the work is public at cowprotocol/subgraph. Protofire did not author the CoW Protocol contracts or the solver market, which are the client's.