> For the complete documentation index, see [llms.txt](https://paragon-protocol.gitbook.io/paragon-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paragon-protocol.gitbook.io/paragon-protocol/core-products/intents-and-batching.md). # Intents & Batching ### Intents & Batching Paragon Flow upgrades swapping from a simple transaction model to an intent-based execution system. Instead of sending a transaction directly, users define their desired outcome and allow the system to execute it under optimal conditions. *** ### What Is an Intent? Instead of executing a trade immediately, you: * define what you want * set your minimum acceptable output (minOut) * sign an intent Paragon then handles execution on your behalf. *** ### How It Works #### 1. You Sign an Intent * no transaction is sent to the public mempool * no early exposure to bots * only a signed instruction is created *** #### 2. Batching Begins Your intent is grouped with others into a short execution window. This enables: * improved routing efficiency * better liquidity access * coordinated execution *** #### 3. Solvers Compete Independent solvers: * analyze all batched intents * route across available liquidity including: * Paragon liquidity * external liquidity (via 1inch and future integrations) They compete to find the best execution path. *** #### 4. Best Route Selection The system selects the optimal proposal based on: * highest output * lowest cost * execution reliability *** #### 5. Atomic Execution Trades are executed: * in a single batch * atomically * with reduced frontrunning risk *** #### 6. Settlement On-chain settlement: * verifies execution * enforces minimum output (minOut) * records execution data ๐Ÿ‘‰ Any execution improvement and distribution logic is handled at settlement and explained separately. *** ### Why Intents Improve Execution #### Better Pricing * multi-hop routing * cross-venue aggregation * solver competition *** #### More Efficient Execution * batched order flow * improved liquidity access * reduced fragmentation *** #### Execution Protection * minimum output enforcement * automatic revert if conditions are not met * optional fallback to classic swap *** ### Proof-of-Best-Execution (PoBE) Each trade records: * expected minimum output * actual execution output Displayed in the interface as: ๐Ÿ‘‰ โ€œYou saved X%โ€ All data is transparent and verifiable on-chain. *** ### Key Components * **Trader** โ†’ signs intent * **Batcher** โ†’ groups intents * **Solvers** โ†’ compete for execution * **FlowSettlement** โ†’ verifies and executes *** ### Fallback Protection If no solver can meet execution requirements: * the trade reverts (default) * or executes via the standard router (if enabled) Users are always protected by their defined minimum output. *** ### Evolution **Phase 1** * external routing (via 1inch) **Phase 2** * Paragon pools + external routing **Phase 3** * full multi-venue solver optimization *** ### Summary Paragon Flow introduces a new execution model based on: * intent-based trading * batch-based settlement * solver-driven routing Paragon Flow is the execution engine that powers optimized trading across the protocol. * **10% โ†’ stXPGN lockers** *** ### Why Intents Are Better #### MEV Resistance * no public mempool exposure * no sandwich attacks * private execution *** #### Better Pricing * multi-hop routing * cross-venue aggregation * solver competition *** #### Shared Value * you keep the savings * LPs are rewarded * protocol aligns incentives *** #### Smart Execution * enforced minOut * automatic revert if not met * optional fallback to classic swap *** ### Proof-of-Best-Execution (PoBE) Every trade is verified and recorded: * your expected output * actual output * surplus generated * how it was distributed Displayed in UI as: ๐Ÿ‘‰ **โ€œYou saved X%โ€** Fully transparent and on-chain. *** ### Key Components * **Trader** โ†’ signs intent * **Batcher** โ†’ groups intents * **Solvers** โ†’ compete for execution * **FlowSettlement** โ†’ verifies & executes *** ### Fallback Protection If no solver can beat your minimum: * trade reverts (default) * OR executes via classic router (if enabled) You are always protected. *** ### ๐ŸŒ Evolution (Important) #### Phase 1 * external routing (1inch, others) * Paragon pools only #### Phase 2 * internal Paragon pools + external routing #### Phase 3 * full multi-venue optimization *** ### ๐Ÿงพ Summary Paragon Flow introduces a new execution model: * intent-based trading * batch-based settlement * solver-driven routing * surplus sharing *** > Paragon Flow is not just a feature. > It is the **engine behind Paragon Shield and the foundation of next-generation DeFi execution.** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://paragon-protocol.gitbook.io/paragon-protocol/core-products/intents-and-batching.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.