diff --git a/docs/avs/running-avs-operator.md b/docs/avs/running-avs-operator.md
index d7242e86..f1941ec5 100644
--- a/docs/avs/running-avs-operator.md
+++ b/docs/avs/running-avs-operator.md
@@ -23,13 +23,13 @@ This registration process is essential for establishing an identity and enabling
 To register, the following command should be executed in the terminal:
 
 ```bash
-docker run -it public.ecr.aws/y7v2w8b2/avs-othentic-client:90fc014d operator register
+docker run --platform linux/amd64 -it public.ecr.aws/y7v2w8b2/avs-othentic-client:f1e34480 operator register
 ```
 
 After executing the command, the following information will be required:
 
-- **Operator's Private Key**: the private key must be provided to authenticate and secure the operator account.
-- **AVS Governance Contract Address**: the following contract address should be entered: [0xfADc5aCf45D7E9ebAB82Dea71E26fe3A9A833337](https://holesky.etherscan.io/address/0xfadc5acf45d7e9ebab82dea71e26fe3a9a833337).
+- **Operator's Private Key**: the private key must be provided to authenticate and secure the operator account. The private key should be provided twice: as a private key and as a signing key.
+- **AVS Governance Contract Address**: the following contract address should be entered: [0xBA7A7CaEE3b1ed84a98dBc20Ea20fe21FE7D557e](https://holesky.etherscan.io/address/0xBA7A7CaEE3b1ed84a98dBc20Ea20fe21FE7D557e).
 
 ## Step 2: Preparing the Configuration File
 
@@ -44,10 +44,12 @@ DATA_FEED_ID=ETH
 L1_RPC= # holesky RPC endpoint
 L1_CHAIN=17000
 
-L2_RPC=# amoy RPC endpoint
+L2_RPC= # amoy RPC endpoint
 L2_CHAIN=80002
 
-TASK_PERFORMER=0x8074Ab463bcDaEE1D87Ec98959084D659d48d4d5
+AVS_GOVERNANCE_ADDRESS=0xBA7A7CaEE3b1ed84a98dBc20Ea20fe21FE7D557e
+ATTESTATION_CENTER_ADDRESS=0xA8779c817C748b15122EF572c195019601715BBe
+TASK_PERFORMER=0x906CD7211CeA5Dc88977c50B015675aB64327728
 PRIVATE_KEY= # operator's private key
 ```
 
@@ -74,7 +76,8 @@ These images can be launched using the following Docker Compose configuration:
 ```yaml
 services:
   operator-attester:
-    image: public.ecr.aws/y7v2w8b2/avs-othentic-client:90fc014d
+    image: public.ecr.aws/y7v2w8b2/avs-othentic-client:f1e34480
+    platform: linux/amd64
     command:
       [
         "node",
@@ -86,7 +89,8 @@ services:
     env_file:
       - .env
   operator-validation-api:
-    image: public.ecr.aws/y7v2w8b2/avs-validation-api:90fc014d
+    image: public.ecr.aws/y7v2w8b2/avs-validation-api:f1e34480
+    platform: linux/amd64
     env_file:
       - .env
 ```
diff --git a/docs/data-providers/deploy.md b/docs/data-providers/deploy.md
index d93128fd..24a5d452 100644
--- a/docs/data-providers/deploy.md
+++ b/docs/data-providers/deploy.md
@@ -29,7 +29,7 @@ Here's a simple example of a `docker-compose.yml` file that you can use to run t
 ```yaml
 services:
   redstone-oracle-node:
-    image: public.ecr.aws/y7v2w8b2/redstone-oracle-node:957ca2a1
+    image: public.ecr.aws/y7v2w8b2/redstone-oracle-node@sha256:07eb1cc4aa3a4f0275c2ef5c2f9a95af06150e35211e20f66f9b24ab1c05cef7
     restart: always
     depends_on:
       - redstone-kms
@@ -47,7 +47,7 @@ services:
 
   redstone-kms:
     restart: always
-    image: public.ecr.aws/y7v2w8b2/kms@sha256:d5df0ad389c329e541b26b09b3ad18b453342f1fee3837c1bd05f23c4a4264da
+    image: public.ecr.aws/y7v2w8b2/kms@sha256:d069bc9afcd1b4e6884e2d4e530d90c94db0aaf1a2265d7facb4f4e2d2fefb3d
     networks:
       - private_network
     expose:
diff --git a/docs/get-started/supported-chains.md b/docs/get-started/supported-chains.md
index 0c998089..1e578a33 100644
--- a/docs/get-started/supported-chains.md
+++ b/docs/get-started/supported-chains.md
@@ -63,6 +63,7 @@ You can check the integration with the showroom app [for EVM Chains](https://sho
 - Etherlink
 - Reya
 - Sei
+- Ink Sepolia
 - And many more...
 
 ### We also support a few non-EVM-compatible chains