# Snapshot System To simplify the user experience, we have chosen not to require users to pay transaction fees in EGLD. Integrating multiple tokens into the application would introduce unnecessary complexity and create a barrier to entry. Instead, most interactions within the app are paid by Ta-da, ensuring a seamless experience for users. However, for a micro-tasking application, it would be inefficient to cover transaction fees for every single action. Therefore, we implemented a snapshot system. It consolidates multiple transactions into a single one, significantly reducing fees. {% hint style="info" %} Example: a standard speech collection job may require \~5,000,000 tasks (productions and checks) and therefore as many blockchain transactions. Considering an average transaction fee of $0.03, the total cost would be $150,000, it's too prohibitive. {% endhint %} Currently, the snapshot system applies primarily to the deposit of TADA tokens (after swapping) into the Prize Pool, slashing, and in-app purchases. When a task is validated by a user, the associated payment is not immediately placed into the Prize Pool. Instead, these payments are aggregated and sent in one batch transaction. The same process applies to slashing and in-app purchases. Information on these transactions is saved in the database and finalized when the snapshot is executed. This approach allows us to maintain a cost-effective and efficient system while providing a smooth user experience. --- # 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://docs.ta-da.io/white-paper/blockchain-integration/snapshot-system.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.