> ## Documentation Index
> Fetch the complete documentation index at: https://docs.saucerswap.finance/llms.txt
> Use this file to discover all available pages before exploring further.
# SaucerSwap V3
> Understand SaucerSwap V3's order book: bids and asks, maker and taker orders, wallet-held funds, off-chain matching, and on-chain settlement on Hedera.
SaucerSwap V3 is a central limit order book (CLOB) for spot trading on Hedera. You buy or sell tokens against orders at specific prices, instead of depositing liquidity into an automated market maker (AMM) pool. Tokens remain in your wallet until a trade settles on-chain.
## How an order book works
A market pairs a base token with a quote token. In SAUCE/USDC, for example, you buy or sell SAUCE at a price expressed in USDC per SAUCE. A buy order spends the quote token to receive the base token; a sell order does the reverse.
| Concept | Meaning |
| ------- | --------------------------------------------------------- |
| Bid | An order to buy the base token at a specified price |
| Ask | An order to sell the base token at a specified price |
| Spread | The difference between the highest bid and the lowest ask |
| Depth | The amount available at each price level |
| Fill | The executed portion of an order |
A large trade may fill against several orders at different prices. A displayed price does not mean your entire trade can execute at that price; available depth and your order's price limits determine what can fill. See [Slippage](/get-started/faq#what-is-slippage) for the difference between a quote and the execution you accept.
## Makers and takers
A maker adds an order that can be filled by another trader. A taker removes available liquidity by trading against it. The distinction depends on how an order fills, not simply whether you selected a limit or market order.
A limit order priced to cross the opposite side of the book can take liquidity immediately. Its unfilled remainder may rest on the book, where later fills act as maker fills. Maker rebates, where configured, are funded by taker fees rather than SAUCE emissions; see [Fees and rebates](/protocol/saucerswap-v3/fees).
## Order types
| Type | Behavior |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Limit | Buys at your limit price or lower, or sells at your limit price or higher; any resting amount remains subject to the order's deadline |
| Market | Seeks immediate execution against available liquidity within the signed amount and price-protection parameters |
| Maker-only | Restricts a limit order to maker fills so it cannot take liquidity |
| One-cancels-the-other (OCO) | Links two limit orders; when one is filled, the service requests cancellation of the other |
The [trading tutorial](/tutorials/trade) covers the web app. Maker-only and OCO parameters are documented in the [Orderbook API](/api-reference/orderbook/orders); do not assume every API option is exposed in the interface. OCO links are managed off-chain, so they do not provide an atomic on-chain guarantee that only one order can fill.
## Off-chain matching, on-chain settlement
V3 separates order entry from settlement:
1. You approve the required token allowance and sign an order message containing its trade parameters.
2. The off-chain matching engine maintains the book and finds fills.
3. The settlement contract, called the reactor, verifies signatures and executes the matched trades atomically on Hedera.
Signing an order does not deposit tokens into the book. Your wallet must retain the required balance and allowance for settlement; spending those tokens elsewhere can prevent an open order from filling. Token approvals are separate standing permissions, potentially for a maximum amount until revoked, rather than a limit that applies only to your next signed order.
Submitting orders and requesting cancellation through the off-chain service do not require a network transaction for each request. The protocol pays the network settlement fee on V3 fills, while traders pay their applicable trading fee. Wallet setup transactions and direct on-chain cancellation can still incur network fees.
## Order book and AMM liquidity
V3 operates alongside [V1](/protocol/saucerswap-v1) and [V2](/protocol/saucerswap-v2). Where enabled, an order can opt into AMM-backed settlement within its signed parameters. This backstop lets V3 orders use pool liquidity without turning the order book into an AMM pool.
The **swap** page compares an eligible V3 quote with the best V1/V2 AMM quote and selects one venue for the trade. This quote comparison is separate from AMM-backed settlement within V3. See [Swap routing](/protocol/routing) for the selection rules.
## Cancellation and settlement risks
An order can be partially filled before you cancel it; cancellation affects only what remains unfilled. An accepted cancellation request is not confirmation that matching or settlement has stopped. Check the final order and fill status before placing a replacement that could duplicate your trade.
Quotes, fills, and cancellation status can be delayed or differ from on-chain state. Non-custodial settlement does not guarantee liquidity, execution, or successful cancellation. Review every wallet prompt and read the [V3 Orderbook Risk Notice](/legal/orderbook-risk-notice) before trading.
SaucerSwap Labs operates the off-chain order entry, matching, and market-data services. Availability depends on that infrastructure even though your tokens remain in your wallet until settlement. Audit coverage is specific to the reviewed contracts and versions; see [Audits](/developers/security/audits).
## Next steps
Read the book, place an order, and follow its fills.
Understand market parameters, minimum orders, and trading availability.
Check trading fees, rebate limits, and xSAUCE discounts.
Follow fills and cancel or replace open orders.