mismatching validator client key share index #253 (#259)

* mismatching validator client key share index#253

* mismatching validator client key share index#253

docs/int/faq/errors.mdx

@@ -288,6 +288,18 @@ docker compose logs
 		If the private key lock file has a timestamp older than 5 seconds, Charon will replace it and continue with its work.
 		If you're sure that no other Charon instances are running, you can delete the private key lock file.
     </details>
+    <details className="details">
+      <summary>
+        <h4 id="mismatching-validator-client-key">
+          <code>Validator api 5xx response: mismatching validator client key share index, Mth key share submitted to Nth charon peer</code> error
+        </h4>
+      </summary>
+    The issue revolves around an invalid setup or deployment, where keyshares are not tied to the enr private key. There appears to be a mix-up during deployment, leading to a mismatching validator client key share index.
+    <ul>For example:</ul>
+    <ul>Imagine node N is Alice, and node M is Bob, the error would read:<code>mismatching validator client key share index, Bob's key share submitted to Alice's charon node.</code></ul>
+    <ul>Bob's private key share(s) are imported to a VC that is connected to Alice's charon node. This is a invalid setup/deployment. Alice's charon node should only be connected to Alice's VC.</ul>
+		Check the keyshare of each node inside cluster-lock.json and see that matches with the key inside <code>node(num)/validator_keys/keystore-0.json</code>
+    </details>
 </details>
 <details open className="details">
   <summary>