bleu · mintlify · Mar 18, 2026
diff --git a/composable-cow/deployment/deploying.mdx b/composable-cow/deployment/deploying.mdx
@@ -24,6 +24,7 @@
 
 ```bash
 curl -L https://foundry.paradigm.xyz | bash
+# Note: This URL redirects to https://getfoundry.sh
 foundryup
 ```
 
@@ -61,4 +62,4 @@

 1. Verify deployments using `cast code`
 2. Update the `networks.json` registry
 3. Leverage the `broadcast/` directory artifacts containing deployment metadata and ABIs
diff --git a/cow-protocol/reference/sdks/cow-sdk.mdx b/cow-protocol/reference/sdks/cow-sdk.mdx
@@ -15,17 +15,17 @@

 The SDK supports all CoW Protocol enabled networks:

 * **Ethereum** (1) - `SupportedChainId.MAINNET`
 * **Gnosis Chain** (100) - `SupportedChainId.GNOSIS_CHAIN`
 * **Arbitrum One** (42161) - `SupportedChainId.ARBITRUM_ONE`
 * **Base** (8453) - `SupportedChainId.BASE`
 * **Polygon** (137) - `SupportedChainId.POLYGON`
 * **Avalanche** (43114) - `SupportedChainId.AVALANCHE`
 * **BNB** (56) - `SupportedChainId.BNB`
 * **Linea** (59144) - `SupportedChainId.LINEA`
 * **Plasma** (9745) - `SupportedChainId.PLASMA`
 * **Ink** (57073) - `SupportedChainId.INK`
 * **Sepolia** (11155111) - `SupportedChainId.SEPOLIA` (Testnet)

 ## 🔗 **Related Resources**

@@ -135,13 +135,13 @@
 The SDK automatically includes UTM tracking in all orders to attribute trading volume to developers. Default parameters:
 
 ```
-{  utmSource: 'cowmunity',  utmMedium: 'cow-sdk@7.1.6',  // SDK version  utmCampaign: 'developer-cohort',  utmContent: '',  utmTerm: 'js'}
+{  utmSource: 'cowmunity',  utmMedium: 'cow-sdk@<version>',  // SDK version (set automatically)  utmCampaign: 'developer-cohort',  utmContent: '',  utmTerm: 'js'}
 ```
 
 **Customize or disable** via `advancedSettings.appData.metadata.utm`:

 ```
 // Custom UTMawait sdk.getQuote(parameters, {  appData: {    metadata: {      utm: { utmContent: 'my-integration-v2' }    }  }})// Disable UTMawait sdk.getQuote(parameters, {  appData: {    metadata: {      utm: {}    }  }})
 ```

 > **Note:** Providing any `utm` field gives you full control - the SDK will not add defaults.
@@ -173,7 +173,7 @@
 ### Installation

 ```
 # For ethers v6pnpm add @cowprotocol/sdk-ethers-v6-adapter ethers# For ethers v5pnpm add @cowprotocol/sdk-ethers-v5-adapter ethers@^5.7.0# For viempnpm add @cowprotocol/sdk-viem-adapter viem
 ```

 ### Adapter Setup Examples
@@ -193,7 +193,7 @@
 #### ViemAdapter

 ```
 import { ViemAdapter } from '@cowprotocol/sdk-viem-adapter'import { http, createPublicClient, privateKeyToAccount } from 'viem'import { sepolia } from 'viem/chains'const account = privateKeyToAccount('YOUR_PRIVATE_KEY' as `0x${string}`)const transport = http('YOUR_RPC_URL')const provider = createPublicClient({ chain: sepolia, transport })// You can also set `walletClient` instead of `signer` using `useWalletClient` from wagmiconst adapter = new ViemAdapter({ provider, signer: account })
 ```

 ## Low-Level SDK Usage Example

diff --git a/cow-protocol/tutorials/solvers/local_test.mdx b/cow-protocol/tutorials/solvers/local_test.mdx
@@ -1,11 +1,11 @@
 ---
 title: "Locally testing a solver with the CoW Protocol orderflow"
 description: "CoW Protocol infrastructure is a lot of services running together in herd harmony, which is a bit intimidating at the beginning. Before proceeding, it would be advisable to read the architectural overview to get a better understanding of how CoW Protocol works and its entities."
 ---

 In order to test a solver against CoW Protocol's orderflow, one needs to locally run the following components

 * autopilot, which will be configured to point, for example, to the production orderbook and to send the auctions to a local driver.
 * driver, which will receive auctions from the autopilot and forward them to the solver engine
 * the solver engine that is meant to be tested, run as a local http server able to receive `/solve` requests from the driver and respond to them.

@@ -21,7 +21,7 @@
    cargo run --bin autopilot -- --native-price-estimators "Driver|baseline|http://driver/baseline" --skip-event-sync true --node-url $NODE_URL --shadow https://barn.api.cow.fi/mainnet --drivers "mysolver1|http://localhost:11088|0x0000000000000000000000000000000000000000|0"
 ```

 where one needs to set the NODE\_URL appropriately (e.g., a free Infura endpoint).

 <Warning>
  CoW Protocol services infrastructure can be very heavy on RPC resource consumption. Be careful if using with post-paid plans, it's recommended to keep a close eye on RPC resource consumption.
@@ -35,16 +35,16 @@

 where one needs to configure driver.config.toml to point to their solver engine. A sample such file can be found [here](https://github.com/cowprotocol/services/blob/main/crates/driver/example.toml).

 Once the above are set up and running, one can then start testing their solver engine against one of the following orderbooks:

 | Orderbook URL                                                                         | Network      | Environment |
 | ------------------------------------------------------------------------------------- | ------------ | ----------- |
 | [https://barn.api.cow.fi/mainnet/api](https://barn.api.cow.fi/mainnet/api)            | Mainnet      | Staging     |
 | [https://api.cow.fi/mainnet/api](https://api.cow.fi/mainnet/api)                      | Mainnet      | Production  |
 | [https://barn.api.cow.fi/xdai/api](https://barn.api.cow.fi/xdai/api)                  | Gnosis Chain | Staging     |
 | [https://api.cow.fi/xdai/api](https://api.cow.fi/xdai/api)                            | Gnosis Chain | Production  |
-| [https://barn.api.cow.fi/arbitrum\_one/api](https://barn.api.cow.fi/arbitrum_one/api) | Arbitrum One | Staging     |
-| [https://api.cow.fi/arbitrum\_one/api](https://api.cow.fi/arbitrum_one/api)           | Arbitrum One | Production  |
+| [https://barn.api.cow.fi/arbitrum_one/api](https://barn.api.cow.fi/arbitrum_one/api) | Arbitrum One | Staging     |
+| [https://api.cow.fi/arbitrum_one/api](https://api.cow.fi/arbitrum_one/api)           | Arbitrum One | Production  |
 | [https://barn.api.cow.fi/base/api](https://barn.api.cow.fi/base/api)                  | Base         | Staging     |
 | [https://api.cow.fi/base/api](https://api.cow.fi/base/api)                            | Base         | Production  |
 | [https://barn.api.cow.fi/avalanche/api](https://barn.api.cow.fi/avalanche/api)        | Avalanche    | Staging     |
@@ -53,12 +53,12 @@
 | [https://api.cow.fi/polygon/api](https://api.cow.fi/polygon/api)                      | Polygon      | Production  |
 | [https://barn.api.cow.fi/bnb/api](https://barn.api.cow.fi/bnb/api)                    | BNB          | Staging     |
 | [https://api.cow.fi/bnb/api](https://api.cow.fi/bnb/api)                              | BNB          | Production  |
 | [https://barn.api.cow.fi/linea/api](https://barn.api.cow.fi/linea/api)                | Linea        | Staging     |
 | [https://api.cow.fi/linea/api](https://api.cow.fi/linea/api)                          | Linea        | Production  |
 | [https://barn.api.cow.fi/plasma/api](https://barn.api.cow.fi/plasma/api)              | Plasma       | Staging     |
 | [https://api.cow.fi/plasma/api](https://api.cow.fi/plasma/api)                        | Plasma       | Production  |
 | [https://barn.api.cow.fi/ink/api](https://barn.api.cow.fi/ink/api)                    | Ink          | Staging     |
 | [https://api.cow.fi/ink/api](https://api.cow.fi/ink/api)                              | Ink          | Production  |
 | [https://barn.api.cow.fi/sepolia/api](https://barn.api.cow.fi/sepolia/api)            | Sepolia      | Staging     |
 | [https://api.cow.fi/sepolia/api](https://api.cow.fi/sepolia/api)                      | Sepolia      | Production  |

diff --git a/cow-py/api/swap.mdx b/cow-py/api/swap.mdx
@@ -3,7 +3,7 @@
 description: "Functions for swapping tokens using the CoW Protocol"
 ---

 ## swap_tokens

 Swap tokens using the CoW Protocol. This is the main high-level function for executing token swaps.

@@ -32,8 +32,8 @@
 | Parameter | Type | Required | Default | Description |
 |-----------|------|----------|---------|-------------|
 | `amount` | `Wei` | Yes | - | Amount of tokens to sell (in Wei) |
 | `account` | `LocalAccount` | Yes | - | Ethereum account to sign the order with |
 | `chain` | `Chain` | Yes | - | Blockchain network to execute on |
 | `sell_token` | `ChecksumAddress` | Yes | - | Address of the token to sell |
 | `buy_token` | `ChecksumAddress` | Yes | - | Address of the token to buy |
 | `safe_address` | `ChecksumAddress \| None` | No | `None` | Safe address (uses pre-signature scheme if provided) |
@@ -92,7 +92,7 @@

 ## CompletedOrder

 A Pydantic model representing a successfully created order.

 ```python
 class CompletedOrder(BaseModel):
@@ -105,15 +105,21 @@
 | Field | Type | Description |
 |-------|------|-------------|
 | `uid` | `UID` | Unique order identifier (56 bytes) |
-| `url` | `str` | CoW Explorer URL for tracking |
+| `url` | `str` | OrderBook API URL for the order |
 
-### Explorer URLs
+### Order URL
 
-The URL points to CoW Explorer based on the chain:
+The `url` field contains the OrderBook API endpoint for the order:
+
+```
+https://api.cow.fi/mainnet/api/v1/orders/{uid}
+```
+
+To get the CoW Explorer URL for user-facing tracking, construct it manually:
 
 - Mainnet: `https://explorer.cow.fi/ethereum/orders/{uid}`
 - Gnosis Chain: `https://explorer.cow.fi/gc/orders/{uid}`
 - Arbitrum: `https://explorer.cow.fi/arb1/orders/{uid}`

 ```python
 result = await swap_tokens(...)

diff --git a/cow-py/guides/swapping-tokens.mdx b/cow-py/guides/swapping-tokens.mdx
@@ -11,9 +11,9 @@

 Before swapping tokens, ensure you have:

 - An Ethereum account with a private key
 - Sufficient balance of the token you want to sell
 - Token approval for the CoW Protocol Vault Relayer

 ## Token Approval Flow

@@ -32,7 +32,7 @@
    ```
  </Step>
  <Step title="Approve Token Spending">
    Grant the Vault Relayer permission to spend your tokens:

    ```python
    from eth_typing import ChecksumAddress
@@ -213,8 +213,8 @@
 | Parameter | Type | Required | Default | Description |
 |-----------|------|----------|---------|-------------|
 | `amount` | `Wei` | Yes | - | Amount of sell token to swap |
 | `account` | `LocalAccount` | Yes | - | Ethereum account for signing |
 | `chain` | `Chain` | Yes | - | Target blockchain network |
 | `sell_token` | `ChecksumAddress` | Yes | - | Address of token to sell |
 | `buy_token` | `ChecksumAddress` | Yes | - | Address of token to buy |
 | `safe_address` | `ChecksumAddress \| None` | No | `None` | Safe/multisig address (if applicable) |
@@ -229,10 +229,9 @@
 The function returns a `CompletedOrder` object with:
 
 ```python
-@dataclass
-class CompletedOrder:
+class CompletedOrder(BaseModel):
     uid: UID  # Unique order identifier
-    url: str  # CoW Explorer URL for tracking
+    url: str  # OrderBook API URL for the order
 ```
 
 ## How It Works
@@ -254,7 +253,7 @@

 ## After the Swap

 When `swap_tokens` returns a `CompletedOrder`, the order has been submitted to the CoW Protocol orderbook. Solvers now compete in batch auctions to find the best execution path for your trade.

 ### Monitoring Order Status

@@ -288,7 +287,14 @@
 If your order has not yet been filled, you can request cancellation:
 
 ```python
-await api.delete_order(completed_order.uid, signature, signing_scheme)
+from cowdao_cowpy.order_book.generated.model import OrderCancellations
+
+cancellation = OrderCancellations(
+    orderUids=[completed_order.uid],
+    signature=signature,
+    signingScheme=signing_scheme,
+)
+await api.delete_order(cancellation)
 ```
 
 <Note>
@@ -299,14 +305,17 @@

 The SDK supports swapping on the following networks:

 - **Ethereum Mainnet** -- `Chain.MAINNET`
 - **Gnosis Chain** -- `Chain.GNOSIS`
 - **Arbitrum One** -- `Chain.ARBITRUM_ONE`
 - **Base** -- `Chain.BASE`
+- **Polygon** -- `Chain.POLYGON`
+- **Avalanche** -- `Chain.AVALANCHE`
+- **BNB Smart Chain** -- `Chain.BNB`
 - **Sepolia Testnet** -- `Chain.SEPOLIA`
 
 <Tip>
  Use `Chain.SEPOLIA` for testing without spending real funds. Get testnet tokens from Sepolia faucets.
 </Tip>

 ## Error Handling
@@ -339,11 +348,11 @@

 | Problem | Likely Cause | Fix |
 |---------|-------------|-----|
 | `InsufficientAllowance` error | Vault Relayer not approved | Run the token approval flow first |
 | `InsufficientBalance` error | Not enough sell token | Check balance before calling `swap_tokens` |
 | Order created but never fills | Low liquidity or tight slippage | Increase `slippage_tolerance`, try common pairs |
 | `NoLiquidity` error | Token pair not supported | Verify token addresses, try larger amounts |
 | `UnexpectedResponseError` | API issue or invalid params | Check token addresses are checksummed, amount > 0 |
 | Order expires | Solvers couldn't fill in time | Use longer `valid_to`, wider slippage |

 ## Next Steps

diff --git a/cow-py/quickstart.mdx b/cow-py/quickstart.mdx
@@ -3,10 +3,10 @@
 description: "Execute your first token swap with the CoW Protocol Python SDK"
 ---

 This guide walks through creating and executing a token swap on CoW Protocol using the Python SDK, learning how to swap tokens with built-in MEV protection and gasless trading.

 <Note>
  CoW Protocol employs batch auctions to protect traders from MEV and provides the best execution prices by aggregating liquidity across multiple DEXs.
 </Note>

 ## Prerequisites
@@ -14,12 +14,12 @@
 Before starting, ensure you have:

 - The CoW Protocol Python SDK [installed](/cow-py/installation)
 - A wallet with test tokens (Sepolia testnet)
 - Your wallet's private key
 - Approval for the CoW Protocol Vault Relayer to spend your tokens

 <Warning>
  You must approve the CoW Protocol Vault Relayer contract before executing a swap.
 </Warning>

 ## Environment Setup
@@ -96,7 +96,7 @@
 from cowdao_cowpy.common.chains import Chain
 ```

 The SDK uses `web3.py` for Ethereum interactions and provides a simple `swap_tokens` function.

 ### Configure Token Addresses

@@ -110,7 +110,7 @@
 ```

 <Tip>
  Always use checksummed addresses to avoid errors via `Web3.to_checksum_address()`.
 </Tip>

 ### Specify Sell Amount
@@ -141,7 +141,7 @@
 )
 ```

 The function handles quote retrieval, order creation and signing, orderbook submission, and returns the order UID and explorer URL.

 ## Advanced Options

@@ -155,7 +155,7 @@
     slippage_tolerance=0.01,  # 1% slippage (default: 0.5%)
     partially_fillable=False,  # Allow partial fills (default: False)
     valid_to=None,  # Order expiry timestamp (default: uses quote expiry)
-    env="prod"  # Environment: "prod", "staging", or "barn" (default: "prod")
+    env="prod"  # Environment: "prod" or "staging" (default: "prod")
 )
 ```
 
@@ -212,7 +212,7 @@
    Ensure your wallet has enough of the sell token. Account for token decimals when checking balances.
  </Accordion>
  <Accordion title="Missing Token Approval">
    Before swapping, approve the CoW Protocol Vault Relayer:

    ```python
    from cowdao_cowpy.common.constants import CowContractAddress
@@ -228,7 +228,7 @@
 ## Next Steps

 - Explore [Order Management](/cow-py/guides/managing-orders) to learn how to fetch, monitor, and cancel orders
 - Investigate [Advanced Features](/cow-py/advanced/composable-orders) for composable orders and TWAP strategies
 - Browse the [API Reference](/cow-py/api/swap) for complete documentation
 - Learn about [Contract Interaction](/cow-py/guides/contract-interaction) with CoW Protocol smart contracts
 - Read the [Testing Guide](/cow-protocol/howto/integrate/testing) for how to test on Sepolia and graduate to production
diff --git a/cow-sdk/api/subgraph-sdk.mdx b/cow-sdk/api/subgraph-sdk.mdx
@@ -1,9 +1,13 @@
 ---
 title: "Subgraph SDK"
 description: "TypeScript client for querying CoW Protocol's historical trading data and metrics from TheGraph"
 ---
 
+<Warning>
+The `SubgraphApi` is deprecated and not currently maintained. It may be removed in a future SDK version. Consider using the [OrderBook API](/cow-protocol/reference/apis/orderbook) for querying order and trade data instead.
+</Warning>
+
 The SubgraphApi provides a TypeScript client for querying historical trading data, volume statistics, and protocol metrics from CoW Protocol subgraphs across multiple chains.
 
 ## Installation

@@ -17,9 +21,9 @@

 ## Features

 - **SubgraphApi Client** - Dedicated client for subgraph querying
 - **Pre-built Queries** - Common queries for protocol statistics
 - **Multi-chain Support** - Currently available on Ethereum, Gnosis Chain, Arbitrum One, Base, and Sepolia (subset of all supported CoW Protocol chains)
 - **Type-safe Responses** - All GraphQL responses are fully typed
 - **Custom Query Support** - Execute custom GraphQL queries with type safety

@@ -37,14 +41,14 @@
 Optional configuration
  <Expandable>
    <ResponseField name="chainId" type="SupportedChainId">
    Chain ID for queries (defaults to Mainnet)
    </ResponseField>
  </Expandable>
 </ResponseField>

 ## Methods

 ### getTotals

 Get overall protocol statistics including tokens, orders, traders, settlements, volume, and fees.

@@ -138,7 +142,7 @@
  </Expandable>
 </ResponseField>

 ### runQuery

 Execute a custom GraphQL query with full type safety.

@@ -271,11 +275,11 @@

 The SubgraphApi currently supports the following networks (a subset of the full CoW Protocol chain list):

 - Ethereum Mainnet
 - Gnosis Chain
 - Arbitrum One
 - Base
 - Sepolia Testnet

 ## API Key Requirements


diff --git a/cow-sdk/installation.mdx b/cow-sdk/installation.mdx
@@ -7,7 +7,7 @@

 ## Quick Overview

 The CoW Protocol SDK enables blockchain interaction through three adapter options. Installation involves the main package plus your chosen adapter framework.

 ## Core Installation

@@ -21,13 +21,13 @@

 You must choose one of three adapters based on your Web3 library:

 **Viem** - Modern, lightweight TypeScript library requiring viem 1.x+

 **Ethers v6** - The current ethers.js version (recommended for ethers users)

 **Ethers v5** - Legacy version; consider upgrading to v6 or using Viem

 Each adapter installation differs slightly. For Viem, you'd run:

 ```bash
 npm install @cowprotocol/sdk-viem-adapter viem
@@ -35,14 +35,14 @@

 ## Essential Dependencies

 The SDK requires `cross-fetch` (^3.x). Optional packages include `ipfs-only-hash`, `multiformats`, and `@openzeppelin/merkle-tree` for specialized features like app-data metadata and merkle operations.
 
 ## Environment Requirements
 
-Node.js 16+ is mandatory. TypeScript support includes built-in type definitions with standard `tsconfig.json` settings (moduleResolution: "node", esModuleInterop: true).
+Node.js 22+ is required. TypeScript support includes built-in type definitions with standard `tsconfig.json` settings (moduleResolution: "node", esModuleInterop: true).
 
 ## Framework Integration
 
 React/Next.js users typically integrate via wagmi, while Node.js backends use direct Viem initialization with environment variables for sensitive credentials.
 
-The current SDK version is **v7.4.1**, with migration guidance available for v6 upgrades.
+Migration guidance is available for v6 to v7 upgrades.
diff --git a/cow-sdk/quickstart.mdx b/cow-sdk/quickstart.mdx
@@ -5,18 +5,18 @@

 # CoW Protocol SDK Quickstart Guide

 This documentation provides a comprehensive walkthrough for executing your first token swap using the CoW Protocol SDK in under five minutes.

 ## Key Prerequisites
 
 Before starting, ensure you have:
-- Node.js version 16 or higher
+- Node.js version 22 or higher
 - A wallet containing a private key for transaction signing
 - An RPC endpoint URL (Alchemy, Infura, or Tenderly)
 - Test tokens on Sepolia testnet

 <Warning>
 Test on testnets before attempting mainnet transactions.
 </Warning>

 ## Installation & Setup
@@ -32,9 +32,9 @@
 ## Web3 Adapter Configuration

 The guide provides implementations for three frameworks:
 - **Viem**: Using `createPublicClient` and `privateKeyToAccount`
 - **Ethers v6**: Using `JsonRpcProvider` and `Wallet`
 - **Ethers v5**: Using `ethers.providers.JsonRpcProvider`

 Each adapter requires a provider (read-only client) and signer (wallet with private key).

@@ -71,7 +71,7 @@
 ## Troubleshooting Common Issues

 The documentation addresses frequent problems:
 - **Insufficient balance**: Obtain test tokens from the Sepolia faucet
 - **Allowance errors**: Complete token approval before swapping
 - **Expired quotes**: Refresh quotes within the validity window
 - **RPC failures**: Verify endpoint URLs or try alternative providers
@@ -84,7 +84,7 @@
 ```typescript
 {
   utmSource: 'cowmunity',
-  utmMedium: 'cow-sdk@7.1.6',  // SDK version
+  utmMedium: 'cow-sdk@<version>',  // SDK version (set automatically)
   utmCampaign: 'developer-cohort',
   utmContent: '',
   utmTerm: 'js'

diff --git a/cow-swap/widget/params.mdx b/cow-swap/widget/params.mdx
@@ -3,7 +3,7 @@
 description: "Integrate the power of  into your product! With the widget, you can create an incredible trading interface. Specify the required pair of currencies, customize the look and much more!"
 ---

 Create your own widget using the configurator [https://widget.cow.fi](https://widget.cow.fi).

 ![Demo](/images/cow-protocol/tutorials/assets/images/widget-bc5358690765bdbc5b2bc9d2a13a20b5.png)

@@ -25,7 +25,7 @@
 
 ## App key
 
-You must specify the `appCode` parameter when initializing the widget. This parameter is used to identify the source of orders. The key must be a UTF8 string of up to 50 chars. It will be a part of orders meta-data, see more in the [CoW Protocol Docs](https://docs.cow.fi/front-end/creating-app-ids/create-the-order-meta-data-file/appcode).
+You must specify the `appCode` parameter when initializing the widget. This parameter is used to identify the source of orders. The key must be a UTF8 string of up to 50 chars. It will be a part of orders meta-data, see more in the [CoW Protocol Docs](/cow-protocol/reference/core/intents/app-data).
 
 ## Partner fee
 
@@ -35,7 +35,7 @@
 import { createCowSwapWidget, CowSwapWidgetParams } from '@cowprotocol/widget-lib'const widgetContainer = document.getElementById('cowswap-widget')const params: CowSwapWidgetParams = {  partnerFee: {    bps: 50, // 0.5%    recipient: '0x0000000000000000000000000000000000000000', // Fee destination address  },}createCowSwapWidget(widgetContainer, { params })
 ```

 This configuration will apply a partner fee for all networks and trade types (swaps, limit orders, TWAPs, etc.). You can use [Flexible config](#flexible-config) for having more flexibility, or [Advanced configuration](#advanced-configuration) to have even more control over the partner fee configuration parameters.

 ### Flexible config

@@ -69,7 +69,7 @@

 The recipient is the address to which the fee will be sent.

 Make sure that the fee recipient address exists on the respective network defined in the parameters. For example, if you use a Safe as a recipient and the Safe was created on Ethereum mainnet, then for Gnosis Chain you must create **another** Safe and set it as a fee recipient.

 As a fee recipient, you can specify either string or a key-value pair in the format `chainId: recipientAddress`:

@@ -120,9 +120,9 @@
 | **Ranges**         | `min ≥ 0`, `max ≤ 5000` (50 %), `min ≤ defaultValue ≤ max`, `min < max`                                                                                                                         |
 | **Defaults**       | If the user doesn’t specify a slippage, the widget falls back to `defaultValue`                                                                                                                 |
 | **Auto slippage**  | If the auto-slippage is less than or equal to `defaultValue`, the swap will use `defaultValue`                                                                                                  |
 | **ETH‑Flow floor** | When `defaultValue < 200` bps (2 %) for Ethereum Mainnet or `defaultValue < 50` (0.5 %) for other networks and the trade is *ETH‑Flow*, the widget will force the slippage to **2 %**/**0.5 %** |

 ### Example JSON (Configurator ready)

 ```
 {  "slippage": {    "1": { "min": 1, "max": 3900, "defaultValue": 3000 },    "8453": { "min": 500, "max": 5000, "defaultValue": 600 }  }}

diff --git a/flash-loan-router/getting-started/installation.mdx b/flash-loan-router/getting-started/installation.mdx
@@ -9,10 +9,11 @@

 ### Foundry

 The Flash-Loan Router is built with Foundry, a blazing fast Ethereum development toolkit. Install Foundry using:
 
 ```bash
 curl -L https://foundry.paradigm.xyz | bash
+# Note: This URL redirects to https://getfoundry.sh
 foundryup
 ```
 

diff --git a/snippets/supported-networks.mdx b/snippets/supported-networks.mdx
@@ -2,15 +2,15 @@

 | Network | Chain ID | Type |
 | --- | --- | --- |
 | Ethereum | 1 | Mainnet |
 | Gnosis Chain | 100 | Mainnet |
 | Arbitrum One | 42161 | Layer 2 |
 | Base | 8453 | Layer 2 |
 | Polygon | 137 | Sidechain |
 | Avalanche C-Chain | 43114 | Sidechain |
 | BNB Smart Chain | 56 | Sidechain |
-| Optimism | 10 | Layer 2 |
+| Optimism | 10 | Layer 2 (bridge-only) |
 | Linea | 59144 | Layer 2 |
 | Plasma | 9745 | Layer 2 |
 | Ink | 57073 | Layer 2 |
 | Sepolia | 11155111 | Testnet |
diff --git a/watch-tower/development/setup.mdx b/watch-tower/development/setup.mdx
@@ -11,7 +11,7 @@
 
 To develop the CoW Protocol Watch Tower, you'll need:
 
-* `node` (`>= v16.18.0`)
+* `node` (`>= v18.0.0`)
 * `yarn`
 * `npm`
 
@@ -25,7 +25,7 @@

 ## Local Development Workflow

 Testing against the Goerli or Sepolia testnet is recommended during development.

 To run the watch-tower locally:

@@ -62,12 +62,12 @@
 * `--slack-webhook <url>` - Slack webhook URL
 * `--only-owner <address...>` - Monitor specific contract/safe addresses only

 ## Testing Against Testnets

 When developing, test against Goerli or Sepolia testnet by following these steps:

 1. Configure your RPC endpoint in the config file
 2. Set the appropriate deployment block for the testnet
 3. Run the watch-tower with your test configuration

 ```bash

diff --git a/watch-tower/getting-started/installation.mdx b/watch-tower/getting-started/installation.mdx
@@ -5,15 +5,15 @@

 # Installation

 The CoW Protocol Watch Tower is a standalone application that monitors blockchain events for programmatic orders and submits them to the CoW Protocol OrderBook API.

 ## Requirements
 
 Before installing the Watch Tower, ensure you have the following:
 
-* Node.js `>= v16.18.0`
+* Node.js `>= v18.0.0`
 * yarn package manager
 * An RPC node connected to a supported network (Ethereum mainnet, Arbitrum One, Gnosis Chain, Base, Sepolia, etc.)
 * Internet access to the CoW Protocol OrderBook API

 ## Installation
@@ -74,7 +74,7 @@

 <Steps>
  <Step title="Generate type definitions">
    Generate TypeChain types from contract ABIs:

    ```bash
    yarn typechain

diff --git a/watch-tower/introduction.mdx b/watch-tower/introduction.mdx
@@ -9,15 +9,15 @@
 
 ## What is Watch Tower?
 
-The Watch Tower is a standalone application that monitors the blockchain for programmatic orders created through the [CoW Protocol](https://docs.cow.fi/cow-protocol) [programmatic order framework](https://docs.cow.fi/cow-protocol/concepts/order-types/programmatic-orders). It acts as a critical infrastructure component that bridges on-chain programmatic orders with the CoW Protocol OrderBook API.
+The Watch Tower is a standalone application that monitors the blockchain for programmatic orders created through the [CoW Protocol](https://docs.cow.fi/cow-protocol) [programmatic order framework](/cow-protocol/reference/contracts/programmatic/twap). It acts as a critical infrastructure component that bridges on-chain programmatic orders with the CoW Protocol OrderBook API.
 
 > "Watch Tower keeps an eye on Composable Cows, automatically detecting new programmatic orders and posting eligible discrete orders to the orderbook."
 
 ## Why does it exist?

 Programmatic orders in CoW Protocol allow users to define trading logic on-chain through smart contracts. However, these orders need to be:

 1. **Discovered** - The watch tower monitors blockchain events to detect when new programmatic orders are created
 2. **Evaluated** - It continuously polls programmatic orders to check if their execution conditions are met
 3. **Submitted** - When conditions are satisfied, it posts the resulting discrete orders to the CoW Protocol OrderBook API

@@ -47,14 +47,14 @@
 The watch tower tracks two primary events emitted by the `ComposableCoW` contract:

 * **`ConditionalOrderCreated`** - Emitted when a single programmatic order is created
 * **`MerkleRootSet`** - Emitted when a batch of programmatic orders (merkle tree) is set for a safe

 ### Persistent registry

 All discovered programmatic orders are stored in a local LevelDB database, maintaining:

 * Active programmatic orders by owner (safe address)
 * Order parameters and merkle proofs
 * Last processed block information
 * Submitted discrete order status

@@ -74,11 +74,11 @@

 The watch tower can monitor multiple chains simultaneously, including:

 * Ethereum Mainnet
 * Arbitrum One
 * Gnosis Chain
 * Base
 * Sepolia (testnet)

 ## Use cases

@@ -90,7 +90,7 @@
 * Ensure reliable execution of your users' programmatic orders
 * Maintain independence from third-party infrastructure

 ### For DApp node operators

 The watch tower is available as a [DAppNode package](https://github.com/cowprotocol/dappnodepackage-cow-watch-tower), allowing you to: