# Threshold Encryption

To solve the MEV crisis, FOGEVM implements Threshold Encryption for transaction propagation.

* **The Problem:** On Ethereum, transactions are broadcast in plaintext. Everyone sees them before they are confirmed.
* **The Solution:**

1. **User Side:** The user's wallet generates a transaction and encrypts it using the network's Public Key.
2. **Propagation:** The encrypted blob is broadcast to the network. No node can decrypt it individually.
3. **Consensus:** Once the transactions are ordered into a block by the Sequencer, the validator committee collaborates to construct the Decryption Key.
4. **Execution:** The block is decrypted and executed only after the order is finalized.

* **Outcome:** Front-running is physically impossible because the "front" of the line is determined before the data is revealed.


---

# 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.fogevm.vip/core-technology/threshold-encryption.md?ask=<question>
```

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.
