Refactored Dockerfile and README to use 'outputs' directory instead of 'execution/results'

Author: merendamattia

Dockerfile

@@ -25,8 +25,8 @@ COPY . .
 # Build the project with Gradle
 RUN gradle assemble
 
-# Create results directory
-RUN mkdir -p /app/execution/results
+# Create outputs directory
+RUN mkdir -p /app/outputs
 
 # Set the entry point of the container
 ENTRYPOINT ["java", "-jar", "/app/build/libs/evm-lisa-all.jar"]

README.md

@@ -66,21 +66,21 @@ Alternatively, you can pass your API key directly using the `--etherscan-api-key
 
 1. Build the Docker container:
    ```bash
-   mkdir -p execution/docker &&
+   mkdir -p outputs/docker &&
    docker build -t evm-lisa:latest .
    ```
 
 2. Run EVMLiSA with Docker:
    ```bash
    docker run --rm -it \
    -v $(pwd)/.env:/app/.env \
-   -v $(pwd)/execution/docker:/app/execution/results \
+   -v $(pwd)/outputs/docker:/app/outputs \
    evm-lisa:latest \
    [options]
    ```
 
    - `-v $(pwd)/.env:/app/.env`: Mounts your environment file
-   - `-v $(pwd)/execution/docker:/app/execution/results`: Shares the results directory
+   - `-v $(pwd)/outputs/docker:/app/outputs`: Shares the results directory
 
 ### Using Command Line
 
@@ -153,7 +153,7 @@ java -jar build/libs/evm-lisa-all.jar \
 ```bash
 docker run --rm -it \
 -v $(pwd)/.env:/app/.env \
--v $(pwd)/execution/docker:/app/execution/results \
+-v $(pwd)/outputs/docker:/app/outputs \
 evm-lisa:latest \
 -a 0x7c21C4Bbd63D05Fa9F788e38d14e18FC52E9557B \
 --stack-size 64 \
@@ -205,39 +205,53 @@ For cross-chain analysis, EVMLiSA supports policy files that define event-functi
 {
   "policy": [
     {
-      "event": "EventName1",
-      "function": "functionName1"
-    },
-    {
-      "event": "EventName2",
-      "function": "functionName2"
+      "sourceFunction": {
+        "name": "deposit",
+        "events": ["Deposit"]
+      },
+      "destinationFunction": {
+        "name": "deposit"
+      }
     }
   ]
 }
 ```
 
 ### Policy structure explanation
 
-- **policy**: An array of objects, each containing:
-  - **event**: The name of the event that triggers a cross-chain operation
-  - **function**: The name of the function that should be called in response to the event
+- `policy`: An array of objects, each containing:
+  - `sourceFunction`: An object describing the source function and its events:
+    - `name`: The name of the function that emits the event
+    - `events`: An array of event names that trigger cross-chain operations
+  - `destinationFunction`: An object describing the destination function:
+    - `name`: The name of the function that should be called in response to the event
 
 ### Example
 
 ```json
 {
   "policy": [
     {
-      "event": "Deposit",
-      "function": "deposit"
-    },
-    {
-      "event": "TransferOut",
-      "function": "transferOut"
+      "sourceFunction": {
+        "name": "initGenesisBlock",
+        "events": [
+          "InitGenesisBlockEvent"
+        ]
+      },
+      "destinationFunction": {
+        "name": "initGenesisBlock"
+      }
     },
     {
-      "event": "VaultTransfer",
-      "function": "returnVaultAssets"
+      "sourceFunction": {
+        "name": "pause",
+        "events": [
+          "Paused"
+        ]
+      },
+      "destinationFunction": {
+        "name": "pause"
+      }
     }
   ]
 }