# Solvers Solvers are the smart agents behind TETRICS protocol that take user-submitted intents and figure out the most efficient way to execute them. They work like a matchmaker in a busy marketplace—analyzing and optimizing transactions so that everything runs smoothly onchain. ### **What Are Solvers?** Solvers are specialized components that scan batches of blockchain intents to find the best execution paths. They aim to match intents from different users, optimizing for lower fees, speed, and overall security. By leveraging real‑time data and various liquidity sources, solvers ensure that every transaction is processed in the most effective manner possible.
### **How Do Solvers Work?** **1. Batch Analysis:** When multiple intents are submitted (like Alice’s and Bob’s), solvers group them into batches. This collective view allows them to see opportunities where intents might complement each other. **2. Finding Matches:** Consider Alice’s intent to buy 100 tokens if the price drops to $1 and Bob’s intent to stake tokens. A solver reviews the batch to see if Alice’s buying condition can be paired with a seller’s intent or another complementary action. **3. Optimization:** If a direct match isn’t found within the batch, solvers extend their search. They look into additional onchain or offchain liquidity sources and data streams to secure the best possible execution path. This process helps minimize gas fees and improve overall transaction efficiency. --- # Agent Instructions: 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: ``` GET https://tetrics.gitbook.io/x/architecture/intent-centric-framework/solvers.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.