Skip to content

CoW DAO CIPs — Solver Competition (reference index)

CoW Improvement Proposals (CIPs) that establish, modify, or discuss the solver competition: who can solve, how solutions are scored and ranked, how winners are chosen, rewards, fees, bonding, and enforcement/slashing. Captured 2026-06-18 for the BYOS exploration (BYOS RFP). Status/details summarized from forum search — open each link for authoritative text. The consolidated mechanics live in solver-auctions.md.

Auction & winner-selection mechanism

CIPTitleWhat it changes / discusses
CIP-67Moving from batch auction to the fair combinatorial auctionThe current core mechanism. Replaces single-winner batch auction with the FCA: per-directed-pair reference bids, filtering of underperforming batched bids, multiple winners. Higher throughput + stronger per-pair fairness guarantees. Most relevant to how BYOS bids win.
CIP-11Rules of the Solver Competition — status quo and updateFoundational competition rules: social-consensus (implicit) rules, global + local token-conservation constraints.
CIP-13Rules update: ban pennyingProhibits pennying (deliberately inflating reported scores expecting rewards to cover losses).
CIP-38Solver Computed Fees & Rank by SurplusSolvers compute their own "network fee" to cover gas; ranking moves to surplus-based.
CIP-72Aligning quoting and solving behavior of solversAddresses solvers giving over-optimistic quotes but not matching bids at solve time. Relevant to BYOS quote/solve consistency.

Rewards & fees

CIPTitleWhat it changes / discusses
CIP-20Auction model for solver rewardsEstablishes the auction-based (second-price) COW reward model for the competition winner.
CIP-34Testing Fee Models for CoW ProtocolEarly experimentation with protocol fee models.
CIP-36Adjusting and renewing solver rewards budgetRenews the rewards budget (committed 8M COW for the competition).
CIP-48Solver rewards budget renewal & update of bonding pool operationsBudget renewal + introduces the 15% service fee on positive COW rewards for designated/bonding-pool solvers.
CIP-57Solver rewards on all chainsExtends rewards across all operating chains (mainnet, Gnosis, Arbitrum, …).
CIP-74Align Solver Rewards with Protocol Revenue + volume-based feeReplaces fixed reward cap with a dynamic cap tied to protocol fees of the winning solution; adds a 2 bps unconditional volume fee. Directly shapes BYOS economics (the RFP's fee defaults to 0). See also the retrospective and the small-order second-price issue.
CIP-85Performance and Consistency RewardsCurrent reward shape: fixes reward budget at 50% of protocol revenue; adds consistency rewards for reliable participation.

Bonding, eligibility & enforcement

CIPTitleWhat it changes / discusses
CIP-7Allowing External SolversEstablishes bonding pools ($500k + 1.5M COW Safe owned by CoW DAO); pool creators signal liability to allow-list solver addresses. The mechanism BYOS itself is bonded under.
CIP-44Reduced bonding requirementsReduced bonding pool ($50k + 500k COW, scaling up) granting full calldata/submission control; still vouched under the DAO pool. A likely path for BYOS.
CIP-52EBBO (fairness) specs, reimbursement & escalationDefines EBBO violation certificates, reimbursement, and slashing escalation. Defines BYOS's liability surface.
CIP-55Slashing of the GlueX solverConcrete precedent: a solver slashed for misbehavior — illustrates real enforcement.
CIP-78Dissolve Sprinter Bonding PoolExample of the pool-dissolution process in practice.
CIP-DraftSimplifying the operations of the CoW DAO bonding poolOngoing discussion on bonding-pool operations.

Most load-bearing for BYOS

  1. CIP-67 — the FCA mechanism BYOS must win under.
  2. CIP-85 + CIP-74 — current reward/fee economics (the RFP says BYOS keeps 100% of rewards, fee defaults to 0).
  3. CIP-7 / CIP-44 — bonding pool BYOS operates under.
  4. CIP-52 — EBBO/slashing, i.e. BYOS's liability if a sub-solver's proposal harms users.
  5. CIP-72 — quote/solve consistency, relevant to proposal re-simulation.

Note: CIP numbers/status evolve. Re-check the forum's Governance and Closed Proposals categories for anything newer than the capture date.

This specification is normative. Where an implementation disagrees with it, the implementation is wrong.