From 515c192500eab84d273d2e22e68c4aa142126944 Mon Sep 17 00:00:00 2001
From: fixanoid <felix.shnir@gmail.com>
Date: Wed, 25 Mar 2020 10:46:55 -0400
Subject: [PATCH] Updating Compatibility table & adding Quorum 2 geth map
 (#959)

---
 docs/FAQ.md | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/docs/FAQ.md b/docs/FAQ.md
index 30b0ffae3..3d7186c2f 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -41,14 +41,19 @@
     Unfortunately, that is not possible. Quorum nodes configured with raft will only be able to work correctly with other nodes running raft consensus. This applies to all other supported consensus algorithms.
 
 ??? info "Quorum version compatibility table"
-    |                                     | Adding new node v2.0.x | Adding new node v2.1.x | Adding new node v2.2.x |
-    | ----------------------------------- | ---------------------- | ---------------------- | ---------------------- |
-    | Existing chain consisting of v2.0.x | <span style="color:green;">block sync<br /> public txn<br /> private txn</span>  | <span style="color:red;">block sync</span>  | <span style="color:red;">block sync</span> |
-    | Existing chain consisting of v2.1.x | <span style="color:red;">block sync</span>  | <span style="color:green;">block sync<br /> public txn<br /> private txn</span> | <span style="color:green;">block sync<br /> public txn<br /> private txn</span> |
-    | Existing chain consisting of v2.2.x | <span style="color:red;">block sync</span>  | <span style="color:green;">block sync<br /> public txn<br /> private txn</span> | <span style="color:green;">block sync<br /> public txn<br /> private txn</span> |
+    |                                     | Adding new node v2.0.x | Adding new node v2.1.x - v2.5.x |
+    | ----------------------------------- | ---------------------- | ---------------------- |
+    | Existing chain consisting of v2.0.x | <span style="color:green;">block sync<br /> public txn<br /> private txn</span>  | <span style="color:red;">block sync</span>  |
+    | Existing chain consisting of v2.1.x - v2.5.0 | <span style="color:red;">block sync</span>  | <span style="color:green;">block sync<br /> public txn<br /> private txn</span> |
 
     **Note:** While every Quorum v2 client will be able to connect to any other v2 client, the usefullness will be severely degraded. <span style="color:red;">Red color</span> signifies that while connectivity is possible, <span style="color:red;">red colored</span> versions will be unable to send public or private txns to the rest of the net due to the EIP155 changes in the signer implemented in newer versions.
 
+??? info "Quorum to Geth version mapping"
+    | Quorum v2.0.x - v2.1.1 | Quorum v2.2.0 - v2.2.1 | Quorum v2.2.2 - v2.5.0 |
+    | ---------------------- | ---------------------- | ---------------------- |
+    | Geth v1.7.2            | Geth v1.8.12           | Geth v1.8.18           |
+
+
 ### Tessera FAQ
 
 ??? question "What does enabling 'disablePeerDiscovery' mean?"