Bleu × CoW: Year 3 Retrospective

Three years ago, CoW approved Bleu’s first grant. Since then, we’ve become long-term core contributors, shipping initiatives across product, engineering, developer infrastructure, and ecosystem growth.

A few highlights from our first two years show the range of that work. We built the first production interface for CoW AMM, helping attract its first deposits, shape the initial product experience, and validate the concept with real users.

For builders, we helped turn the community-built Python and Rust SDKs into usable, open-source libraries. cow-py has already generated $18M+ in volume from 8,800 orders across six chains and surpassed 27,000 PyPI downloads.

We’ve also helped make CoW’s value tangible to a wider audience. Have I Been MEV’d? brought prominent Ethereum figures into the conversation by showing how much their wallets had lost to MEV.

Year three: shipping core infrastructure

Over the past year, our work moved closer to CoW’s core product, developer environment, and solver competition.

Making CoW easier to build and test

We made the CoW Playground fully usable offline, packaging a local chain, liquidity sources, protocol contracts, and end-to-end trading scenarios into a reproducible development environment.

We then added a performance-testing layer with configurable load generation, benchmarks, test scenarios, and Grafana dashboards. Engineers can now test both correctness and performance.

A more modern frontend foundation

Last year, CoW Swap’s frontend stack was still tied to old EVM packages like Ethers.js v5 and Web3React. We replaced it with Viem, Wagmi, and Reown, preserving existing wallet support while removing a significant amount of technical debt.

The migration now ships in CoW Swap releases and provides a stronger foundation for wallet connectivity, mobile support, and new chains.

Programmatic orders, live in production

We built the Programmatic Orders API to connect conditional-order generators with their individual order parts, execution status, and actual EOA owners.

Today, it powers the discovery layer behind TWAP orders for regular wallets on CoW Swap. Seeing grant-funded infrastructure become part of a major production feature—and help open one of CoW’s most powerful order types beyond Safe users—is exactly the kind of impact we aim for.

BYOS: opening the solver competition

Our biggest focus today is Bring Your Own Solver.

BYOS creates a simpler path for protocols, market makers, and independent builders to submit proposals for individual orders without taking on all the legal, bonding, and operational overhead of becoming a full solver.

It is already integrated into the BNB staging competition, sub-solvers have settled staging orders, and external builders have begun integrating. We believe BYOS can become one of our most meaningful contributions to CoW: bringing new liquidity, strategies, and participants directly into the solver competition.

Still building with the herd

Three years in, we’re proud of how this collaboration has evolved. Thank you to the grants committee, core team, reviewers, and wider CoWmunity who have challenged, trusted, and built alongside us.

Moooo :cow_face::blue_heart:

5 Likes

Congrats on three years, bleu. Fun to see it all in one place. Grants funded that keeps ending up in the product is the best outcome we can ask for.

Looking forward to seeing BYOS on mainnet. Thanks to the whole team :cow_face:

2 Likes

One more update: we’re currently updating our stop loss app for safe apps to any EOAs, using the same contracts that TWAP for EOA uses. We want launch it soon and make sure all CoW users have access to MEV protected stop loss orders. Test it here: https://cow.airrescue.bleu.builders/

2 Likes

Feature Request: Add a Limit Price Option to Stop-Loss Orders

The upcoming stop-loss order feature looks great! One thing I think would make it much more flexible is adding a separate limit price alongside the trigger price.

Currently, the design includes a trigger price, but it seems to be missing an option to specify the actual execution limit price.

How it could work

For example, suppose I want to sell AAVE:

  • Sell amount: 100 AAVE

  • Trigger price: $140

  • Limit price: $125

When the market price reaches $140, the stop-loss order would activate and submit a sell limit order at $125.

This would give users more control over execution. They could set the trigger price to determine when the order activates, while independently choosing the minimum price they are willing to accept.

Why this would be useful

  • Separate activation and execution: The trigger price determines when the order activates, while the limit price determines the minimum acceptable selling price.

  • More flexibility: Users could trigger an order at $140 but allow execution at $140, $135, $125, or another chosen price.

  • Better control over slippage: A limit price would prevent the order from executing below the user’s chosen price, although it would not guarantee execution.

  • Different trading strategies: Some users may want to execute immediately after triggering, while others may prefer to set a more conservative limit and accept the risk of the order not filling.

Ideally, the UI could include a separate “Limit Price” field below the trigger price, with an option to use the trigger price as the default limit price.

I think this would make the stop-loss feature significantly more powerful while keeping the interface intuitive.

1 Like

@karolak Thanks for the feedback. Actually this is a feature that already exists. If you do the math you will see that the “receive at least” amount is bellow the expected sellAmount * triggerPrice.

The reason for that is because the app have a slippage that by default is calculate automatically but can also be manual set by the user on the order settings (engine icon). Limit price can be calculated by triggerPrice * (1 - slippage).

On your example the slippage is 20%. If the slippage is set high it ensures the trade is executed but users might get bad executions. By ensure it gets executed I mean that if the price drops too fast or CoW competition fails to fill that trade during the fall, the trade might not be executed. For now we’re capping the max slippage at 10%, but we might revisit that in the future.

Part of starting to share this to the public is getting this kind of feedback and understand what way it feels more natural for the user. Also we also want to analyze a bigger volume of orders to improve our auto slippage / limit price algorithm.

I see, the point is that if there is a market dip and it goes past trigger price for more than 10% your limit order will not be executed at all, thus risking even bigger loss. This should be left for the user to decide whether he wants wider slippage and executing instantly when the trigger is met or to risk not executing at all! Every cex /tradfi stop loss work like this u set trigger and limit price. This is very tricky cause higher limit price is risking staying with ur asset when it could go for example 50% which defeats the purpose of stop loss hedge strategy.

Aave trigger price - 140$
Aave limit price 135.
AAve price drops to 130. You stay with ur aave, then it goes to 80 and stays there. YOu are pissed ur stop loss activated but never executed. But if you want to be sure u always get market sell after trigger price u set trigger at 140$, limit 50$, your aave is dumped isntantly as soon as trigger 140$ is met.
If you wanna make it lighter for example for less volatile asset with higher liquidity ie ETH/USD, then user might set limit within ie 3% below trigger price and chil until limit is filled cause he does not expect dump by 50% in 2 sec liek for other shitcoins can happen. But there should be maximum flexibility for the user to adjust according to his strategy instead of fixing it at 10% max slippage. Also slippage is less intuitive than LIMIT order. There might be times when user want to set LIMIT order higher than the trigger price.. Ie aave drops to 140. Then I play for rebounce and set limit sell at 150$.

Id rather have proper full stop limit in parity to cex than half measure as it is right now.

1 Like

Currently the slippage cap I is only applied to our automatically slippage feature, users can set it above the 10%.

Regarding replace slippage with the limit price, I will discuss it with the rest of bleu. Your argument of provide a similar interface of CEX is strong. We’re also checking how our auto-slippage heuristic.

Playing for rebounce is a bit more tricker. The reason is because the trigger price isn’t a condition to only post the order, but also for execute it. The trigger price condition is valided by oracles on both placing and execution times. This means that, following your example, if AAVE drops to 130, COW would probably not fill a limit order of 150, and when the oracle starts to report the price back above 135 the order isn’t valid anymore. This change is more complex and wouldn’t be added for now.

Also, we’re exploring another product that is related with CoW and would love your opinion on it. Let’s set up a channel to discuss it (sent request on discord).

1 Like

FYI we changed the interface and now Limit price is an input on the first page of the card. Thanks for taking the time to test and provide feedback :blue_heart:

1 Like

Perfect! ship it on main cow swap ui :smiley: