> For the complete documentation index, see [llms.txt](https://docs.taco.build/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taco.build/reference/action-control/action-control/use-cases.md). # Use Cases ### Community Bot-Assisted Transactions Community platforms (e.g. a Discord server) leverage TACo, account abstraction, and specialized bots for secure member-to-member transactions . * **Challenge**: User wants to tip another user without setting up their own wallet, nor trusting a Discord bot with unconstrained access to their funds. * **Solution**: Conditional signing that only allows transactions that meet specific criteria – amount limits, recipient validation, rate limiting, etc. * **Benefits**: Users can tip each other and manage their smart account from within their communication application via bot slash commands, with guardrails preventing errant or malicious transactions. ### DAO Treasury Management Decentralized organizations use TACo to automate and safeguard Treasury/DAO operations and transactions. * **Challenge**: DAO requires multisig functionality with programmable and governance-driven execution conditions, without requiring manual approvals at each vote or payroll event. * **Solution**: Conditional signing with execution conditions based on election/governance/proposal/council outcomes and higher-level 'constitutional' guardrails. * **Benefits**: Automated and trust-minimized execution of approved transactions without manual coordination, signatory availability risk, or human error. ### Trading Agents and DeFi Automation Automated trading systems leverage TACo for safe and constrained trade execution. * **Challenge**: Trading bots need to execute trades but require safeguards against exploits, hallucinations, and illicit behavior. * **Solution**: Conditions that validate trade parameters – slippage limits, approved tokens, maximum position sizes, etc. * **Example**: A trading agent can only execute transactions that have been signed to confirm the proposed trade: * Is via approved DEXs. * Is within position size limits. * Meets minimum return thresholds. * Executes during specific time windows. ### Gaming and NFT Platforms Gaming platforms use TACo for in-game transactions. * **Challenge**: Players need transaction signing without exposing their primary wallets. * **Solution**: Game-specific conditions that limit signing to valid game actions. * **Example**: A gaming application can only execute transactions that have been signed to confirm the proposed action falls into one of these categories: * Transfer of game assets between validated players. * Remains within daily transaction limits. * Target/utilizes verified game contracts. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.taco.build/reference/action-control/action-control/use-cases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.