chore(): update readme file

Author: kaltra-muho

README.md

@@ -166,6 +166,47 @@ ACURAST_MNEMONIC=abandon abandon about ...
   - Second element: The address of the original deployer
   - Third element: The deployment ID
   - Example: `["Acurast", "5CiPPseXPECbkjWCa6MnjNokrgYjMqmKndv2rSnekmSK2DjL", 123456]`
+- `benchmarkFilters` (optional): Minimum benchmark requirements used to filter eligible processors.
+  - `minMemoryBytes`: Minimum total RAM in bytes.
+  - `minCpuSingleCoreScore`: Minimum single-core CPU score.
+  - `minStorageBytes`: Minimum total storage in bytes.
+  - `minStorageIoScore`: Minimum storage I/O score.
+  - `poolIds` (advanced): Override compute-pallet benchmark pool IDs.
+
+### Benchmark Filters
+
+You can constrain deployments to processors that satisfy minimum benchmark values.
+Benchmark filters can be configured in `acurast.json` and/or passed via deploy flags.
+
+Config example:
+
+```json
+{
+  "projects": {
+    "example": {
+      "benchmarkFilters": {
+        "minMemoryBytes": 4000000000,
+        "minCpuSingleCoreScore": 1000,
+        "minStorageBytes": 64000000000,
+        "minStorageIoScore": 500
+      }
+    }
+  }
+}
+```
+
+Deploy flag examples (can be combined):
+
+```bash
+acurast deploy --min-memory 4GB --min-cpu-score 1000 --min-storage 64GB --min-io-score 500
+```
+
+Notes:
+
+- CLI flags merge with `benchmarkFilters` from `acurast.json`.
+- `--min-memory` and `--min-storage` accept human-readable byte sizes (for example `4GB`, `512MiB`).
+- During deploy, matcher `check` validates whether enough processors match at the current reward.
+- Per-processor address lists are shown from on-chain `acurastMarketplace.assignedProcessors` after match.
 
 #### .env