Added reorg compatible privacy

docs/Concepts/Privacy/Privacy-Overview.md

@@ -8,14 +8,14 @@ In Besu, privacy refers to the ability to keep transactions private between the
 participants. Other participants cannot access the transaction content or list of participants.
 
 !!! important
-
-    For production systems requiring private transactions:
-
-    * It is recommended you use a network with a consensus mechanism supporting transaction
-    finality, such as [IBFT 2.0](../../HowTo/Configure/Consensus-Protocols/IBFT.md).
-    * Orion must be [highly available and run in a separate instance to Besu].
-
-    Using private transactions with [pruning](../Pruning.md) is not supported.
+    For production systems requiring private transactions: 
+        
+    * We recommend using a network with a consensus mechanism supporting transaction finality. For example, 
+    [IBFT 2.0](../../HowTo/Configure/Consensus-Protocols/IBFT.md).
+    * Orion must be [highly available and run in a separate instance to Besu](../../HowTo/Use-Privacy/Run-Orion-With-Besu.md).
+
+    Using private transactions with [pruning](../Pruning.md) or [fast sync](../../Reference/CLI/CLI-Syntax.md#sync-mode)
+    is not supported.
 
 ## Private transaction manager
 
@@ -37,8 +37,15 @@ node. [Multi-tenancy](Multi-Tenancy.md) allows multiple participants to use the
 node.
 
 !!! tip
+    Private Transaction Managers are also known as Enclaves.
+
+## Reorg Compatible Privacy
+
+In v1.4, using private transactions in a network using a consensus mechanism 
+where forks occur (that is, PoW or Clique) is an early access feature. For example, using private
+transactions on Ropsten. 
 
-    Private Transaction Managers are also refered to as Enclaves.
+Do not use private transctions in production networks using consensus mechanisms that fork.  
 
 <!-- Links -->
-[highly available and run in a separate instance to Besu]: ../../HowTo/Use-Privacy/Run-Orion-With-Besu.md
+[highly available and run in a separate instance to Besu]: ../../HowTo/Use-Privacy/Run-Orion-With-Besu.md

docs/Concepts/Privacy/Private-Transaction-Processing.md

@@ -73,12 +73,13 @@ can read and write to the private world state, and read from the public world st
 
 !!! important
 
-    For production systems requiring private transactions:
-
-    * It is recommended you use a network with a consensus mechanism supporting transaction
-    finality, such as [IBFT 2.0](../../HowTo/Configure/Consensus-Protocols/IBFT.md).
-    * Orion must be [highly available and run in a separate instance to Besu].
+    * We recommend using a network with a consensus mechanism supporting transaction finality. For example, 
+    [IBFT 2.0](../../HowTo/Configure/Consensus-Protocols/IBFT.md).
+    * Orion must be [highly available and run in a separate instance to Besu](../../HowTo/Use-Privacy/Run-Orion-With-Besu.md).
+
+    Using private transactions with [pruning](../Pruning.md) or [fast sync](../../Reference/CLI/CLI-Syntax.md#sync-mode)
+    is not supported.
 
 <!-- Links -->
 [signed with a random key or the key specified on the command line]: ../../HowTo/Use-Privacy/Sign-Privacy-Marker-Transactions.md
-[highly available and run in a separate instance to Besu]: ../../HowTo/Use-Privacy/Run-Orion-With-Besu.md
+[highly available and run in a separate instance to Besu]: ../../HowTo/Use-Privacy/Run-Orion-With-Besu.md

docs/Reference/API-Methods.md

@@ -4163,6 +4163,9 @@ data using `eea_sendRawTransaction`.
 !!! important
     For production systems requiring private transactions, we recommend using a network
     with a consensus mechanism supporting transaction finality. For example, [IBFT 2.0](../HowTo/Configure/Consensus-Protocols/IBFT.md).
+
+    Using private transactions with [pruning](../Concepts/Pruning.md) or [fast sync](CLI/CLI-Syntax.md#sync-mode)
+    is not supported.
 
     Besu does not implement [`eea_sendTransaction`](../HowTo/Send-Transactions/Account-Management.md).