docs(common): move protocol stuff (#340)

Author: immortal-tofu

docs/introductions/architecture_overview.md

@@ -32,7 +32,8 @@ layout:
 
 ### **Set up your development environment**
 
-Use the official Hardhat template from Zama that includes all necessary configurations and dependencies to start developing confidential smart contracts.
+Use the official Hardhat template from Zama that includes all necessary configurations and dependencies to start
+developing confidential smart contracts.
 
 <a href="https://github.com/zama-ai/fhevm-hardhat-template" class="button secondary">Clone the template</a>
 {% endstep %}
@@ -41,8 +42,7 @@ Use the official Hardhat template from Zama that includes all necessary configur
 
 ### Write your first confidential smart contract
 
-Use the provided contract examples, like `MyCounter`, to begin. A basic counter contract might look
-like this:
+Use the provided contract examples, like `MyCounter`, to begin. A basic counter contract might look like this:
 
 ```solidity
 // SPDX-License-Identifier: BSD-3-Clause-Clear
@@ -64,17 +64,17 @@ contract MyCounter is ZamaConfig {
 }
 ```
 
-<a href="https://docs.zama.ai/doc-ui/IoEzE96rh6dKmIRhgam5/solidity-guides/get-started/overview" class="button primary">See the full
-Solidity guide</a> {% endstep %}
+<a href="https://docs.zama.ai/doc-ui/IoEzE96rh6dKmIRhgam5/solidity-guides/get-started/overview" class="button primary">See
+the full Solidity guide</a> {% endstep %}
 
 {% step %}
 
 ### Build your frontend with `@zama-ai/relayer-sdk`
 
 Start from Zama's ready-to-use React template.
 
-<a href="https://docs.zama.ai/doc-ui/IoEzE96rh6dKmIRhgam5/sdk-guides" class="button primary">See the full SDK
-guide</a> <a href="https://github.com/zama-ai/fhevm-react-template" class="button secondary">Clone the template</a> ;
+<a href="https://docs.zama.ai/doc-ui/IoEzE96rh6dKmIRhgam5/sdk-guides" class="button primary">See the full SDK guide</a>
+<a href="https://github.com/zama-ai/fhevm-react-template" class="button secondary">Clone the template</a> ;
 {% endstep %}
 
 {% step %}

docs/introductions/fhevm-components.md

@@ -1,20 +1,13 @@
-## Getting Started
+- [Welcome](README.md)
 
-- [Welcome to FHEVM[Draft]](README.md)
-- [Overview](introduction-overview.md)
+## Protocol
 
-## Architecture
-
-- [Litepaper](litepaper.md)
-- [Overview](architecture_overview.md)
-- [FHE on blockchain](fhe-on-blockchain.md)
-- [FHEVM components](fhevm-components.md)
-- [Encryption, decryption, and computation](d_re_ecrypt_compute.md)
-
-## References
-
-- [Table of all addresses](table_of_addresses.md)
-- [Repositories](overview.md)
+- [FHE on Blockchain](architecture/overview.md)
+  - [Coprocessor](architecture/coprocessor.md)
+  - [Gateway](architecture/gateway.md)
+  - [KMS](architecture/kms.md)
+  - [Relayer & Oracle](architecture/relayer_oracle.md)
+- [Roadmap](roadmap.md)
 
 ## Developer
 

docs/introductions/introduction-overview.md

@@ -0,0 +1,25 @@
+# Coprocessor
+
+The coprocessor is the compute engine of FHEVM, designed to handle resource-intensive homomorphic operations.
+
+### **Key functions**:
+
+1. **Execution**: Performs encrypted operations (e.g., _add_, _mul_) on ciphertexts using the evaluation key.
+2. **Ciphertext management**: Stores and retrieves ciphertexts securely in an off-chain database. Only handles are
+   returned on-chain.
+
+## **Computation**
+
+Encrypted computations are performed using the **evaluation key** on the coprocessor.
+
+- **How it works**:
+  1. The smart contract emits FHE operation events as symbolic instructions.
+  2. These events are picked up by the coprocessor, which evaluates each operation individually using the evaluation
+     key, without ever decrypting the data.
+  3. The resulting ciphertext is persisted in the coprocessor database, while only a handle is returned on-chain.
+- **Data flow**:
+  - **Source**: Blockchain smart contracts (via symbolic execution).
+  - **Processing**: Coprocessor (using the evaluation key).
+  - **Destination**: Blockchain (updated ciphertexts).
+
+<figure><img src="../.gitbook/assets/computation.png" alt="computation"><figcaption></figcaption></figure>

docs/introductions/litepaper.md

@@ -0,0 +1,12 @@
+# Gateway
+
+The Gateway acts as the communication hub between the blockchain, the coprocessor, the KMS, and user-facing
+applications.
+
+### **Key functions**:
+
+- **API for developers**: Exposes endpoints to submit encrypted inputs, request decryption, and manage user decryption.
+- **Proof validation**: Forwards ZKPoKs to the Coprocessor for verification.
+- **Off-chain coordination**: Handles smart contract and user decryption workflows in a verifiable and secure manner.
+
+The Gateway abstracts complex cryptographic flows, simplifying developer integration.

docs/introductions/repositories.md

@@ -0,0 +1,22 @@
+# Host chain
+
+FHEVM smart contracts are Solidity contracts that interact with encrypted values through symbolic execution.
+
+### **Symbolic execution in Solidity**
+
+- **Handles**: Smart contract operations return handles (references to ciphertexts), rather than directly manipulating
+  encrypted data.
+- **Lazy Execution**: Actual computation is done off-chain by the coprocessor after the contract emits symbolic
+  instructions.
+
+This allows efficient, gas-minimized interaction with encrypted data, while preserving EVM compatibility.
+
+### **Zero-Knowledge proofs of knowledge (ZKPoKs)**
+
+FHEVM incorporates ZKPoKs to verify the correctness of encrypted inputs and outputs:
+
+- **Validation**: ZKPoKs ensure that inputs are correctly formed and correspond to known plaintexts without revealing
+  sensitive data.
+- **Integrity**: They prevent misuse of ciphertexts and ensure the correctness of computations.
+
+By combining symbolic execution and ZKPoKs, FHEVM smart contracts maintain both privacy and verifiability.