Run Orion with Besu
Privacy requires Orion to be highly available.
All private transaction participants must be online for a private transaction to be successfully distributed. If any participants are offline when the private transaction is submitted, the transaction is not attempted and must be resubmitted.
If a receiving Orion is available when the private transaction is distributed but is unavailable when the privacy marker transaction is processed, the private transaction is not executed by the receiving Besu node. The private states in the Besu nodes are then inconsistent.
For production systems, we recommend running Besu and Orion in separate instances. If running Besu and Orion in the same instance, restrict the amount of memory used by each JVM to ensure each has enough memory.