Merge branch 'main' into poppyseedDev/library-solidity-patch

Author: poppyseedDev

charts/coprocessor/Chart.yaml

@@ -1,6 +1,6 @@
 name: coprocessor
 description: A helm chart to distribute and deploy Zama fhevm Co-Processor services
-version: 0.8.2
+version: 0.8.3
 apiVersion: v2
 keywords:
   - fhevm

charts/coprocessor/values.yaml

@@ -535,15 +535,8 @@ tfheWorker:
     - --metrics-addr=0.0.0.0:9100
     - --service-name=tfhe-worker  # tfhe-worker service name in OTLP traces
     - --log-level=INFO
-    # Should not be used (unsafe - testing only, keep 0/false values except CI)
-    - --run-server=false
+    # Should not be used (unsafe - testing only, keep false values except CI)
     - --generate-fhe-keys=false
-    - --server-maximum-ciphertexts-to-schedule=0
-    - --server-maximum-ciphertexts-to-get=0
-    - --maximum-compact-inputs-upload=0
-    - --maximum-handles-per-input=0
-    - --server-addr=""
-    - --coprocessor-private-key=""
     # Unique worker identifier (valid UUID v4 format)
     # If not set, defaults to a random UUID generated at startup
     - --worker-id=$(WORKER_ID)

coprocessor/README.md

@@ -72,38 +72,24 @@ $ tfhe_worker --help
 Usage: tfhe_worker [OPTIONS]
 
 Options:
-      --run-server
-          Run the API server
       --run-bg-worker
           Run the background worker
       --generate-fhe-keys
           Generate fhe keys and exit
-      --server-maximum-ciphertexts-to-schedule <SERVER_MAXIMUM_CIPHERTEXTS_TO_SCHEDULE>
-          Server maximum ciphertexts to schedule per batch [default: 5000]
-      --server-maximum-ciphertexts-to-get <SERVER_MAXIMUM_CIPHERTEXTS_TO_GET>
-          Server maximum ciphertexts to serve on get_cihpertexts endpoint [default: 5000]
       --work-items-batch-size <WORK_ITEMS_BATCH_SIZE>
           Work items batch size [default: 10]
       --tenant-key-cache-size <TENANT_KEY_CACHE_SIZE>
           Tenant key cache size [default: 32]
-      --maximum-compact-inputs-upload <MAXIMUM_COMPACT_INPUTS_UPLOAD>
-          Maximum compact inputs to upload [default: 10]
-      --maximum-handles-per-input <MAXIMUM_HANDLES_PER_INPUT>
-          Maximum compact inputs to upload [default: 255]
       --coprocessor-fhe-threads <COPROCESSOR_FHE_THREADS>
           Coprocessor FHE processing threads [default: 8]
       --tokio-threads <TOKIO_THREADS>
           Tokio Async IO threads [default: 4]
       --pg-pool-max-connections <PG_POOL_MAX_CONNECTIONS>
           Postgres pool max connections [default: 10]
-      --server-addr <SERVER_ADDR>
-          Server socket address [default: 127.0.0.1:50051]
       --metrics-addr <METRICS_ADDR>
           Prometheus metrics server address [default: 0.0.0.0:9100]
       --database-url <DATABASE_URL>
           Postgres database url. If unspecified DATABASE_URL environment variable is used
-      --coprocessor-private-key <COPROCESSOR_PRIVATE_KEY>
-          Coprocessor private key file path. Private key is in plain text 0x1234.. format [default: ./coprocessor.key]
 ```
 
 ```bash

coprocessor/docs/fundamentals/fhevm/coprocessor/fhe_computation.md

@@ -5,30 +5,32 @@ Block execution in FHEVM-coprocessor is split into two parts:
 - Symbolic Execution (onchain)
 - FHE Computation (offchain)
 
-Symbolic execution happens onchain, inside the [FHEVMExecutor](../../../../contracts/contracts/FHEVMExecutor.sol) contract (inside the EVM). Essentially, the EVM accumulates all requested FHE operations in a block with their input handles and the corresponding result handles. Then, at the end of block execution, it sends an `AsyncCompute` request to the coprocessor such that FHE computation can be done **eventually**. Note that FHE computation can be done at a future point in time, after the block has been committed on the host blockchain. We can do that, symbolic execution only needs handles and doesn't actual FHE ciphertexts. Actual FHE ciphertexts are needed only on **decryption** and **reencryption**, i.e. when a user wants to see the plaintext value.
+Symbolic execution happens onchain, inside the [FHEVMExecutor](../../../../contracts/contracts/FHEVMExecutor.sol) contract (inside the EVM). Essentially, the EVM accumulates all requested FHE operations in a block with their input handles and the corresponding result handles. These operations are emitted as on-chain events (logs) that the host-listener ingests into the coprocessor database, such that FHE computation can be done **eventually**. Note that FHE computation can be done at a future point in time, after the block has been committed on the host blockchain. We can do that, symbolic execution only needs handles and doesn't need actual FHE ciphertexts. Actual FHE ciphertexts are needed only on **decryption** and **reencryption**, i.e. when a user wants to see the plaintext value.
 
 ```mermaid
 sequenceDiagram
     participant Full Node
-    participant Coprocessor
+    participant Host Listener
     participant DB
+    participant TFHE Worker
 
     loop Block Execution - Symbolic
         Note over Full Node: Symbolic Execution on handles in Solidity
         Note over Full Node: Inside EVM: computations.add(op, [inputs], [result_handles])
     end
 
     Note over Full Node: End of Block Execution
+    Note over Full Node: FHE operations emitted as on-chain events (logs)
 
-    Full Node->>+Coprocessor: AsyncCompute (AsyncComputeRequest(computations))
-    Coprocessor->>+DB: Insert Computations
-    DB->>-Coprocessor: Ack
-    Coprocessor->>-Full Node: AsyncComputeResponse
+    Host Listener->>Full Node: Poll for new events
+    Full Node->>Host Listener: FHE operation events
+    Host Listener->>+DB: Insert Computations
+    DB->>-Host Listener: Ack
 
     loop FHE Computation
-        Coprocessor --> DB: Read Input Ciphertexts
-        Note over Coprocessor: FHE Computation
-        Coprocessor --> DB: Write Result Ciphertexts
+        TFHE Worker --> DB: Read Input Ciphertexts
+        Note over TFHE Worker: FHE Computation
+        TFHE Worker --> DB: Write Result Ciphertexts
     end
 ```
 
@@ -38,6 +40,6 @@ Note that, for now, we omit the Data Availability (DA) layer. It is still work i
 
 ## Parallel Execution
 
-Since the Coprocessor can extract data dependencies from the `AsyncCompute` request, it can use them to execute FHE computations in parallel.
+Since the coprocessor can extract data dependencies from the ingested events, it can use them to execute FHE computations in parallel.
 
 At the time of writing, the Coprocessor uses a simple policy to schedule FHE computation on multiple threads. More optimal policies will be introduced in the future and made configurable.

coprocessor/docs/getting_started/fhevm/coprocessor/configuration.md

@@ -11,38 +11,24 @@ coprocessor --help
 Usage: coprocessor [OPTIONS]
 
 Options:
-      --run-server
-          Run the API server
       --run-bg-worker
           Run the background worker
       --generate-fhe-keys
           Generate fhe keys and exit
-      --server-maximum-ciphertexts-to-schedule <SERVER_MAXIMUM_CIPHERTEXTS_TO_SCHEDULE>
-          Server maximum ciphertexts to schedule per batch [default: 5000]
-      --server-maximum-ciphertexts-to-get <SERVER_MAXIMUM_CIPHERTEXTS_TO_GET>
-          Server maximum ciphertexts to serve on get_cihpertexts endpoint [default: 5000]
       --work-items-batch-size <WORK_ITEMS_BATCH_SIZE>
           Work items batch size [default: 10]
       --tenant-key-cache-size <TENANT_KEY_CACHE_SIZE>
           Tenant key cache size [default: 32]
-      --maximum-compact-inputs-upload <MAXIMUM_COMPACT_INPUTS_UPLOAD>
-          Maximum compact inputs to upload [default: 10]
-      --maximum-handles-per-input <MAXIMUM_HANDLES_PER_INPUT>
-          Maximum compact inputs to upload [default: 255]
       --coprocessor-fhe-threads <COPROCESSOR_FHE_THREADS>
           Coprocessor FHE processing threads [default: 8]
       --tokio-threads <TOKIO_THREADS>
           Tokio Async IO threads [default: 4]
       --pg-pool-max-connections <PG_POOL_MAX_CONNECTIONS>
           Postgres pool max connections [default: 10]
-      --server-addr <SERVER_ADDR>
-          Server socket address [default: 127.0.0.1:50051]
       --metrics-addr <METRICS_ADDR>
           Prometheus metrics server address [default: 0.0.0.0:9100]
       --database-url <DATABASE_URL>
           Postgres database url. If unspecified DATABASE_URL environment variable is used
-      --coprocessor-private-key <COPROCESSOR_PRIVATE_KEY>
-          Coprocessor private key file path. Private key is in plain text 0x1234.. format [default: ./coprocessor.key]
       --service-name <SERVICE_NAME>
           Coprocessor service name in OTLP traces [default: coprocessor]
   -h, --help
@@ -61,19 +47,3 @@ Note that there are two thread pools in the Coprocessor backend:
 The tokio one (set via `--tokio-threads`) determines how many tokio threads are spawned. These threads are used for async tasks and should not be blocked.
 
 The FHE compute threads are the ones that actually run the FHE computation (set via `--coprocessor-fhe-threads`).
-
-#### Secret Signing Key
-
-A secret signing key is needed to allow the Coprocessor backend sign input insertion requests. A `coprocessor.key` file can be given on the command line for the **server** as:
-
-```
-coprocessor --help
-Usage: coprocessor [OPTIONS]
-
-Options:
-...
-      --coprocessor-private-key <COPROCESSOR_PRIVATE_KEY>
-          Coprocessor private key file path. Private key is in plain text 0x1234.. format [default: ./coprocessor.key]
-```
-
-The secret signing key must be kept safe when operating the Coprocessor.