A limit price says which execution terms are acceptable. A stop trigger says when an order should become active. A plain limit order does not automatically wait for a particular price crossing just because the user had that crossing in mind.
Two different instructions
Consider a hypothetical asset currently referenced at 10 B per A. An order to sell A for at least 8 B per A permits execution at 10 as well as at 9 or 8, subject to the protocol's rules. It does not mean “wait until the market falls to 8.”
A stop-style instruction adds a separate activation condition. For example, it might first require a specified reference to reach a threshold and only then allow an order to execute. The trigger source and execution price are distinct components.
The basic 0x limit-order fields encode exchange terms and expiry; they do not, by themselves, create a generic price-crossing trigger. CoW's order-type index likewise distinguishes ordinary orders from programmatic order capabilities.
A trigger is not a guaranteed execution price
Even when a product supports conditional activation, the market may move between trigger observation and settlement. A trigger at a quoted level does not mean that the full order can execute at that exact level.
A stop-limit design can activate an order that still remains unfilled because its price constraint is no longer achievable. A different design may prioritize execution with other bounds. The product must explain which behavior it implements.
Describe the intended behavior in plain language
Ask two questions separately: “Under what condition should this order become eligible?” and “After activation, what is the worst acceptable exchange?” If the interface captures only the second answer, do not assume it has captured the first.
This distinction prevents a common order-entry mistake without requiring a particular trading strategy. Always inspect the supported order type rather than trying to simulate a trigger merely by placing a limit far from the current reference price.
Sources & verification (4)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- Orders — 0x Protocol 4.1 documentation
Version-specific order fields: token identity, amounts, maker/taker, expiry and RFQ.
https://docs.0xprotocol.org/en/latest/basics/orders.html - Limit orders
Limit price, expiration and partial fill concepts.
https://docs.cow.fi/cow-protocol/concepts/order-types/limit-orders - Market orders
Market intent orders target prompt execution and can have bound conditions.
https://docs.cow.fi/cow-protocol/concepts/order-types/market-orders - Order types | CoW Protocol Documentation
Primary index for market, limit and programmatic order specifications.
https://docs.cow.fi/category/order-types