# Overview The **MEV Zone Protect** system implements a **private transaction** submission mechanism that ensures the confidentiality of transactions until they are finalized within a block. This approach mitigates the risk of front-running by preventing transaction contents from being visible to external parties prior to block inclusion, restricting access exclusively to the block builder and validator. The process operates as follows: users submit their transactions to a designated MEV Zone Protect endpoint, where the transaction is retained in a confidential state. The transaction details are accessible only to the block builder, ensuring that they remain undisclosed during processing. The block builder evaluates the private transaction for inclusion in the next block based on predefined criteria, such as the bid amount or gas constraints. Once the block is broadcast and finalized, the transaction becomes publicly visible to all participants. This mechanism provides a structured approach to maintaining transaction privacy and mitigating pre-execution exploits in MEV-optimized environments. --- # 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://mevzone.gitbook.io/mevzone/mev-zone-protect/overview.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.